On Feb 12, 2014, at 11:23 AM, Rafael Weinstein rafa...@google.com wrote:
I pushed the Web Components folks about exactly this issue (why aren't these
callbacks just MutationObservers?) early last year. They convinced me (and I
remain convinced) that these signals should be Custom Element
On 02/12/2014 04:27 AM, Ryosuke Niwa wrote:
On Feb 11, 2014, at 6:06 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote:
* Olli Pettay wrote:
We could add some scheduling thing to mutation observers. By default we'd use
microtask, since that tends to be good for various performance
reasons, but
I pushed the Web Components folks about exactly this issue (why aren't
these callbacks just MutationObservers?) early last year. They convinced me
(and I remain convinced) that these signals should be Custom Element
callbacks and not Mutation Observer records
Here's the logic that convinced me:
On Feb 12, 2014, at 11:23 AM, Rafael Weinstein rafa...@google.com wrote:
I pushed the Web Components folks about exactly this issue (why aren't these
callbacks just MutationObservers?) early last year. They convinced me (and I
remain convinced) that these signals should be Custom Element
On Wed, Feb 12, 2014 at 2:08 PM, Ryosuke Niwa rn...@apple.com wrote:
On Feb 12, 2014, at 11:23 AM, Rafael Weinstein rafa...@google.com wrote:
In a certain sense, you can extend the argument that CE callbacks should be
MO records, and you arrive at the conclusion that you don't need Custom
On Feb 12, 2014, at 2:33 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Feb 12, 2014 at 2:08 PM, Ryosuke Niwa rn...@apple.com wrote:
On Feb 12, 2014, at 11:23 AM, Rafael Weinstein rafa...@google.com wrote:
In a certain sense, you can extend the argument that CE callbacks should be
MO
On 02/12/2014 03:41 AM, Ryosuke Niwa wrote:
Hi,
I’m bringing this up out of:
[Custom]: enteredView and leftView callbacks are still confusing
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24314
Could someone clarify exactly why mutation observers can’t satisfy use cases
for custom elements?
* Olli Pettay wrote:
We could add some scheduling thing to mutation observers. By default
we'd use microtask, since that tends to be good for various performance
reasons, but normal tasks or nanotasks could be possible too.
This sounds like adding a switch that would dynamically invalidate
On Feb 11, 2014, at 6:06 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote:
* Olli Pettay wrote:
We could add some scheduling thing to mutation observers. By default
we'd use microtask, since that tends to be good for various performance
reasons, but normal tasks or nanotasks could be
On Feb 11, 2014, at 6:27 PM, Ryosuke Niwa rn...@apple.com wrote:
On Feb 11, 2014, at 6:06 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote:
* Olli Pettay wrote:
We could add some scheduling thing to mutation observers. By default
we'd use microtask, since that tends to be good for various
Are you proposing new mutation record type? I think that could handle
most of the enter/leave requirements.
observer.observe(target, { element: 'x-foo' });
If MutationObservers are an open topic for extension, I'd love to see
generic css selector support.
observer.observe(target, {
On Feb 11, 2014, at 8:41 PM, Joshua Peek j...@joshpeek.com wrote:
Are you proposing new mutation record type? I think that could handle
most of the enter/leave requirements.
Not really. I’m mostly talking about new timing at which mutation records are
delivered.
Apparently we need to deliver
12 matches
Mail list logo
