Bug 201725

Summary: maisonalyzee.com: Text incorrectly wrapped
Product: WebKit Reporter: youenn fablet <youennf>
Component: TextAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, jonlee, mmaxfield, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: BrowserCompat, InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
URL: https://www.maisonalyzee.com/
See Also: https://bugs.webkit.org/show_bug.cgi?id=261212
Attachments:
Description Flags
Test reduction none

youenn fablet
Reported 2019-09-12 10:03:28 PDT
The 'e' of ALYZÉE is misplaced and the menu is not 100% visible. Chrome renders it ok. Safari does not. Firefox does not.
Attachments
Test reduction (492 bytes, text/html)
2023-01-14 08:44 PST, alan 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2019-09-12 10:04:11 PDT
Given Firefox has the same behaviour, I wonder whether the website is not browser specific.
Simon Fraser (smfr)
Comment 2 2019-09-12 10:28:06 PDT
It's certainly better in FF and Chrome. WebKit seems to have some z-ordering issues.
Radar WebKit Bug Importer
Comment 3 2019-09-12 10:28:21 PDT
<rdar://problem/55307109>
Alexey Proskuryakov
Comment 4 2019-09-12 17:42:23 PDT
Looks like a different font style ends up being used by Safari and Firefox vs. Chrome, so our text is wider. z-ordering seems like it should be tracked as a separate bug, as this is not part of the original description, and certainly has a separate cause.
Ahmad Saleem
Comment 5 2023-01-14 06:19:34 PST
Still reproducing: Safari 16.2 - E is misplaced Safari Technology Preview - E is misplaced Chrome Canary 111 - working fine Firefox Nightly 110 - working fine Just wanted to share updated test results. Thanks!
alan
Comment 6 2023-01-14 08:44:52 PST
Created attachment 464500 [details] Test reduction
alan
Comment 7 2023-01-14 10:24:25 PST
The container width is set to 529px. We measure the content 529.73px wide -> fractional overflow.
Note You need to log in before you can comment on or make changes to this bug.