The default bug view has changed. See this FAQ.

because we bold the selected text, the text shifts to the right (slightly) as you continue to match

RESOLVED FIXED in Firefox 16

Status

()

Firefox
Location Bar
P3
normal
RESOLVED FIXED
10 years ago
5 years ago

People

(Reporter: (not reading, please use seth@sspitzer.org instead), Unassigned)

Tracking

({polish})

Trunk
Firefox 16
polish
Points:
---
Dependency tree / graph
Bug Flags:
blocking-firefox3.5 -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [polish-easy][polish-visual][polish-p1] fixed by bug 587909)

Attachments

(1 attachment)

because we bold the selected text, the text shifts to the right (slightly) as you continue to match.

sayre pointed this one out.

one suggestion he had was using black for the matching text and grey for the non-matching text.  (and dark green vs not-as-dark green for the matching url)
Depends on: 393508
Blocks: 393508
No longer depends on: 393508
using bold appears to have other issues, see bug #407861 "Bolding the found text in autocomplete breaks ligatures "

Comment 2

9 years ago
(In reply to comment #0)
> one suggestion he had was using black for the matching text and grey for the
> non-matching text.

That'll lead to a variation of bug 409974, though. What about using HighlightText/Highlight instead? Won't look great, but it won't look out of place, either.

Updated

9 years ago
Duplicate of this bug: 424192

Comment 4

9 years ago
how about using -moz-opacity: .8 or so on unmatched text?
(In reply to comment #4)
> how about using -moz-opacity: .8 or so on unmatched text?

Alex, would that be a possible way?

Flags: blocking-firefox3.1?
Not going to block the 3.1 release for this. Alex Faaborg has recently talked about using contrasting colors instead of bold+underline to resolve this issue.
Keywords: polish
Priority: -- → P3
(In reply to comment #6)
> Not going to block the 3.1 release for this. Alex Faaborg has recently talked
> about using contrasting colors instead of bold+underline to resolve this issue.

Dietrich, could you please set the flags accordingly?
Flags: blocking-firefox3.1? → blocking-firefox3.1-
(In reply to comment #6)
> Not going to block the 3.1 release for this. Alex Faaborg has recently talked
> about using contrasting colors instead of bold+underline to resolve this issue.

Of course, "contrasting" colors, when foreground-only (i.e., red vs. blue but not white-on-black vs. black-on-white) can be a problem for color-blind users. Maybe the underline should be kept.
Created attachment 343431 [details]
Possible formatting changes

Here is a mockup of possible formatting changes.  This doesn't address the text shifting problem, since we are still using bold, but does clean up the appearance a little by removing the underlines and using contrast for emphasis.

Updated

8 years ago
Whiteboard: [polish-easy][polish-visual][polish-high-visibility]
This bug's priority relative to the set of other polish bugs is:
P1 - Polish issue that appears in the main window, or is something that the user may encounter several times a day.

This effects every interaction with the awesome bar, so definitely something that users will encounter several times a day.
Whiteboard: [polish-easy][polish-visual][polish-high-visibility] → [polish-easy][polish-visual][polish-p1]
This is fixed by bug 587909, which removes the bold.  Varying opacity may happen in bug 774118.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED

Updated

5 years ago
Depends on: 587909
Whiteboard: [polish-easy][polish-visual][polish-p1] → [polish-easy][polish-visual][polish-p1] fixed by bug 587909
Target Milestone: --- → Firefox 16
You need to log in before you can comment on or make changes to this bug.