Comments on: Safari-Bug or Not? DOM Exception 7 http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html PHP freelancer, web developer, mobile web enthusiast Fri, 06 Aug 2010 20:02:29 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Dwight Vietzke http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html/comment-page-1#comment-94 Dwight Vietzke Fri, 23 Jul 2010 02:03:24 +0000 http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html#comment-94 Hi all, The problem sometimes, as eluded to above, is that you can't modify elements with .innerHTML or use other element modification methods (document.write() I think) when the page is served as XML. That is content-type 'application/xhtml+xml'. This is true for many browsers (all?), including Chrome that can read true XML pages. So pages served as XML will error on .innerHTML, unless you create the element in javascript, append it the the document and then use .innerHTML. Why it works for added elements and not existing ones is beyond me, but oh well. Otherwise the problem might just be as stated, that you are trying to modify something that doesn't (clearly) exist yet, is considered 'read only' or something. So what to do it the first case of an XML page? I found this on the web: BetterInnerHTML v1.2, (C) OptimalWorks.net Just google the above for the latest version of their .innerHTML replacement code. Works great for me, although I did modify it for may own purposes (made a Dojo style module of it). It uses simple DOM munipulation to accomplish the same thing as .innerHTML. Hope that helps others who follow this error. Hi all,

The problem sometimes, as eluded to above, is that you can’t modify elements with .innerHTML or use other element modification methods (document.write() I think) when the page is served as XML. That is content-type ‘application/xhtml+xml’. This is true for many browsers (all?), including Chrome that can read true XML pages. So pages served as XML will error on .innerHTML, unless you create the element in javascript, append it the the document and then use .innerHTML. Why it works for added elements and not existing ones is beyond me, but oh well.

Otherwise the problem might just be as stated, that you are trying to modify something that doesn’t (clearly) exist yet, is considered ‘read only’ or something.

So what to do it the first case of an XML page?

I found this on the web:

BetterInnerHTML v1.2, (C) OptimalWorks.net

Just google the above for the latest version of their .innerHTML replacement code. Works great for me, although I did modify it for may own purposes (made a Dojo style module of it). It uses simple DOM munipulation to accomplish the same thing as .innerHTML.

Hope that helps others who follow this error.

]]> By: goran http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html/comment-page-1#comment-86 goran Mon, 22 Mar 2010 18:36:25 +0000 http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html#comment-86 Works for me too. Thanks a_[w]! Works for me too. Thanks a_[w]!

]]> By: NB http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html/comment-page-1#comment-70 NB Tue, 19 May 2009 23:59:00 +0000 http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html#comment-70 Thanks a_[w], that did the trick for me! Thanks a_[w], that did the trick for me!

]]> By: a_[w] http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html/comment-page-1#comment-69 a_[w] Wed, 13 May 2009 17:32:24 +0000 http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html#comment-69 For dynamic CSS you can use "innerText" property of STYLE tag object. It works without any errors. For dynamic CSS you can use “innerText” property of STYLE tag object. It works without any errors.

]]> By: Rocco http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html/comment-page-1#comment-60 Rocco Mon, 24 Nov 2008 20:30:44 +0000 http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html#comment-60 thanks barney, seems like this problem never gets old ;) maybe you could provide a little code listing? i could add it to the original post. thanks barney, seems like this problem never gets old ;) maybe you could provide a little code listing? i could add it to the original post.

]]> By: Barney http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html/comment-page-1#comment-59 Barney Sun, 23 Nov 2008 23:23:34 +0000 http://www.g-roc.com/27_safari-bug-or-not-dom-exception-7.html#comment-59 You were one of the top coherent hits for 'NO_MODIFICATION_ALLOWED_ERR: DOM Exception 7', which has been giving me bizzare trouble with Webkit when it comes to writing innerHTML for a STYLE tag (I'm trying to build dynamically generated CSS stylesheets). As far as I can work out Webkit's DOM believes a lot of proper XML XHTML tags are read only. Not the most helpful comment to a year-old problem, I know :). I'm getting arround it by defining another variable, copying the current innerHTML if needed, deleting the original element and then replacing it. Ugly but least roundabout way I can find of dealing with this seemingly unsolvable problem. You were one of the top coherent hits for ‘NO_MODIFICATION_ALLOWED_ERR: DOM Exception 7′, which has been giving me bizzare trouble with Webkit when it comes to writing innerHTML for a STYLE tag (I’m trying to build dynamically generated CSS stylesheets). As far as I can work out Webkit’s DOM believes a lot of proper XML XHTML tags are read only. Not the most helpful comment to a year-old problem, I know :). I’m getting arround it by defining another variable, copying the current innerHTML if needed, deleting the original element and then replacing it. Ugly but least roundabout way I can find of dealing with this seemingly unsolvable problem.

]]>