Bug 203750

Summary: Ahem content paints outside of the content area.
Product: WebKit Reporter: alan <zalan>
Component: TextAssignee: Myles C. Maxfield <mmaxfield>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, bfulgham, mmaxfield, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar, WPTImpact
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://github.com/web-platform-tests/wpt/issues/20058
https://bugs.webkit.org/show_bug.cgi?id=204197
Attachments:
Description Flags
AHEM overflow
none
Screenshot none

alan
Reported 2019-11-01 11:51:53 PDT
Created attachment 382606 [details] AHEM overflow see attached test case
Attachments
AHEM overflow (427 bytes, text/html)
2019-11-01 11:51 PDT, alan
no flags
Screenshot (62.23 KB, image/png)
2019-11-01 11:52 PDT, alan
no flags
alan
Comment 1 2019-11-01 11:52:11 PDT
Created attachment 382607 [details] Screenshot
alan
Comment 2 2019-11-01 11:53:11 PDT
It looks like when we paint the AHEM
alan
Comment 3 2019-11-01 11:55:32 PDT
(In reply to zalan from comment #2) > It looks like when we paint the AHEM :) Ahem outside of the content area. It's all good when the content is clipped either explicitly (overflow: hidden) or implicitly (composited layer).
Radar WebKit Bug Importer
Comment 4 2019-11-01 12:28:07 PDT
Myles C. Maxfield
Comment 5 2019-11-01 15:33:28 PDT
Ahem has unitsPerEm = 1000. If the font size divides evenly into that, the drawing is (closer) to what is expected. In the general case, font antialiasing will not lie within the layout rect. We need to deal with that in WebKit.
Alexey Proskuryakov
Comment 7 2019-11-03 10:15:26 PST
(In reply to Simon Fraser (smfr) from comment #6) > Gecko turns off antialiasing for Ahem when testing: We did too, as of 12 years ago: bug 17086, r31322.
Alexey Proskuryakov
Comment 8 2019-11-03 10:18:15 PST
...which was rolled back in r31424.
Simon Fraser (smfr)
Comment 9 2019-11-20 10:59:30 PST
*** This bug has been marked as a duplicate of bug 204197 ***
Note You need to log in before you can comment on or make changes to this bug.