Hi!
We are investigating if we can use the RadEditor to handle asp.net server controls in designtime example: <asp:Label runat="server" />.
So far it seems to work with css-styling on those custom tags, that's great!
But in IE9 (using IE 9 documentMode) the (x)html-serialization of those custom tags with namespace prefix renders incorrectly. When clicking HTML the custom tag becomes <asp:ASP:LABEL runat="server"></asp:ASP:LABEL>
I have debugged the javascript code and found that bug. All IE versions have the node.scopeName property which contains "asp" in this case, and the RadEditor uses this property to build html in combination with node.nodeName property. BUT in IE9-mode the node.nodeName contains both scopeName and localName, thats why it renders wrong.
My bug fix suggestion when in IE9 mode and greater is to use the node.scopeName in combination with node.localName or just use node.nodeName.toLowerCase() like in other browsers...
Please confirm if this bug will be fixed, Thanks.
/Erik
We are investigating if we can use the RadEditor to handle asp.net server controls in designtime example: <asp:Label runat="server" />.
So far it seems to work with css-styling on those custom tags, that's great!
But in IE9 (using IE 9 documentMode) the (x)html-serialization of those custom tags with namespace prefix renders incorrectly. When clicking HTML the custom tag becomes <asp:ASP:LABEL runat="server"></asp:ASP:LABEL>
I have debugged the javascript code and found that bug. All IE versions have the node.scopeName property which contains "asp" in this case, and the RadEditor uses this property to build html in combination with node.nodeName property. BUT in IE9-mode the node.nodeName contains both scopeName and localName, thats why it renders wrong.
My bug fix suggestion when in IE9 mode and greater is to use the node.scopeName in combination with node.localName or just use node.nodeName.toLowerCase() like in other browsers...
Please confirm if this bug will be fixed, Thanks.
/Erik