Re: [whatwg] HTMLLinkElement.disabled and HTMLLinkElement.sheet behavior

2011-10-05 Thread Julien Chaffraix
>> 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 is

Re: [whatwg] HTMLLinkElement.disabled and HTMLLinkElement.sheet behavior

2011-10-04 Thread Julien Chaffraix
>> * 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

[whatwg] HTMLLinkElement.disabled and HTMLLinkElement.sheet behavior

2011-10-04 Thread Julien Chaffraix
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

[whatwg] EventSource - Handling a charset in the content-type header

2011-03-23 Thread Julien Chaffraix
Hi, the EventSource specification states the current content-type header should match the string "text/event-stream". However following some bugs opened inside the WebKit project [1], we relaxed the content-type check to ignore any specified charset as it confused developers and can potentially br