[Webkit-unassigned] [Bug 105337] Expose mutation observers to chromium

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=105337





--- Comment #24 from Dane Walllinga <dgwallinga at chromium.org>  2013-01-17 15:39:23 PST ---
How would you imagine such an API looking? The specific things we'd need to be able to detect for autofill are new forms, new fields on an existing form, reordering of existing fields, and changes to the name of an existing field. In practice, I would imagine (don't have data at hand) we'd mainly have to worry about the first two, but some sites do some weird stuff, and changes to the name attribute could definitely come up. My worry is that I'd basically have to re-implement MutationObservers - perhaps a lighter weight version, but still touching a fair amount of code in WebCore. One of my goals was to avoid having to make changes outside of WebKit/chromium, since this is for a chrome-only feature, but maybe that's not feasible?

Out of curiosity, do you know why DOMMutationEvent was exposed to chromium? I know that's no longer going to be supported at some point, but you can do basically the same things you could with MutationObservers, but with even worse performance.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.