On Monday, May 15, 2017 at 5:51:46 PM UTC+3, Anthony Lieuallen wrote:
>
> Where I've heard other people describe it, it sounds like they've made
> compromises to provide compatible calls. Ones I'm not excited about
> emulating.
>
Just in case, please don't rely on what people describe without it
investigating yourself.
GM.getValue("serialized").then(sData => {
> var oData = JSON.parse(sData);
> // useful things happen here.
> });
>
> Which is a change, but hopefully not a huge one.
>
This is a huge change actually and in many cases a breaking one. Just one
example off the top of my head: processing/altering a page while it's being
parsed/loaded using MutationObserver and "@run-at: document-start" so that
the changes are applied to an element before it's actually shown. Any async
API callback will be queued in a separate js engine event after a chunk of
the page is already processed and [usually] even rendered on screen. In
other words you'll introduce FOUC unless there'll be a method to have
GM_value injected alongside the script code (this is what Tampermonkey
does).
--
You received this message because you are subscribed to the Google Groups
"greasemonkey-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/greasemonkey-users.
For more options, visit https://groups.google.com/d/optout.
