Closed Bug 1434029 Opened 3 years ago Closed 3 years ago

Broken bold fonts on e-reader-forum.de

Categories

(Core :: Graphics: WebRender, defect, P1)

Product:
Core
Component:
Graphics: WebRender
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox58 --- unaffected
firefox59 --- unaffected
firefox60 --- disabled

People

(Reporter: Tobias.Marty, Assigned: lsalzman)

References

(Blocks 2 open bugs,
URL
)

Details

(Keywords: correctness, nightly-community) 

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180129100406

Steps to reproduce:

Enable WebRender.
Visit www.e-reader-forum.de


Actual results:

Notice very blurred and washed out bold fonts on the page: 
https://abload.de/img/brokenbold82oj5.png


Expected results:

Fonts are rendered correctly: 
https://abload.de/img/okboldvtoov.png
Component: Untriaged → Graphics: WebRender
Product: Firefox → Core
Thanks! Confirmed in Nightly 60 x64 20180129100406 de_DE @ Debian Testing (KDE, Radeon RX480).
fresh profile: gfx.webrender.all

It looked like non-WR by removing both text-shadows. There are other text-shadow bugs.
Blocks: webrender-site-issues
URL: https://www.e-reader-forum.de/
Status: UNCONFIRMED → NEW
Has STR: --- → yes
status-firefox58: --- → unaffected
status-firefox59: --- → unaffected
status-firefox60: --- → disabled
status-firefox-esr52: --- → unaffected
Ever confirmed: true
Keywords: correctness, nightly-community
OS: Unspecified → All
Hardware: Unspecified → All
See Also: → 1430520
Version: 60 Branch → Trunk
Assignee: nobody → lsalzman
Blocks: stage-wr-trains
Priority: -- → P1
Will be resolved by WR PR https://github.com/servo/webrender/pull/2393
Status: NEW → ASSIGNED
See Also: → https://github.com/servo/webrender/pull/2393
Depends on: 1436058
No longer depends on: 1436058
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
This being fixed with a PR - is there a Gecko side reftest that we can add that catches this problem?
You need to log in before you can comment on or make changes to this bug.