I am posting this as a workaround in case anyone else is having this issue.
I was having a problem with Firefox with the Paste Plain Text (and Paste Cleaning Word Formatting) inline popup windows on tall pages that have multiple Editors. I created a test page to demonstrate this:
http://client.hughes-stl.com/wuphysicians/test/edit.aspx
If you click the Paste Plain Text button in the top Editor, the inline popup shows fine. If you scroll all the way down and click the Paste Plain Text button in the bottom editor, the popup at first does not appear to show up. If you scroll back up, you'll see that it has appeared at the top of the page. This causes a lot of confusion for a client of ours who thinks that the button doesn't work. It seems to me that multiple editors will show their inline popups positioned next to the first Telerik box (or always at the top of the page) regardless of where the Editor that fired the inline popup is. I would prefer them shown centered on the page window (position: fixed) or near the Editor that fired them.
I have a lot of CSS on the actual page, but I created this test page with no extra CSS to test/demonstrate that it is not a CSS conflict issue. According to Firebug, the inline popup window for the second editor is absolutely positioned near the top of the page (not position:fixed). For long pages with multiple editors, this means many users cannot see the inline popups when they appear.
The solution is to change the DOCTYPE of the page. I had it originally at HTML 4 Transitional. I set it to XHTML (Strict or not; both work), and it shows up in the middle of the browser window correctly.
I was having a problem with Firefox with the Paste Plain Text (and Paste Cleaning Word Formatting) inline popup windows on tall pages that have multiple Editors. I created a test page to demonstrate this:
http://client.hughes-stl.com/wuphysicians/test/edit.aspx
If you click the Paste Plain Text button in the top Editor, the inline popup shows fine. If you scroll all the way down and click the Paste Plain Text button in the bottom editor, the popup at first does not appear to show up. If you scroll back up, you'll see that it has appeared at the top of the page. This causes a lot of confusion for a client of ours who thinks that the button doesn't work. It seems to me that multiple editors will show their inline popups positioned next to the first Telerik box (or always at the top of the page) regardless of where the Editor that fired the inline popup is. I would prefer them shown centered on the page window (position: fixed) or near the Editor that fired them.
I have a lot of CSS on the actual page, but I created this test page with no extra CSS to test/demonstrate that it is not a CSS conflict issue. According to Firebug, the inline popup window for the second editor is absolutely positioned near the top of the page (not position:fixed). For long pages with multiple editors, this means many users cannot see the inline popups when they appear.
The solution is to change the DOCTYPE of the page. I had it originally at HTML 4 Transitional. I set it to XHTML (Strict or not; both work), and it shows up in the middle of the browser window correctly.
1 Answer, 1 is accepted
0
Hi guys,
RadControls for ASP.NET AJAX are designed and developed to work primarily under standards compliance mode XHTML1.0 and XHTML1.1 because in quirks mode it is really hard to achieve similar looks in all browsers, especially with a sophisticated controls such as RadEditor. Our recommendation is to stick to standards compliance mode, unless quirks is required. This is the only way to achieve best performance and crossbrowser looks.
Greetings,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
RadControls for ASP.NET AJAX are designed and developed to work primarily under standards compliance mode XHTML1.0 and XHTML1.1 because in quirks mode it is really hard to achieve similar looks in all browsers, especially with a sophisticated controls such as RadEditor. Our recommendation is to stick to standards compliance mode, unless quirks is required. This is the only way to achieve best performance and crossbrowser looks.
Greetings,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.