On Tue, 28 Aug 2012, Boris Zbarsky wrote:
On 8/28/12 12:46 AM, Ian Hickson wrote:
I've updated the spec to not block on style sheets for nested parser's
scripts.
I'm not sure I follow. What is not going to block on what with this change?
As far as I can tell, 0 1 2 in your testcase at
On 8/28/12 2:12 AM, Ian Hickson wrote:
On Tue, 28 Aug 2012, Boris Zbarsky wrote:
As far as I can tell, 0 1 2 in your testcase at
http://damowmow.com/playground/demos/document-write-and-scripts/002.html is
consistent with the following order of execution:
1) x=0
2) x1=0,x=1 (nothing else has
On Tue, 28 Aug 2012, Boris Zbarsky wrote:
Ah, I see. So is what you're proposing that stylesheets that are
inserted by a nested tokenizer not block scripts in general, but
stylesheets that are inserted by a top-level tokenizer block scripts as
usual?
Or is what you're proposing that
On 8/28/12 1:27 PM, Ian Hickson wrote:
The latter. The blocking only affects scripts that are prepare the
scripted by the top-level parser, not a reentrant parser.
OK. I see.
This requires the blocked by state to live on an individual script
instead of on the document, right?
I _think_
On 8/28/12 1:51 PM, Ian Hickson wrote:
I beg of you, let's not make it any more complicated. :-)
Amen. Just trying to catch up on what the state of things is now... ;)
-Boris
On Wed, 6 Jun 2012, Boris Zbarsky wrote:
Unless I'm mistaken, nothing in the HTML spec does anything
differently based on whether a script comes from document.write() or
not. The information about whether a character in the tokeniser came
from the network, document.write() during a
On 8/28/12 12:46 AM, Ian Hickson wrote:
I've updated the spec to not block on style sheets for nested parser's
scripts.
I'm not sure I follow. What is not going to block on what with this change?
As far as I can tell, 0 1 2 in your testcase at
On Thu, Jun 7, 2012 at 2:47 AM, Ian Hickson i...@hixie.ch wrote:
On Fri, 27 Jan 2012, Boris Zbarsky wrote:
On 1/27/12 1:30 AM, Ian Hickson wrote:
On Wed, 5 Oct 2011, Henri Sivonen wrote:
On Tue, Oct 4, 2011 at 9:54 PM, Boris Zbarskybzbar...@mit.edu wrote:
What Firefox does do is block
On Fri, 27 Jan 2012, Boris Zbarsky wrote:
On 1/27/12 1:30 AM, Ian Hickson wrote:
On Wed, 5 Oct 2011, Henri Sivonen wrote:
On Tue, Oct 4, 2011 at 9:54 PM, Boris Zbarskybzbar...@mit.edu wrote:
What Firefox does do is block execution ofscript tags (but not
timeouts, callbacks, etc!)
On 6/6/12 7:47 PM, Ian Hickson wrote:
On Fri, 27 Jan 2012, Boris Zbarsky wrote:
On 1/27/12 1:30 AM, Ian Hickson wrote:
On Wed, 5 Oct 2011, Henri Sivonen wrote:
On Tue, Oct 4, 2011 at 9:54 PM, Boris Zbarskybzbar...@mit.edu wrote:
What Firefox does do is block execution ofscript tags (but
On 1/27/12 1:30 AM, Ian Hickson wrote:
On Wed, 5 Oct 2011, Henri Sivonen wrote:
On Tue, Oct 4, 2011 at 9:54 PM, Boris Zbarskybzbar...@mit.edu wrote:
What Firefox does do is block execution ofscript tags (but not
timeouts, callbacks, etc!) if there are pending non-altenate
parser-inserted
On Tue, 4 Oct 2011, Julien Chaffraix wrote:
following WebKit's attempt at implementing the behavior of |sheet| and
|disabled| per HTML5 / CSSOM [1], we have found that the specs [2] [3]
either under-specify the behavior or do not match what browsers are
doing.
The spec has changed a bit
Thanks for the explanation. I took a black-box approach in testing - I
don't pretend to know how Firefox works - and from that perspective,
it looked like it was synchronous as the |sheet| was present and
properly populated in JS.
Try setting an interval to poll right before the link is
On 10/5/11 9:01 PM, Julien Chaffraix wrote:
Ah. Do they set disabled and expect it to take effect whenever the sheet
actually appears?
Yes, we have seen some regressions because people were expecting exactly that.
So for what it's worth, Gecko implemented the current behavior of
creating
Hi everyone,
following WebKit's attempt at implementing the behavior of |sheet| and
|disabled| per HTML5 / CSSOM [1], we have found that the specs [2] [3]
either under-specify the behavior or do not match what browsers are
doing.
Here are the behaviors seen during testing:
* IE9 does not support
On 10/4/11 2:41 PM, Julien Chaffraix wrote:
* However, FF loads the stylesheet synchronously whereas Opera does it
asynchronously from a JS perspective
Uh... Firefox does not load anything synchronously.
What Firefox does do is block execution of script tags (but not
timeouts, callbacks,
* However, FF loads the stylesheet synchronously whereas Opera does it
asynchronously from a JS perspective
Uh... Firefox does not load anything synchronously.
What Firefox does do is block execution of script tags (but not timeouts,
callbacks, etc!) if there are pending non-altenate
17 matches
Mail list logo
