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

[bugzilla-daemon at webkit.org]

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


Adam Barth <abarth at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #180057|review?                     |review-
               Flag|                            |




--- Comment #15 from Adam Barth <abarth at webkit.org>  2013-01-14 13:38:30 PST ---
(From update of attachment 180057)
> We'll need to create mutation observers for a whitelisted set of web pages belonging to multipage autofill flows (for a related bug on the chromium side, maybe check https://codereview.chromium.org/11539003/). Basically we need to be able to support autofill behavior on pages with ajax-y stuff, which means knowing when dom changes happen so we can query the autofill server again. Initially maybe around 20 sites, though potentially more going forward. You are correct that this could have some performance impact on dom operations, but the improvements to autofill should speed up the user experience overall.

This approach sounds problematic.  What happens when we expand beyond this whitelisted set of sites?

Perhaps WebKit should provide more detailed callbacks to notify you of when things of interest happen in a web page.  MutationObserver sounds like too general a mechanism for your needs.

I wonder if we should think more carefully about how to divide the implementation of this feature between WebKit and Chromium.

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