AndrewM Reporter
	Description • 17 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008040404 Firefox/3.0pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008040404 Firefox/3.0pre

Spinoff from bug 406894.

Lim Chee Aun posted the following code in bug 406894 comment 19 which can be added to userChrome.css to change the autocomplete-history-dropmarker on Vista to menulist-button:

#urlbar > .autocomplete-history-dropmarker{
-moz-appearance: menulist-button !important;
margin: -1px -1px -1px 0 !important;
}

The result can be seen in attachment 313893 [details].

In bug 408694 comment 24, Mike Beltzner said: "Can we get a separate bug on that filed with that patch nominated for review
and approval? That looks a lot nicer for Vista than what we have now.
", so here is the bug :)

I have only noticed one small problem with using this, which is that on secure sites, the background of the dropdown arrow button stays white while the rest of the location bar turns yellow. This would be a moot point if it is decided not to turn the location bar yellow on Windows, of course.

Reproducible: Always

	AndrewM Reporter
	Comment 1 • 17 years ago

(In reply to comment #0)
> ...
> In bug 408694 comment 24, Mike Beltzner said: "Can we get a separate bug on
> that filed with that patch nominated for review
> and approval? That looks a lot nicer for Vista than what we have now.
> ", so here is the bug :)

Oops, that should of course be bug 406894 comment 24.

	Jesper Kristensen
	Comment 2 • 17 years ago

If margin is changed to 0 instead of -1px, this would also be a nice change on XP.

	Kai Liu
	Comment 3 • 17 years ago

Once bug 428878 lands, this would be great to have for Classic, too.  But without the -1px margins, of course.

	Kai Liu
	Comment 4 • 16 years ago

Bug 430434 eliminates the hover state of the dropmarker in chrome.  While that bug was intended to be applied only to menulists that are shaped like a button, it also means that the dropmarker can't be used in this case, where it's shaped like a text box.  Could 430434 be implemented differently to avoid using the chrome-vs-content distinction as a proxy for the button-vs-textbox distinction?

	Dão Gottwald [:dao]
	Comment 5 • 16 years ago

I think attachment 313893 [details] looks unbalanced with the two different dropmarkers next to each other.