Closed Bug 1287420 Opened 8 years ago Closed 5 years ago

Insufficient search results terms emphasis/highlight in autocomplete popup result list

Categories

(Firefox :: Address Bar, defect, P3)

x86_64
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: stef, Unassigned)

References

Details

(Whiteboard: [fxsearch])

Relatively light search results terms emphasis/highlight (bold font after bug 1273943) is not easily noticeable/soaks in, especially with part word matches among diverse results.
I think that was exactly the reasoning behind it, it should be visible when you are actively looking for it, but should disappear otherwise. Note you can "easily" change the hilight using a userChrome.css hack, you could even make it flashing red :) Let's see what Stephen thinks.
Flags: needinfo?(shorlander)
Priority: -- → P3
Whiteboard: [fxsearch]
(In reply to Marco Bonardo [::mak] (Away 6-20 Aug) from comment #2) > I think that was exactly the reasoning behind it, it should be visible when > you are actively looking for it, but should disappear otherwise. The problem is, it is not really visible if I'm actively looking for it with part word matches among diverse results. > Note you can "easily" change the hilight using a userChrome.css hack, you > could even make it flashing red :) This method seems unsupported so please don't suggest using it.
(In reply to Stefan Plewako [:stef] from comment #3) > This method seems unsupported so please don't suggest using it. Why do you say that? It is as supported as changing non-exposed options in about:config.
I don't know how it is on a mac, but I posted a win7 screenshot (https://bug1291323.bmoattachments.org/attachment.cgi?id=8776986), in urls, it is almost imperceptible
(In reply to Marco Bonardo [::mak] (Away 6-20 Aug) from comment #4) > (In reply to Stefan Plewako [:stef] from comment #3) > > This method seems unsupported so please don't suggest using it. > > Why do you say that? It is as supported as changing non-exposed options in > about:config. As I have heard from Mozilla developers dismissing concerns and feedback that way, changing non-exposed options via about:config or other way is also not supported and shouldn't be considered as valid solution.
indeed it's not officially supported and you won't get a bug fixed if it's caused by your changes, still not a valid reason to not use it, if it improves your life.
Maybe it helps developers close eyes on problems but it doesn't improve users lives in the long run.
Flags: needinfo?(shorlander)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.