Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-20 Thread Anne van Kesteren
On Tue, Jun 19, 2012 at 10:52 PM, Olli Pettay olli.pet...@helsinki.fi wrote: end-of-microtask or end-of-task everywhere. And yes, some parsing / networking details may unfortunately be exposed, but in a way which should be quite random. Web devs just can't really rely on network packages to be

Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-20 Thread Ryosuke Niwa
On Tue, Jun 19, 2012 at 1:52 PM, Olli Pettay olli.pet...@helsinki.fiwrote: Ojan points out that simply using end-of-task could expose low-level implementation detail of the parser to script (such as how much parsing is done in a single task before the parser yields). Does Firefox do

Re: [IndexedDB] Origins and document.domain

2012-06-20 Thread Anne van Kesteren
On Wed, Jun 20, 2012 at 6:06 AM, Kyle Huey m...@kylehuey.com wrote: By my reading, the spec does not clearly specify what the 'origin' should be.  IDBFactory.open/deleteDatabase say Let origin be the origin of the IDBEnvironment used to access this IDBFactory.  The IDL states Window implements

Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-20 Thread Olli Pettay
On 06/20/2012 10:36 AM, Ryosuke Niwa wrote: On Tue, Jun 19, 2012 at 1:52 PM, Olli Pettay olli.pet...@helsinki.fi mailto:olli.pet...@helsinki.fi wrote: Ojan points out that simply using end-of-task could expose low-level implementation detail of the parser to script (such as how

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Charles McCathieNevile
On Wed, 20 Jun 2012 06:19:22 +0200, Elliott Sprehn espr...@gmail.com wrote: On Tue, Jun 19, 2012 at 1:38 PM, Tab Atkins Jr. jackalm...@gmail.comwrote: ... This is not a good argument. qSA is used often enough, and has a long enough name, that the name is actually a pretty significant

Web Notifications

2012-06-20 Thread Anne van Kesteren
Hi, The Web Notifications WG is planning to move Web Notifications to W3C Last Call meaning we don't intend to change it. But we might have missed something and would therefore appreciate your review of http://dvcs.w3.org/hg/notifications/raw-file/tip/Overview.html and any comments you might have

Re: Web Notifications

2012-06-20 Thread Melvin Carvalho
On 20 June 2012 10:58, Anne van Kesteren ann...@annevk.nl wrote: Hi, The Web Notifications WG is planning to move Web Notifications to W3C Last Call meaning we don't intend to change it. But we might have missed something and would therefore appreciate your review of

Re: Web Notifications

2012-06-20 Thread Olli Pettay
On 06/20/2012 11:58 AM, Anne van Kesteren wrote: Hi, The Web Notifications WG is planning to move Web Notifications to W3C Last Call meaning we don't intend to change it. But we might have missed something and would therefore appreciate your review of

Re: CfC: Publish FPWD of Web Intents spec; deadline June 12

2012-06-20 Thread Robin Berjon
On Jun 19, 2012, at 13:29 , Arthur Barstow wrote: Dave - it appears this CfC passed. Unless I hear otherwise from you, I will assume DAP will take care of the Transition Request and Publication Request. Yes, we'll take care of that. The draft will be published under joint ownership between

Tags and origins (was: Re: Web Notifications)

2012-06-20 Thread Anne van Kesteren
On Wed, Jun 20, 2012 at 12:17 PM, Olli Pettay olli.pet...@helsinki.fi wrote: Seems like tags are global. I think they should be per origin. Yes I believe they should be. http://dvcs.w3.org/hg/notifications/rev/563e9af218b9 Thanks, -- Anne — Opera Software http://annevankesteren.nl/

Re: Tags and origins (was: Re: Web Notifications)

2012-06-20 Thread Charles McCathieNevile
On Wed, 20 Jun 2012 14:30:08 +0200, Anne van Kesteren ann...@annevk.nl wrote: On Wed, Jun 20, 2012 at 12:17 PM, Olli Pettay olli.pet...@helsinki.fi wrote: Seems like tags are global. I think they should be per origin. Yes I believe they should be.

Re: Tags and origins (was: Re: Web Notifications)

2012-06-20 Thread Anne van Kesteren
On Wed, Jun 20, 2012 at 3:03 PM, Charles McCathieNevile cha...@opera.com wrote: In the default case yes. Can you use something to change that (a la from-origin)? I don't really see how. Do you have an example where it makes sense? -- Anne — Opera Software http://annevankesteren.nl/

Re: Tags and origins (was: Re: Web Notifications)

2012-06-20 Thread John Gregg
On Wed, Jun 20, 2012 at 5:30 AM, Anne van Kesteren ann...@annevk.nl wrote: On Wed, Jun 20, 2012 at 12:17 PM, Olli Pettay olli.pet...@helsinki.fi wrote: Seems like tags are global. I think they should be per origin. Yes I believe they should be.

Re: Tags and origins (was: Re: Web Notifications)

2012-06-20 Thread Anne van Kesteren
On Wed, Jun 20, 2012 at 3:25 PM, John Gregg john...@google.com wrote: Can we either go back to the original language where in the showing algorithm you compare both tag and origin (add origin to the model), Sure. http://dvcs.w3.org/hg/notifications/rev/93c6983ce465 -- Anne — Opera Software

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Lachlan Hunt
On 2012-06-20 10:42, Charles McCathieNevile wrote: In other words we have the same arguments that we had five years ago, when we settled on querySelector as the one that provoked least objection. ... But spending another few months arguing about it hasn't proven that we are any wiser, nor

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Marat Tanalin | tanalin . com
20.06.2012, 18:26, Lachlan Hunt lachlan.h...@lachy.id.au: In particular, is there really value in adding two distinct methods that differ only by whether they return 1 element or a collection?  Resolving this issue first would help with resolving the naming issue. It should be noted that

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Dave Methvin
It should be noted that JQuery/sizzle does not use querySelector() at all, AFAICS. It only uses querySelectorAll() and sometimes switches to .getElementById() or document.body. I took a look at using querySelector as an optimization a while back but it did not seem to make a significant

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Marat Tanalin | tanalin . com
20.06.2012, 18:14, Lachlan Hunt lachlan.h...@lachy.id.au: 4. Support for returning elements that are not descendants of the context object. This feature allows a selector to be constructed such that it matches an element anywhere in the tree relative to the context element. This feature

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Boris Zbarsky
On 6/20/12 10:52 AM, Dave Methvin wrote: This test html is based on the msn.com http://msn.com home page to be representative of a big real-life document. For what it's worth, that document has about 2200 DOM nodes. That's two orders of magnitude smaller than big real-life documents. This

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Boris Zbarsky
On 6/20/12 11:34 AM, Marat Tanalin | tanalin.com wrote: It's natural to suppose that searching for just _first_ matching element and returning immediately once it's found should be much _faster_ than searching for _all_ matching elements (be it 100 or 1000 elements) even if we need just first

Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-20 Thread Adam Klein
On Wed, Jun 20, 2012 at 12:36 AM, Ryosuke Niwa rn...@webkit.org wrote: On Tue, Jun 19, 2012 at 1:52 PM, Olli Pettay olli.pet...@helsinki.fiwrote: Ojan points out that simply using end-of-task could expose low-level implementation detail of the parser to script (such as how much parsing is

Re: Web Notifications

2012-06-20 Thread Andrew Wilson
On Wed, Jun 20, 2012 at 3:17 AM, Olli Pettay olli.pet...@helsinki.fi wrote: On 06/20/2012 11:58 AM, Anne van Kesteren wrote: Hi, The Web Notifications WG is planning to move Web Notifications to W3C Last Call meaning we don't intend to change it. But we might have missed something and would

Re: Web Notifications

2012-06-20 Thread Andrew Wilson
On Wed, Jun 20, 2012 at 2:36 PM, Andrew Wilson atwil...@google.com wrote: On Wed, Jun 20, 2012 at 3:17 AM, Olli Pettay olli.pet...@helsinki.fi wrote: On 06/20/2012 11:58 AM, Anne van Kesteren wrote: Hi, The Web Notifications WG is planning to move Web Notifications to W3C Last Call meaning

Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-20 Thread Ryosuke Niwa
On Wed, Jun 20, 2012 at 1:33 PM, Adam Klein ad...@chromium.org wrote: On Wed, Jun 20, 2012 at 12:36 AM, Ryosuke Niwa rn...@webkit.org wrote: On Tue, Jun 19, 2012 at 1:52 PM, Olli Pettay olli.pet...@helsinki.fiwrote: Ojan points out that simply using end-of-task could expose low-level

Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-20 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: I can't think of any cases where you would *not* want these to fire for parser mutations. For example if you are building an XBL-like widget library which uses the DOM under a node to affect behavior or rendering of some other object. If you attach the widget before the