Closed Bug 1163455 Opened 10 years ago Closed 9 years ago

Residual 'overline' text-decoration not removed when changing text-decoration value

Categories

(Core :: Layout: Text and Fonts, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
Tracking Status
firefox40 --- affected

People

(Reporter: bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: testcase)

Interactive DHTML test with vendor-prefixes ------------------------------------------- http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/text-decoration-DHTML.xht Steps ----- 1- Check vertical-rl radio button 2- Check overline radio button 3- Check upright radio button A) 4- Check line-through radio button or B) 4- Check underline radio button Actual result ------------- After step 4, there are 2 residual overline text-decoration still painted; one over (or to the right of) "Text ÉÉ__" and one over (or to the right of) "zz". Expected result --------------- No residual overline text-decoration. Notes ----- - The test declares "DejaVu Serif" font. The test also renders the actual result when using "Liberation Serif". Right now, I do not know if such test will render the actual result with another font face (besides DejaVu Serif and Liberation Serif) and under another operating system. - Chrome 42.0.2311.135 and Chrome 44.0.2391.0 pass such 4-steps test. - I am using Firefox 40.0a1 buildID=20150430100104 - I use Linux 3.13.0-52-generic x86_64, Qt: 4.8.6, KDE 4.13.3; Kubuntu (trusty) 14.04.02 LTS - I've searched for duplicates and did not find any - I've set severity to minor since I do not know entirely the context causing issue, circumstances (font, font size, etc) and frequency related to such issue.
Blocks: writing-mode
Keywords: testcase
> Right now, I do not know if such test > will render the actual result with another font face (besides DejaVu Serif > and Liberation Serif) and under another operating system. Such test will render the actual result with "Times New Roman" under Windows XP SP3.
OS: Linux → All
While using Firefox 48.0a1 buildID=20160414030247, I get expected results. Most likely, the patch in bug 1229743 fixed this bug. Resolving as FIXED
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.