Hi guys!
First of all to clarify that I am using Telerik.Web.UI v. 2011.1.413.40, so it may be addressed already in the newer versions. I am doing some Sitefinity development, that's why I am using that version of the controls.
The problem is that hidden fields are really hidden ;) in the editor when used under IE 9, while they show up in IE versions lower than 9 and are selectable in the Editor design view. Not really a big deal, can you tell me if this is addressed and the hidden fields are shown in some of the newer versions of the editor under IE 9 or not?
If they are I'll not bother to search for workaround (my release will probably fall after the Q3 release so I think I'll be using pretty new version of the controls if Sitefinity include it).
Refer to the screenshots for examples.
I am starting off with a blank HTML with only
In IE 9 as you can see the editor design surfice is blank, while the hidden field is correctly displayed and selectable in lower versions.
Once again it is not a big deal and once again - I just want to know if this is addressed or will be addressed (seems very low priority but it may appear important to my project).
First of all to clarify that I am using Telerik.Web.UI v. 2011.1.413.40, so it may be addressed already in the newer versions. I am doing some Sitefinity development, that's why I am using that version of the controls.
The problem is that hidden fields are really hidden ;) in the editor when used under IE 9, while they show up in IE versions lower than 9 and are selectable in the Editor design view. Not really a big deal, can you tell me if this is addressed and the hidden fields are shown in some of the newer versions of the editor under IE 9 or not?
If they are I'll not bother to search for workaround (my release will probably fall after the Q3 release so I think I'll be using pretty new version of the controls if Sitefinity include it).
Refer to the screenshots for examples.
I am starting off with a blank HTML with only
<input type="hidden" value="test"></input>In IE 9 as you can see the editor design surfice is blank, while the hidden field is correctly displayed and selectable in lower versions.
Once again it is not a big deal and once again - I just want to know if this is addressed or will be addressed (seems very low priority but it may appear important to my project).
2 Answers, 1 is accepted
0
Accepted
Hi Pavka,
Actually, this is a browser behavior and it can be reproduced in a standard editable IFRAME. The editor's content area is an editable IFRAME and to provide rich text editing capabilities uses the Rich Text Editing engine of the browser under which it operates.
IE developers have changed the way the browser renders the hidden fields in the IE9 browser and now they are invisible as in the other browsers: Firefox 6, Google Chrome, Safari and Opera.
The only workaround that I could suggest is to render the page in IE8 mode using the meta tag below:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
Have a successful day!
Kind regards,
Rumen
the Telerik team
Actually, this is a browser behavior and it can be reproduced in a standard editable IFRAME. The editor's content area is an editable IFRAME and to provide rich text editing capabilities uses the Rich Text Editing engine of the browser under which it operates.
IE developers have changed the way the browser renders the hidden fields in the IE9 browser and now they are invisible as in the other browsers: Firefox 6, Google Chrome, Safari and Opera.
The only workaround that I could suggest is to render the page in IE8 mode using the meta tag below:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
Have a successful day!
Kind regards,
Rumen
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now
0
Power
Top achievements
Rank 2
Rank 2
answered on 05 Oct 2011, 03:21 PM
Thanks, Rumen!
Makes sense. Seems MS are going to comply with the other browsers on this.
Makes sense. Seems MS are going to comply with the other browsers on this.