[Webkit-unassigned] [Bug 32261] Add ability to specify suggested autocomplete value in HTMLInputElement

[bugzilla-daemon at webkit.org]

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





--- Comment #15 from Zelidrag Hornung <zelidrag at chromium.org>  2009-12-10 10:12:23 PST ---
>From John's comments, there are two issues that need to be answered here:

a) Accepting autocomplete suggestion on focus lost. The current implementation
proposal in the attachment will (for Chromium only) indeed turn suggestion into
the input element's value on focus lost. I am open to suggestion about what
makes more sense than that, but IMO this seemed like the most natural behavior
from UX perspective. Alternatively, we could potentially require users to press
enter to explicitly accept the suggestion or identify focus lost cases where
that transition won't happen. It is also true that the site could trigger focus
change and get the suggestion turned into the element's value, but the site's
JS code has no way of knowing if a particular filed is in the suggestion mode
at all. So, it would really be a crap shooting for a site to get such value. We
could still stem this issue by not transferring the value at least in a case
when JS call caused the focus lost.

b) UI inconsistencies. The field will actually look different, to the certain
degree, in suggest mode case - the added/suggested part of the value will
actually have a text selection there. Once the value is accepted, the selection
goes away. We could further mitigate page look/behaving inconsistency here by
modifying rendering. That will most likely be browser specific. For Chromium,
we could simply use a different coloring scheme, similar what we do for
autofill.

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