Closed
Bug 293773
Opened 20 years ago
Closed 20 years ago
Bold-underline line too thick compared to other popular browsers.
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: khman999, Unassigned)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Sometimes the underline of bolden-underlined words on a webpage looks too thick and upsets the overall appearance. This always happens when I do searches using Google. The searched keyword(s) would be bolden and underlined in an underlined sentence. The words not boldened have a "normal" line thickness. When both are coupled together it looks odd. IE6 seems to have this bit right. Reproducible: Always Steps to Reproduce: 1. Go to Google.com 2. Search for anything. 3. Look at results page. 1. Open notepad. 2. Type in "<u>This looks <b>odd.</b></u>" excluding speech marks. 3. Open using Firefox latest version. Actual Results: Regular type fonts have a normal thin underline thickness compared to the bolden word. Expected Results: The bolden text, if underlined, should have an underlined thickness no different to ones that are unboldened. Using default Firefox theme. Appears to have existed since the first ever firefox version.
Assignee: myk → nobody
Component: User Interface → Layout
Product: Bugzilla → Core
QA Contact: default-qa → layout
Version: unspecified → 1.7 Branch
Comment 1•20 years ago
|
||
On 1.0.3 OS/2 & trunk Linux I see as reporter describes here, but don't see a reason why in quirks.css.
Comment 2•20 years ago
|
||
I see uniform underscore thickness on 1.0.3 on OS/2 & trunk Linux
Updated•20 years ago
|
OS: Windows XP → All
Version: 1.7 Branch → Trunk
Comment 3•20 years ago
|
||
See bug #1777, and especially bug #1777 comment 241, which indicates this is a WONTFIX.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•