Scripts that have been updated, in some way, due to Firefox 1.5 and Greasemonkey 0.6.4:
- Flickr Photo Page Enhancer: It originally used GM_XmlHttpRequest, that went away in GM 0.3.5 due to security reasons, I replaced it with regular XmlHttpRequest, which went away as a side effect of new security measures in 0.6.*, but GM_XmlHttpRequest is back. Did that make any sense to you? Me neither.
Update 04-Dec-05: Okay, now it uses E4X and it’s pretty and elegant. Whee! - Flickr Thumbnails Enhancer Same reason as above, same ugly, ugly hacky solution to the problem.
- del.icio.us >> My Web: del.icio.us redesigned (and might I say damn fine job), and this script was highly dependent on the page structure. Fixed.
- Yahoo User Persistence Thing: There was an existing bug with selecting “Other..” not working correctly.
- Update 03-Dec-05: Flickr Rich Edit, Flickr Tag Quick Edit, and Flickr User Icon Enhancer: Done in by changes to unsafeWindow. Fixed.
Also, several scripts that are no longer useful are no longer under active development. These include the Flickr Login Thing (Yahoo Login Thing pretty much covers that), the Bloglines thing (now built into Bloglines… when did that happen?), and several one-offs that I made on request but don’t actually use myself.
13 Responses to 'Userscript updates due to Greasemonkey 0.6.4'
Track 
replies to this post.
Sorry about the xmlhttprequest thing. I know that was kinda a silly dance GM did.
the Flickr Photo Page Enhancer doesn’t work for me. The error console shows
Error: DOMParser is not a constructor
I’m using FF 1.5 and GreaseMonkey 0.6.4
Aaron: I understand the reasons behind the changes, really, and I appreciate the thought you (and Mark et al) have put into security and stability. Better documentation for people who don’t quite follow the list would not be unwelcome. :)
Ianiv: I got that error with 0.6.2, but am unable to reproduce with 0.6.4. What platform?
Just to be sure I tried it with a new profile and I still have the same problem.
I’m using WinXP, Firefox says it is
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
which I installed as RC3 but as far as I know is the same as the final 1.5 release.
One more clue: evaluating “var parser = new DOMParser();” in the Javascript console does not give the error and parser is assigned a DOMParser object.
Crap. I was using 0.6.3 and didn’t realize it. I’m off to work now, but I’ll get back to this ASAP.
Loving the FPPE script, eagerly awaiting fix for FF1.5 and GM 0.6.4 While you’re at it, could you throw in a link to large size along with the rest? (I know it’s already covered elsewhere on the page)
If a photo has a large size, that size is stored intead of the original size — in other words, the original size is not stored for images larger than 1024 pixels on a side, and large size is stored instead (ref). The script still says “original”, but the link will be to the biggest version of the picture available, whether that’s the large size or the original size.
Works fine now. Thanks!
thanks for the swell updates.
rich edit works except for the ‘link’ link .. which doesn’t seem to function anymore.
FF 1.6 GM 0.6.4
Good catch Stri. Shows you how often I leave comments, but I would have noticed eventually.
very useful script but with Firefox 1.5 and new Greasmankey…
I test …but they don’t do nathing…what can i do?
You can be more specific for a start, bruno. Can’t troubleshoot with no data.