I am having an interesting problem that would on the surface appear to be unrelated to the RadEditor.
Basically, I have a RadEditor near the top of the page, not inside of a update panel. This gets its content loaded from a database.
Underneath this, I have an updatepanel with some drop down lists and a few buttons that do stuff with the selected items in the drop down list. When I press one of these buttons for the first time after loading the page, I get Sys.WebForms.PageRequestManagerParserErrorException, with details:
Any thoughts as to how the contents of the RadEditor above the Update Panel would affect the presence of the Parser exception? All help would be greatly appreciated.
UPDATED - This Exception does not appear in Internet Explorer, but does occur in Firefox 2 and 3 and in Safari.
Basically, I have a RadEditor near the top of the page, not inside of a update panel. This gets its content loaded from a database.
Underneath this, I have an updatepanel with some drop down lists and a few buttons that do stuff with the selected items in the drop down list. When I press one of these buttons for the first time after loading the page, I get Sys.WebForms.PageRequestManagerParserErrorException, with details:
Error parsing near ' <!DOCTYPE html P'.
The very odd thing is this: I ONLY get this error if there is complicated HTML text within the RadEditor at the top of the page. If this Editor is empty, then the error does not occur. I have tested this over and over again, always with the same results. If there is just plain text in the editor, I do not get ParserErrorException. If there is more complicated html that I have pasted into the Editor previously and saved to the database, that has now been loaded into the Editor, I always get the exception when I press one of the buttons in the uploadpanel below it for the first time after I have loaded the page.Any thoughts as to how the contents of the RadEditor above the Update Panel would affect the presence of the Parser exception? All help would be greatly appreciated.
UPDATED - This Exception does not appear in Internet Explorer, but does occur in Firefox 2 and 3 and in Safari.