greasemonkey firefox js javascript Archives - The Story of David Kaspar https://blog.davidkaspar.com/archives/tag/greasemonkey-firefox-js-javascript Online journal and ponderings about the Internet, gadgets and photography. Fri, 02 Dec 2005 17:40:52 +0000 en-US hourly 1 https://wordpress.org/?v=6.9 https://blog.davidkaspar.com/wp-content/uploads/2020/05/chubby.gif greasemonkey firefox js javascript Archives - The Story of David Kaspar https://blog.davidkaspar.com/archives/tag/greasemonkey-firefox-js-javascript 32 32 Firefox 1.5 and Greasemonkey 0.6.4: where is my DOMParser https://blog.davidkaspar.com/archives/2005/12/firefox-1-5-and-greasemonkey-0-6-4-where-is-my-domparser.php https://blog.davidkaspar.com/archives/2005/12/firefox-1-5-and-greasemonkey-0-6-4-where-is-my-domparser.php#comments Fri, 02 Dec 2005 17:40:52 +0000 https://davidkaspar.com/wp/2005/12/02/firefox-1-5-and-greasemonkey-0-6-4-where-is-my-domparser/ The good news is that Firefox 1.5 is out and for it there is also the newest Greasemonkey 0.6.4. The bad news is that this combination breaks a lot of existing user scripts. There is a WiKi up that gives a helping hand at upgrading scripts but it is not complete (covers mainly XPCNativeWrappers, you … Continue reading "Firefox 1.5 and Greasemonkey 0.6.4: where is my DOMParser"

The post Firefox 1.5 and Greasemonkey 0.6.4: where is my DOMParser appeared first on The Story of David Kaspar.

]]> The good news is that Firefox 1.5 is out and for it there is also the newest Greasemonkey 0.6.4.
The bad news is that this combination breaks a lot of existing user scripts. There is a WiKi up that gives a helping hand at upgrading scripts but it is not complete (covers mainly XPCNativeWrappers, you know the unsafeWindow thingy).
I was quite surprised that the IMDB ratings for MyVue.com stopped working. It was specifically the DOMParser that stops working with the cryptic error message ‘DOMParser is not a constructor’.
The instinctive thing would be to use responseXML instead of responseText but only until you remind your self that the GM_xmlhttpRequest implementation returns the same string for both functions (instead of the correct DOM object for responseXML).
I was just about to dive into manual parsing of the XML response with regexp and indexOf goodness but was literally saved by boogs from the Greaseblog.
He pointed me to the little known “new XML()” of Mozilla E4X. It can parse XML text strings and provide DOM like interface so it is good enough for the job.
There are some oddities of course. When first using it you will get a xml is a reserved identifier error. Don’t ask why but the xml declaration has to be stripped out from the top of your xml document. Achieve this with responseText.replace(/<\?xml version="1.0"\?>/,'').
To get to a node use the following syntax: xmlDoc..foo[0] (for the first instance of foo tag). I found more information on the EX4 syntax at the E4X Expression Tester.
Now get busy fixing those old Greasemonkey scripts!
Update
Turns out that you can use XPCNativeWrapper to instantiate a new DOMParser (and other missing objects like XMLSerializer, HTMLBodyElement, …) like so:
var dp = new XPCNativeWrapper(window, "DOMParser").DOMParser.
I am not sure about the security implications of doing this.

The post Firefox 1.5 and Greasemonkey 0.6.4: where is my DOMParser appeared first on The Story of David Kaspar.

]]> https://blog.davidkaspar.com/archives/2005/12/firefox-1-5-and-greasemonkey-0-6-4-where-is-my-domparser.php/feed 2