Home > Unknown Runtime > Innerhtml Unknown Runtime Error

Innerhtml Unknown Runtime Error

Contents

November 29, 2012 at 12:16 AM Sourabh Nazarkar said... July 9, 2011 at 1:34 AM JDSANS said... My advisor refuses to write me a recommendation for my PhD application unless I apply to his lab If possible, how to include cut marks in PDF? (using watermark?) How strange Another cause of the "Unknown runtime error" is attempting to write to elements that are read-only in IE. weblink

It seems that IE 8 does not like custom tag names such as and will throw a "unknown runtime error" when you attempt to set the innerHTML of a custom I wrote a javascript function to create a form, a text input for the headline, and a textarea for the body, all in a hidden div, and then the function submits April 26, 2014 at 12:55 PM haseeb anwar ul haq said... There seems to be an issue with the Javascript in IE. http://stackoverflow.com/questions/13817999/innerhtml-issue-in-ie8-and-below

Innerhtml Unknown Runtime Error

Why does Wikipedia list an improper pronunciation of Esperanto? Which may or may not be a good thing. Reload to refresh your session. PromoteJS Blog Archive ► 2012 (1) ► August 2012 (1) ► 2011 (3) ► June 2011 (1) ► May 2011 (1) ► January 2011 (1) ► 2010 (2) ► October 2010

your code modified : March 11, 2007 at 11:52 AM Rakesh Pai said... @voracity:That behavior is not wrong. current community chat Stack Overflow Meta Stack Overflow your communities Sign up or log in to customize your list. It makes no claim to be an XML parser or to support XHTML.It is interesting that, in this case, IE is strictly adhering to a standard when in many other places If you are really the kind of markup nazi that I am, you'll notice that the p tag doesn't allow any block-level tags within it, and both LI and UL are

Thanks for this post. The simplest way is to convert read-only elements to div element. February 17, 2009 at 7:20 AM Floris said... this content I agree completely that this is not a good error message at all, but really, IE is enforcing correct W3C block/inline tag recommendations here - something Firefox is not doing.

IE was the first to have it, and thus its behavior (including unwanted errors) is the closest thing to a standard there is. December 3, 2012 at 9:36 PM Anonymous said... these are just pure bugs you're running into.innerhtml is particularly problematic, select elements, table elements especially. However, in this case, XML/XHTML has nothing to do with anything; HTML is a separate specification with its own rules, and MSHTML (IE's HTML parser) is only an HTML parser.