www.jw.org - Text on the page overflows
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P3, Webcompat Score:4)
People
(Reporter: ctanase, Assigned: twisniewski)
References
(Depends on 1 open bug, )
Details
(5 keywords, Whiteboard: [webcompat-source:web-bugs][webcompat:sightline][webcompat:core])
User Story
user-impact-score:90 platform:windows,mac,linux,android impact:content-missing configuration:general affects:all branch:release diagnosis-team:layout
Attachments
(2 files)
Environment:
Operating system: Mac OS X 10.15/Windows 10
Firefox version: Firefox 145.0/147
Steps to reproduce:
- Go to https://www.jw.org/en/library/bible/kingdom-interlinear-greek-translation/books/revelation/22/
- Observe the text on the page.
Expected Behavior:
The text is correctly aligned and is fully visible.
Actual Behavior:
The text is not fully visible, it overflows on right side of the page.
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/191594
| Reporter | ||
Comment 1•3 months ago
|
||
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
| Comment hidden (obsolete) |
Comment 3•3 months ago
|
||
Adding <wbr> after all <ruby> elements seems to fix the issue.
Comment 4•3 months ago
•
|
||
Workaround:
the following css seems to be fix the issue.
ruby::after {
content: "\200B"; /* Zero-width space (line break opportunity) */
}
or
body {
line-break: anywhere;
}
Comment 5•3 months ago
•
|
||
I filed bug 2003395 as a platform-bug here.
Aside from us fixing that bug... the cleanest fix here would be for the site to move the space characters outside of the rb tags, as in reference case 1b posted on that bug.
In the absence of those fixes, the first part of comment 4 (adding an explicit zero-width space after each ruby tag) seems like a good possible sitepatch that we could ship. That might introduce linebreaks in spots where they aren't intended (and where other browsers don't break), after ruby elements that do not contain a space character; but nonetheless, it'll be better than the layout we're getting right now, I think.
Updated•3 months ago
|
| Assignee | ||
Updated•3 months ago
|
| Assignee | ||
Comment 6•3 months ago
|
||
Updated•3 months ago
|
Comment 8•3 months ago
|
||
| bugherder | ||
| Assignee | ||
Updated•3 months ago
|
Updated•3 months ago
|
Updated•1 month ago
|
Updated•13 days ago
|
Description
•