Comments on: 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 Online journal and ponderings about the Internet, gadgets and photography. Thu, 03 May 2007 02:53:49 +0000 hourly 1 https://wordpress.org/?v=6.9.1 By: Tim McCormack https://blog.davidkaspar.com/archives/2005/12/firefox-1-5-and-greasemonkey-0-6-4-where-is-my-domparser.php#comment-1014 Thu, 03 May 2007 02:53:49 +0000 https://davidkaspar.com/wp/2005/12/02/firefox-1-5-and-greasemonkey-0-6-4-where-is-my-domparser/#comment-1014 So, any new information about the XPCNativeWrapper approach, and the security implications thereof?

]]> By: Johan Sundström https://blog.davidkaspar.com/archives/2005/12/firefox-1-5-and-greasemonkey-0-6-4-where-is-my-domparser.php#comment-1013 Thu, 02 Mar 2006 09:04:37 +0000 https://davidkaspar.com/wp/2005/12/02/firefox-1-5-and-greasemonkey-0-6-4-where-is-my-domparser/#comment-1013 Interestingly, I manage quite fine to use DOMParser without jumping through all those hoops in the Mark my links script I whipped together the last few days — at least running Mozilla 1.5.0.1. Reports has it it doesn’t work with 1.5.0, though, so your method may have slightly better portability.

David says:
Maybe Mozilla 1.5.0.1 again enabled the DOMParser?
It was specifically Firefox 1.5 for which many Greasemonkey scripts broke because DOMParser had been disabled.
I found the EX4 syntax very elegant but will try not use it because it is less portable.
Will check out your scripts later today.

]]>