I think you should post this directly in bugzilla.mozilla.org, kind of like
https://bugzilla.mozilla.org/show_bug.cgi?id=616397 as it is not something
we have changed in Greasemonkey, but a Firefox-dependent change of some
sort.
It may help if you phrase that ticket in some way to make non-Greasemonkey
people understand it, and I would suggest changing your user script into a
minimal html page with just a <script src="gm-script.js"> tag linking your
user script, reproducing the issue but with everything except the parsing
that fails removed from it. This hack should not be specific in any way to
the Greasemonkey execution context, as far as I'm aware, and the regression
probably needs some Mozilla people looking in to its details for the proper
fix.
If you can, reduce it down to something as minimal as this (I'm a bit short
on time at the moment, but I think you might get the idea; essentially, the
less unrelated cruft for them to get distracted by the easier to diagnose
and fix it):
prompt('Expected result: "foo & bar"'<><![CDATA[foo & bar]]></>.toString());
--
/ Johan Sundström, http://ecmanaut.blogspot.com/
--
You received this message because you are subscribed to the Google Groups
"greasemonkey-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/greasemonkey-users?hl=en.
