Closed Bug 400682 Opened 17 years ago Closed 17 years ago

favicons displayed at full size in open location autocomplete and homepage (pref ui) autocomplete

Categories

(Firefox :: Address Bar, defect, P3)

defect

Tracking

()

VERIFIED FIXED
Firefox 3 beta3

People

(Reporter: mossop, Assigned: moco)

Details

(Keywords: polish)

Attachments

(5 files, 1 obsolete file)

1. Hide the url bar (fullscreen mode, drag it off the toolbar, whatever)
2. File - Open Location.
3. Start typing into the testbox in the dialog that appears.

The favicons in the autocomplete that pops up are displayed at full size rather than shrunk to 16x16 when appropriate. You need to have something like www.bbspot.com in your autocomplete to see it.
Flags: blocking-firefox3?
confirming on Windows XP.

thanks for reporting this, Dave.

there are rules in browser.css to set the image to 16px x 16px, but perhaps they should be moved to autocomplete.css
OS: Mac OS X → All
Hardware: PC → All
Flags: blocking-firefox3? → blocking-firefox3+
Keywords: polish
bug 389273 helps here I bet.
Depends on: 389273
Target Milestone: --- → Firefox 3 M11
> bug 389273 helps here I bet.

I think this is really a case of some missing css, see comment #1.
No longer depends on: 389273
Priority: -- → P3
taking, while testing #405269, I noticed this appears in the homepage pref UI as well.

Note, mconnor is right (about dolske's fix helping), but if the favicon was less than a certain number of bytes (the threshhold before he converts and scales) but bigger than 16px x 16px, we'd still have this bug.

fix coming up.
Assignee: nobody → sspitzer
Summary: favicons displayed at full size in open location autocomplete → favicons displayed at full size in open location autocomplete and homepage (pref ui) autocomplete
Attached patch wip patch (obsolete) — Splinter Review
gavin, what do you think of this approach?

These rules are currently duplicated in browser.css, see http://lxr.mozilla.org/mozilla/source/browser/themes/winstripe/browser/browser.css#937

I could move all the url bar related css rules out of browser.css and into autocomplete.css (would url-autocomplete.css be a better name?) and leave behind the ones that deal with the search bar (suggesthint)

(note, pinstripe and gnomestripe changes are missing.)
Attachment #292807 - Flags: review?(gavin.sharp)
note, the url bar autocomplete continues to work fine (tested by setting browser.urlbar.richResults to false)

note, switched from width to max-width, as these rules will affect the search bar autocomplete results, browser content autocomplete results, etc.
Attachment #292807 - Attachment is obsolete: true
Attachment #292818 - Flags: review?(gavin.sharp)
Attachment #292807 - Flags: review?(gavin.sharp)
Status: NEW → ASSIGNED
Keywords: regression
oops, not a regression, since fx 2 didn't have favicons in these places.
Keywords: regression
Attachment #292818 - Flags: review?(gavin.sharp) → review+
fixed.

for litmus, a good test case is http://www.nps.gov/alcatraz/, assuming that http://www.nps.gov/favicon.ico remains 32 x 32 px

Checking in toolkit/themes/pinstripe/global/autocomplete.css;
/cvsroot/mozilla/toolkit/themes/pinstripe/global/autocomplete.css,v  <--  autoco
mplete.css
new revision: 1.16; previous revision: 1.15
done
Checking in toolkit/themes/winstripe/global/autocomplete.css;
/cvsroot/mozilla/toolkit/themes/winstripe/global/autocomplete.css,v  <--  autoco
mplete.css
new revision: 1.24; previous revision: 1.23
done
Checking in browser/themes/gnomestripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/gnomestripe/browser/browser.css,v  <--  browser.
css
new revision: 1.145; previous revision: 1.144
done
Checking in browser/themes/pinstripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/pinstripe/browser/browser.css,v  <--  browser.cs
s
new revision: 1.101; previous revision: 1.100
done
Checking in browser/themes/winstripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/winstripe/browser/browser.css,v  <--  browser.cs
s
new revision: 1.141; previous revision: 1.140
done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Flags: in-litmus?
Resolution: --- → FIXED
alex / kevin:  you will want to make similar changes to proto
Late comments:

* Does Gnomestripe have this issue? The patch doesn't change toolkit/themes/gnomestripe/global/autocomplete.css (as with win/pingstripe), presumably because that file doesn't exist. So I guess it was already working?

* Why |max-width: 16|? Will this cause misalignments if an entry has a favicon less than 16 pixels wide?
> * Does Gnomestripe have this issue? The patch doesn't change
> toolkit/themes/gnomestripe/global/autocomplete.css (as with win/pingstripe),
> presumably because that file doesn't exist. So I guess it was already working?

yes, gnomestripe doesn't have autocomplete.css.  it uses winstripe's autocomplete.css by default.  See http://lxr.mozilla.org/seamonkey/source/toolkit/themes/Makefile.in#49

> * Why |max-width: 16|? 

max-width, because these css rules will impact the search bar autocomplete results, the browser content autocomplete and other toolkit consumers.  if we use min-width, we'd now have an extra 16px gap.

> Will this cause misalignments if an entry has a favicon less than 16 pixels wide?

Good question!  I just tested, and we don't have this problem.  The 8x8 favicon that I created for testing purposes gets scaled up to 16 x 16 px in the various locations.

Let me figure out why.

I'll attach the test case to this bug.
Verified FIXED with testcases in comment 16 on:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3pre) Gecko/2008010204 Minefield/3.0b3pre

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008010204 Minefield/3.0b3pre

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3pre) Gecko/2008010104 Minefield/3.0b3pre
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: