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

[bugzilla-daemon at webkit.org]

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





--- Comment #24 from Naoki Takano <takano.naoki at gmail.com>  2011-05-16 22:14:00 PST ---
Tony, this is not autofill specific problem. It happens with your suggested test pattern.

Should I make another bug entry?

Thanks,

(In reply to comment #23)
> Ok, I'll make sure with some test code...
> 
> (In reply to comment #22)
> > (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.