[Webkit-unassigned] [Bug 60010] [Chromium]Add clear_autofill flag to hide autofill popup without clear field.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon May 16 11:57:40 PDT 2011


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


Tony Chang <tony at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tony at chromium.org




--- Comment #22 from Tony Chang <tony at chromium.org>  2011-05-16 11:57:39 PST ---
(In reply to comment #16)
> Maciej, the code revision history tells me you might be familiar with the drag&drop code.  Could you weigh in on this patch and the related Chromium one, http://codereview.chromium.org/6902196/ ?
> 
> Here's a quick summary of the problem, as I understand it:
>   (1) We initiate a drag event for "suggested" (uncommitted) Autofill text in a text field.
>   (2) This drag should cause the text to be committed.
>   (3) When the text is committed, the "suggested" text is cleared; but it is still referenced in the drag state.
>   (4) When the corresponding drop event occurs, we hit an assertion because the referenced selection is orphaned.
> 
> Do you have any suggestions on how to handle this somewhat unusual situation?

Is this problem specific to Autofill?  For example, if I select and drag text and a dom event fires (e.g., ondragenter) and removes the text I'm dragging, do we hit the same assertion?

If so, this might be a bug that needs to be fixed separately.

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



More information about the webkit-unassigned mailing list