When implementing :scope support, I discovered that as things stand this
call:
document.querySelector(":scope")
is specified to return null. In particular
http://dev.w3.org/2006/webapi/selectors-api2/#queryselector step 1 calls
http://dev.w3.org/2006/webapi/selectors-api2/#determine-contex
On Thu, Nov 29, 2012 at 4:31 PM, Ian Hickson wrote:
> On Tue, 17 Jul 2012, Ian Hickson wrote:
> >
> > My plan is to make it so that cross-origin URLs start cross-origin
> > workers. The main unresolved question is how to do this in an opt-in
> > manner. The best idea I've come up with so far is h
On Tue, 17 Jul 2012, Ian Hickson wrote:
>
> My plan is to make it so that cross-origin URLs start cross-origin
> workers. The main unresolved question is how to do this in an opt-in
> manner. The best idea I've come up with so far is having scripts that
> want to opt-in to being run in such a w
On Wed, Nov 28, 2012 at 2:51 PM, Maciej Stachowiak wrote:
>
> Does this support the previously discussed mechanism of allowing either
> public or private components? I'm not able to tell from the referenced
> sections.
>
Can you explain the use case for wanting private shadows that are not
isola
On Wed, Nov 28, 2012 at 4:10 PM, David Bruant wrote:
>
> >> One downside of this is that it means that if you're doing a bunch of
> >> separate read/write operations in separate locks, each lock is held
> >> until we've had a chance to fire the final success event for the
> >> operation. So if you
On 2012-11-25 16:19, Ms2ger wrote:
> On 11/25/2012 02:49 PM, Arthur Barstow wrote:
>> This is Call for Consensus to publish a Working Draft of the DOM spec
>> using #ED as the basis.
>
> Same objections as to the XHR WD.
>From your XHR objection:
> I object unless the draft contains a clear poin
