On 2012-11-30 03:01, Boris Zbarsky wrote:
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
Just a reminder: this group is a forum for discussion of technical
specifications, and follows the existing W3C process. Discussion of what
process *should* be is off topic here.
On Sun, 02 Dec 2012 12:07:20 +0100, Jungkee Song jungk...@gmail.com
wrote:
On Sun, Dec 2, 2012 at 11:07 AM,
On 12/03/2012 01:44 PM, Charles McCathie Nevile wrote:
Just a reminder: this group is a forum for discussion of technical
specifications, and follows the existing W3C process. Discussion of what
process *should* be is off topic here.
I find it unfortunate that you try to cut off discussions
On 12/3/12 7:33 AM, Lachlan Hunt wrote:
So it seems the current spec ended up treating these in
the same way by matching nothing:
document.querySelector(:scope)
document.findAll(:scope)
document.findAll(:scope, null)
document.findAll(:scope, [])
That's how I read it, yes.
I can change the
When were you thinking of kicking off the DOM4 Events process?
I'd like to have a draft up this week. We may also ask for a FPWD if we're
ready by the 10th.
I want to have D4E rolling so that stuff we chose to punt from D3E has a
landing pad.
From: gary...@google.com
On Mon, Dec 3, 2012 at 9:48 AM, Travis Leithead
travis.leith...@microsoft.com wrote:
When were you thinking of kicking off the DOM4 Events process?
** **
I'd like to have a draft up this week. We may also ask for a FPWD if we're
ready by the 10th.
** **
I want to have D4E
Sorry for the late response.
Adding more create* methods feels like a bug. I understand that there are
a couple of concerns/arguments here:
- Current implementations that aren't self-hosting are going to have
trouble with the idea of unattached (floating) ShadowRoot instances
- As a
From: Ian Hickson [mailto:i...@hixie.ch]
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
On Sat, 1 Dec 2012, Ms2ger wrote:
I object to this publication because of this change:
http://dvcs.w3.org/hg/xhr/rev/2341e31323a4
I agree. That change is offensive. It gives credit to dozens of people who
have done basically nothing productive at all, for work that a few of us
have spent
This is a list of typos and other minor formatting problems that I
encountered while going through the current DOM Level 3 Event spec. A few
of the things listed here are actual errors, but the majority fall into two
categories:
* Initial capital letter missing at the start of a note or warning.
*
10 matches
Mail list logo
