The Address Location field font face and dropdown list looks compressed




14 years ago
13 years ago


(Reporter: will, Assigned: bugs)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



14 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

The address location field in the toolbar, where you type,
and it's dropdown autocomplete list font looks compressed horizontally and
almost like it's not using the system font (Lucida Grande) or something else odd
is going on here.  It clearly doesn't look right when compared to other
applications that use the system font.

Reproducible: Always
Steps to Reproduce:
1.Launch Firefox
2.Type in an address in the address field, namely a long address
Actual Results:  
The string looks like it's compressed horizontally when compared to other
applications on the system.  The search field also compresses the text in the
same way.  Could be because it's not using the correct system font.  The
bookmarks toolbar font face looks like it's using the correct system font for

Expected Results:  
Firefox should render the address bar font using the correct system font and
spacing, etc.

Comment 1

14 years ago
Reporter, a screenshot might be helpful here.

Comment 2

14 years ago
Created attachment 163714 [details]
screenshot of compressed address field text

This shows how the font face/characters are being compressed compared to the
system font's default character spacing.  I've taken a screenshot of Firefox's
address field and put that text into TextEdit with 12pt Lucida Grande font
selected, you can see that it's noticeably shorter in Firefox's address field
than what it should be to look correct compared to the system font.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.