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

[bugzilla-daemon at webkit.org]

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





--- Comment #28 from Elliott Sprehn <esprehn at chromium.org>  2013-02-11 13:35:19 PST ---
(In reply to comment #27)
> (In reply to comment #26)
> > (In reply to comment #24)
> > > How would you imagine such an API looking?
> > 
> > I think you want to hook a combination of FormAssociatedElement::resetFormOwner and FormAssociatedElement::didChangeForm. With some clean up we can probably make it so you only need to hook one of them.
> > 
> > Then I'd expose a new emedder hook in Editor like didAssociateInput.
> 
> That's not going to be sufficient. That can only inform us when a field is added to a form already existing on the document. If a new form is created, some fields added, and then placed inside a div. We need to know when the div is added to the document, and this won't give us that. Hence my earlier assertion that we potentially need to be informed of any node that gets added to the dom.

You can use FormAssociatedElement::insertedInto or HTMLFormElement::insertedInto to catch those cases. insertionPoint->inDocument() is true then.

Seems reasonable to have a formAdded notification as well. These things may not make sense in EditorClient (though for now it seems okay).

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