On Mon, Mar 4, 2013 at 8:14 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 4 Mar 2013, Anne van Kesteren wrote:
1) How does HTML distinguish for which fetch the tasks are queued?
How do you mean?
What I meant was that when loading a page, various APIs will start
invoking fetch. That in turn
I'm trying to understand why Document and HTMLDocument got merged. In
practice, UAs don't do that, and doing it imposes a performance penalty
on manipulating, say, XMLHttpRequest response documents (because the
name getter on HTMLDocument makes property access slower on that object).
So why
On Tue, Mar 5, 2013 at 4:38 PM, Boris Zbarsky bzbar...@mit.edu wrote:
I'm trying to understand why Document and HTMLDocument got merged. In
practice, UAs don't do that, and doing it imposes a performance penalty on
manipulating, say, XMLHttpRequest response documents (because the name
getter
On 3/5/13 11:45 AM, Anne van Kesteren wrote:
On Tue, Mar 5, 2013 at 4:38 PM, Boris Zbarsky bzbar...@mit.edu wrote:
I'm trying to understand why Document and HTMLDocument got merged. In
practice, UAs don't do that, and doing it imposes a performance penalty on
manipulating, say, XMLHttpRequest
On Tue, Mar 5, 2013 at 4:50 PM, Boris Zbarsky bzbar...@mit.edu wrote:
I don't care about the methods. Putting all of those on Document is fine by
me, I think.
I care about the named getter being forced onto all documents.
Okay, so that is slightly different from how this thread started out.
On Tue, 5 Mar 2013, Boris Zbarsky wrote:
On 3/5/13 11:59 AM, Anne van Kesteren wrote:
On Tue, Mar 5, 2013 at 4:50 PM, Boris Zbarsky bzbar...@mit.edu
wrote:
I don't care about the methods. Putting all of those on Document is
fine by me, I think.
I care about the named getter
On 3/5/13 3:30 PM, Ian Hickson wrote:
I'd be fine with having a Document descendant that is used for Documents
that have global scopes / browsing contexts / the works, and one that is
used for Documents that don't (e.g. createDocument(), XHR); would that
address this issue?
It's one way to
On Tue, Mar 5, 2013 at 12:42 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 3/5/13 3:30 PM, Ian Hickson wrote:
I'd be fine with having a Document descendant that is used for Documents
that have global scopes / browsing contexts / the works, and one that is
used for Documents that don't (e.g.
On Mon, Mar 4, 2013 at 11:33 AM, L. David Baron dba...@dbaron.org wrote:
You could make the same argument against most of @scoped: you don't need
to
define a scoped style for a class, just use a different class name.
I think for the rest of @scoped, there are both significant
performance
