http://www.w3.org/Bugs/Public/show_bug.cgi?id=14214
Glenn Adams gl...@skynav.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
On Thu, Oct 20, 2011 at 2:33 PM, Lachlan Hunt lachlan.h...@lachy.id.au
wrote:
Not necessarily. It depends what exactly it means for a selector to
contain
:scope for determining whether or not to enable the implied :scope
behaviour. Consider:
foo.find(:not(:scope));
Ooh, this is an
Hi,
Based on the ongoing discussion, I've put together the following list
of requirements and sumarised use cases that should be met by the design
of new features in selectors API.
*Use Cases*
1. Select elements that are descendants of specific Element node, where
all elements matched by
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14530
Summary: Hi, In Server-Sent Events Section Processing model,
it should be clearly stated how to avoid the
pipelining of HTTP requests on the connection used for
an event
On Oct 20, 2011, at 4:34 PM, Tab Atkins Jr. wrote:
On Thu, Oct 20, 2011 at 12:09 PM, Jonas Sicking jo...@sicking.cc wrote:
Let's do the general discussion about how live and non-live NodeLists
should behave in a separate thread.
Yes, let's. ^_^
The immediate question here is how
On Thu, 20 Oct 2011 16:39:56 +0200, Igor Oliveira
igor.olive...@openbossa.org wrote:
Hello,
Currently CSSMatrix and SVGMatrix has an immutable API. None of the
method calls change the Matrix, instead, it creates a new Matrix with
the changed value. It can be a problem specially when
On 10/21/11 11:28 AM, João Eiras wrote:
On Thu, 20 Oct 2011 16:39:56 +0200, Igor Oliveira
igor.olive...@openbossa.org wrote:
Hello,
Currently CSSMatrix and SVGMatrix has an immutable API. None of the
method calls change the Matrix, instead, it creates a new Matrix with
the changed value. It
On Fri, Oct 21, 2011 at 11:28 AM, João Eiras jo...@opera.com wrote:
On Thu, 20 Oct 2011 16:39:56 +0200, Igor Oliveira
igor.olive...@openbossa.org wrote:
Hello,
Currently CSSMatrix and SVGMatrix has an immutable API. None of the
method calls change the Matrix, instead, it creates a new
Thanks for the information!
My understanding is that browsers have already been delivering streamed
responses in chunks (Transfer-Encoding), so it makes a lot of sense to
expose such a semantics explicitly through the XHR2 API.
Streamed requests are equally important, e.g. for use cases such as
On 20/10/11 10:39 AM, Igor Oliveira wrote:
Currently CSSMatrix and SVGMatrix has an immutable API. None of the
method calls change the Matrix, instead, it creates a new Matrix with
the changed value. It can be a problem specially when CSSMatrix is
used together with WebGL. [1]
SVGMatrix is not
Hi Art, all,
On 10/14/2011 09:27 PM, Arthur Barstow wrote:
The people working on the D3E spec (namely Jacob, Doug and Olli) propose
below that the spec be published as a Candidate Recommendation and this
is a CfC to do so:
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14364
Ian 'Hixie' Hickson i...@hixie.ch changed:
What|Removed |Added
Status|NEW |RESOLVED
On 20/10/11 12:39 AM, Timmy Willison wrote:
From the perspective of building a selector engine, I think all
selector engines need something like .findAll, and not something like
:scope.
On Tue, Oct 18, 2011 at 8:00 PM, Alex Russell slightly...@google.com
mailto:slightly...@google.com wrote:
13 matches
Mail list logo