RESOLVED FIXED 102645
input.value="" should clear date/time input elements with partial values
https://bugs.webkit.org/show_bug.cgi?id=102645
Summary input.value="" should clear date/time input elements with partial values
Kent Tamura
Reported 2012-11-18 22:24:53 PST
crbug.com/161443 If a page has <input type=date> with ENABLE_INPUT_MULTIPLE_FIELDS_UI and a user specifies a number only in one or two subfields (like [mm/13/yyyy]), input.value="" should clear the number.
Attachments
Patch (21.24 KB, patch)
2012-11-18 23:04 PST, Kent Tamura
no flags
Patch for landing (21.13 KB, patch)
2012-11-19 01:37 PST, Kent Tamura
no flags
Kent Tamura
Comment 1 2012-11-18 23:04:56 PST
WebKit Review Bot
Comment 2 2012-11-18 23:50:53 PST
Comment on attachment 174897 [details] Patch Attachment 174897 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/14894085 New failing tests: inspector-protocol/debugger-terminate-dedicated-worker-while-paused.html
Kentaro Hara
Comment 3 2012-11-19 00:58:25 PST
Comment on attachment 174897 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=174897&action=review > Source/WebCore/ChangeLog:8 > + Additional information of the change such as approach, rationale. Please add per-function descriptions below (OOPS!). Please add it. > Source/WebCore/ChangeLog:20 > + If the new value is an empty string and sub-fields has values, we should > + update the UI value to the empty state. I want to understand this behavior more. What happens if you update the UI value to an empty state whenever the new value is an empty string?
Kent Tamura
Comment 4 2012-11-19 01:06:01 PST
Comment on attachment 174897 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=174897&action=review >> Source/WebCore/ChangeLog:8 >> + Additional information of the change such as approach, rationale. Please add per-function descriptions below (OOPS!). > > Please add it. oops. I'll remove this line because the per-function comments are enough. >> Source/WebCore/ChangeLog:20 >> + update the UI value to the empty state. > > I want to understand this behavior more. What happens if you update the UI value to an empty state whenever the new value is an empty string? It's ok too. However I'd like to avoid unnecessary UI update as possible because updateInnerTextValue is an expensive operation.
Kentaro Hara
Comment 5 2012-11-19 01:27:33 PST
Comment on attachment 174897 [details] Patch Thanks for the clarification. Makes sense to me.
Kent Tamura
Comment 6 2012-11-19 01:37:02 PST
Created attachment 174913 [details] Patch for landing
WebKit Review Bot
Comment 7 2012-11-19 02:08:44 PST
Comment on attachment 174913 [details] Patch for landing Clearing flags on attachment: 174913 Committed r135131: <http://trac.webkit.org/changeset/135131>
WebKit Review Bot
Comment 8 2012-11-19 02:08:51 PST
All reviewed patches have been landed. Closing bug.
Kentaro Hara
Comment 9 2012-11-19 05:06:44 PST
I rebaselined the test result for Win in r135139. I think the rebaseline would be OK but I'd be happy if you could check it.
Kentaro Hara
Comment 10 2012-11-19 05:44:39 PST
Another rebaselining in r135147. (Maybe more rebaselining is needed. I'm leaving now:-)
Kent Tamura
Comment 11 2012-11-19 06:07:50 PST
Thank you for the rebaseline. Yeah, these test results can be platform-dependent because of locale data differences.
Note You need to log in before you can comment on or make changes to this bug.