On Wed, Aug 11, 2010 at 7:06 AM, Maciej Stachowiak m...@apple.com wrote:
On Aug 9, 2010, at 8:21 PM, Timothy Hatcher wrote:
Adding input/beforeinput events (#3) wont solve the need of most
extension developers that use mutation events today (the examples you cite).
So that makes it hard to
On Wed, Aug 18, 2010 at 2:31 PM, Ojan Vafai o...@chromium.org wrote:
My intuition is that very few sites or extensions actually depend on them
being synchronous.
I agree. I worked on some extension app this spring but all I needed to know
was when the subtree of certain nodes change so that I
On Aug 9, 2010, at 8:21 PM, Timothy Hatcher wrote:
On Aug 9, 2010, at 7:52 PM, Dimitri Glazkov wrote:
I am very, very tempted to just get rid of them. As Ojan indicated,
the use cases for DOM Mutation events are extremely limited and to me,
most of them feel like we should be solving them
On Mon, Aug 9, 2010 at 9:28 PM, Geoffrey Garen gga...@apple.com wrote:
As Ojan indicated,
the use cases for DOM Mutation events are extremely limited and to me,
most of them feel like we should be solving them differently anyway.
This is the question I'm most interested in.
You say the use
On Thu, Aug 5, 2010 at 2:22 AM, Adam Barth aba...@webkit.org wrote:
On Thu, Aug 5, 2010 at 1:59 AM, Maciej Stachowiak m...@apple.com wrote:
If mutation events tend to break editing, one simple solution is to turn
then off within the scope of editing operations and send a single mutation
On Mon, Aug 9, 2010 at 4:39 PM, Ojan Vafai o...@chromium.org wrote:
On Thu, Aug 5, 2010 at 2:22 AM, Adam Barth aba...@webkit.org wrote:
On Thu, Aug 5, 2010 at 1:59 AM, Maciej Stachowiak m...@apple.com wrote:
If mutation events tend to break editing, one simple solution is to turn
then off
Hi Ojan.
Mutation events are a huge source of crashes and they complicate WebCore code
considerably.
Indeed. I also think mutation events unnecessarily complicate the API space
from a web content author's perspective.
Also, I don't see any evidence that mutation events are used much other
I am very, very tempted to just get rid of them. As Ojan indicated,
the use cases for DOM Mutation events are extremely limited and to me,
most of them feel like we should be solving them differently anyway.
However, with the introduction of extensions into Chromium and Safari,
DOM Mutation
On Aug 9, 2010, at 7:52 PM, Dimitri Glazkov wrote:
I am very, very tempted to just get rid of them. As Ojan indicated,
the use cases for DOM Mutation events are extremely limited and to me,
most of them feel like we should be solving them differently anyway.
However, with the introduction
As Ojan indicated,
the use cases for DOM Mutation events are extremely limited and to me,
most of them feel like we should be solving them differently anyway.
This is the question I'm most interested in.
You say the use cases are limited. How do you know? Are you speaking about when
you
10 matches
Mail list logo
