The "Search" button on Win32/Linux is now in all-caps. All upper-case text is harder to read, and more likely to be ignored, than mixed-case text, since it lacks word-shapes that facilitate legibility, as explained in any typography 101 class. Moreso, the only use of all-caps that I've seen used by trained designers is when it's used sparing to contrast with non-all caps text in a very different typeface. Since we don't use any other typefaces in our UI, this reason shouldn't apply. If you want the Search button to stand out, may I suggest coming up with a more effective and visually savvy means of expressing it?
*** Bug 30940 has been marked as a duplicate of this bug. ***
Thanks for this feedback. We are currently testing this. This is one of the proposals in order to make users more familiar with the new search URL bar feature. BTW as any typography 102 class goes on to explain, the legibility is negatively affected only when uppercase is used within larger amounts of body text. Here we use it for one single word which is more meant to be a glyph rather than a textual expression. Bu as said earlier we are still tweaking these things and looking at alternatives. Accepting bug for later resolution
Status: NEW → ASSIGNED
Target Milestone: M16
Severity: normal → minor
OS: Windows 98 → All
Hardware: PC → All
I DON'T BELIEVE IT! FIRST THE BUTTON USED ALL CAPS, NOW IT USES ALL CAPS AND * BOLD*. DO WE REALLY BELIEVE THAT USERS ARE STUPID, OR IS THAT JUST THE IMPRESSION WE WISH TO PROMOTE?
U BETTR SHUT UP IF U WANT 2 KEEP UR ELITE ACCESS ON MY BBS, BUDDY! ;)
lol fix checked in
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
fixed how? I wasn't aware we'd resolved the issue. Moreover, there are two search buttons. One in the Url bar and one in the sidepanel. I believe when Mr. Elig wrote the bug he was referring to the url button. My only requirement is that they both be exactly the same. (once the style issue is resolved)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
doh commercial build is using a separate DTD apparently.
Move to M20 for later polish.
Target Milestone: M16 → M20
I assume this was corrected a while ago, so marking fixed.
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago → 19 years ago
Resolution: --- → FIXED
VERIFIED Fixed 2000083008 builds
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.