On 07/21/2014 12:21 AM, milakam wrote:
Hi everyone,
A BeforeLoad replacement was never discussed as a target use case for
MutationObservers, therefore this message.
I'm currently creating a JS cross-browser user script and noticed that
only Chromium notifies the MutationObserver for an
Boris
That said, I can't reproduce the behavior you claim.
http://jsfiddle.net/59Sxf/ alerts evil for me in Chrome.
If the alert scripts are referenced as external js files it will alert
good.js in Chrome. But I assume it's then a bug in Chrome that Data URLs
are treated differently.
Olli
No.
I was walking with Will about how the browser prioritizes the loading of
scripts and stylesheets. An idea that came up in our conversation was
allowing the user to directly access Fetch objects associated with scripts
and stylesheets. Some examples of how I could see this working:
(1) Allowing
On 7/21/14, 12:42 PM, milakam wrote:
If the alert scripts are referenced as external js files it will alert
good.js in Chrome.
http://jsfiddle.net/59Sxf/1/ seems to disagree.
This doesn't sound too bad Safari 5.0 and later (and other WebKit-based
browsers) generates a beforeload event before
On 7/21/14, 1:13 PM, Boris Zbarsky wrote:
http://jsfiddle.net/59Sxf/1/ seems to disagree.
Er, sorry, I failed to actually test it in Chrome.
And my original fiddle with data: URIs had a quoting issue which meant
it wasn't testing the behavior.
So I agree with you about what Chrome's
On 7/21/14, 1:21 PM, Boris Zbarsky wrote:
That said, Chrome's behavior is not useful for your purposes for
script-inserted scripts, since those do prepare a script before the
mutation observer fires...
And for parser-created scripts I expect Chrome doesn't prevent the
preload, but haven't
