Can we disallow mutation events inside shadow DOM?
There is no legacy content that depends on mutation events API inside
shadow DOM, and we have a nice spec implementation of new mutation
observer API already.
FYI, https://bugs.webkit.org/show_bug.cgi?id=79278
Best,
Ryosuke Niwa
Software
On 02/24/2012 01:38 AM, Ryosuke Niwa wrote:
Can we disallow mutation events inside shadow DOM?
Sounds good to me.
Whatever shadow dom spec will be implemented, mutation events shouldn't
fire there. Mutation observers should work.
-Olli
There is no legacy content that depends on mutation
Sounds good. Filed a bug here:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16096
:DG
On Thu, Feb 23, 2012 at 3:38 PM, Ryosuke Niwa rn...@webkit.org wrote:
Can we disallow mutation events inside shadow DOM?
There is no legacy content that depends on mutation events API inside shadow
DOM,
Just to be clear on this: what is the status of mutation observers? If
there any chance shadow dom beats mutation observers to standardization? I
don't think so, but just checking... If that turned out to be the case it
could be crippling shadow dom until such a time..
Brian
On Feb 23, 2012
On 02/24/2012 02:10 AM, Brian Kardell wrote:
Just to be clear on this: what is the status of mutation observers?
They are in DOM 4. The API may still change a bit, but
there is already one implementation, and another one close to
ready.
If
there any chance shadow dom beats mutation
On Thu, Feb 23, 2012 at 4:10 PM, Brian Kardell bkard...@gmail.com wrote:
Just to be clear on this: what is the status of mutation observers? If
there any chance shadow dom beats mutation observers to standardization? I
don't think so, but just checking... If that turned out to be the case
Yeah that was pretty much my feeling but always worth checking.
On Feb 23, 2012 7:13 PM, Olli Pettay olli.pet...@helsinki.fi wrote:
On 02/24/2012 02:10 AM, Brian Kardell wrote:
Just to be clear on this: what is the status of mutation observers?
They are in DOM 4. The API may still change a
