Bug 43760 - [GTK] Inputs of type 'search' have weird looking checkboxes instead of search/clear icons
Summary: [GTK] Inputs of type 'search' have weird looking checkboxes instead of search...
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
Keywords: Gtk
Depends on:
Reported: 2010-08-09 17:08 PDT by Gustavo Noronha (kov)
Modified: 2010-08-11 16:21 PDT (History)
1 user (show)

See Also:

proposed patch (3.27 KB, patch)
2010-08-09 17:13 PDT, Gustavo Noronha (kov)
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo Noronha (kov) 2010-08-09 17:08:14 PDT
Subject says it all. If you have, say, <input type="search" results="0"> this should be drawing a nice search icon in the left corner of the entry, and a clear icon in the right corner, when something is entered, but we get weird checkboxes instead.
Comment 1 Gustavo Noronha (kov) 2010-08-09 17:13:39 PDT
Created attachment 63958 [details]
proposed patch
Comment 2 Xan Lopez 2010-08-10 08:36:07 PDT
Comment on attachment 63958 [details]
proposed patch

Comment 3 Martin Robinson 2010-08-10 09:38:47 PDT
I think it might be good to make these icons members of the RenderTheme, much like the images used for media buttons. What do you think?
Comment 4 Gustavo Noronha (kov) 2010-08-10 09:49:53 PDT
Oops, sorry Martin, I just landed r65074 before reading your comment. I thought about doing it that way, but I didn't really see advantages to adding the complexity, do you see any advantage in having member variables?
Comment 5 Gustavo Noronha (kov) 2010-08-10 09:50:32 PDT
Comment on attachment 63958 [details]
proposed patch

Landed as r65074. I'm leaving the bug open while we explore Martin's suggestion.
Comment 6 Martin Robinson 2010-08-11 16:21:08 PDT
The reason I suggested was in case we could track changes to the icon theme. Perhaps we cannot, but either way this could easily be a followup patch. I'll close this issue for now! :)