RESOLVED FIXED Bug 84677
Clickable area of a calendar picker indicator is too small 
https://bugs.webkit.org/show_bug.cgi?id=84677
Summary Clickable area of a calendar picker indicator is too small
Kent Tamura
Reported 2012-04-24 00:56:00 PDT
Clickable area of a calendar picker indicator '▼' is too small.
Attachments
Patch (1.56 KB, patch)
2012-04-24 01:00 PDT, Kent Tamura 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Kent Tamura
Comment 1 2012-04-24 01:00:31 PDT
Created attachment 138511 [details] Patch
Kentaro Hara
Comment 2 2012-04-24 04:15:27 PDT
Comment on attachment 138511 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=138511&action=review > Source/WebCore/ChangeLog:8 > + Test: fast/forms/date/date-appearance.html is affected. Isn't there any test update?
Kent Tamura
Comment 3 2012-04-24 06:23:35 PDT
Comment on attachment 138511 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=138511&action=review >> Source/WebCore/ChangeLog:8 >> + Test: fast/forms/date/date-appearance.html is affected. > > Isn't there any test update? Fortunately(?), date-appearance.html already has a failure entry in test_expectations.txt.
Kentaro Hara
Comment 4 2012-04-24 06:25:20 PDT
Comment on attachment 138511 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=138511&action=review rs=me >>> Source/WebCore/ChangeLog:8 >>> + Test: fast/forms/date/date-appearance.html is affected. >> >> Isn't there any test update? > > Fortunately(?), date-appearance.html already has a failure entry in test_expectations.txt. Got it.
Kent Tamura
Comment 5 2012-04-24 06:32:25 PDT
Comment on attachment 138511 [details] Patch Thanks!
WebKit Review Bot
Comment 6 2012-04-24 07:47:42 PDT
Comment on attachment 138511 [details] Patch Clearing flags on attachment: 138511 Committed r115052: <http://trac.webkit.org/changeset/115052>
WebKit Review Bot
Comment 7 2012-04-24 07:47:47 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.