Closed
Bug 1494746
Opened 6 years ago
Closed 5 years ago
Words are merged together when using `word-wrap: break-word` with a small width
Categories
(Core :: Disability Access APIs, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1241631
People
(Reporter: anika.henke, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
106.98 KB,
image/png
|
Details | |
1.73 KB,
patch
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36
Steps to reproduce:
Open the reduced test case on http://jsbin.com/guxovas
This test case has (sometimes hidden) content ("Posted on") with a width of 1px inside a container with `word-wrap: break-word`.
Either navigate with a screen reader (e.g. NVDA) to the content under "Hidden content with the issue" and listen to what it reads.
Or alternatively open the accessibility inspector and read what the "textleaf" reports the content is.
Actual results:
You will hear (or read) "Postedon".
Expected results:
You should hear (or read) "Posted on".
Comment 1•6 years ago
|
||
I'm trying to check whether this is a recent regression or not, but yes I wouldn't expect that the presence of word-wrap:break-word should affect what the accessible text content is.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Component: Layout → Disability Access APIs
Priority: P3 → --
Comment 2•6 years ago
|
||
Doesn't look like this is a recent regression.
For reference here's a mochitest that currently fails.
Reporter | ||
Comment 3•6 years ago
|
||
I've just checked if any other related CSS declarations trigger the same issue. I found that apart from the above mentioned `word-wrap: break-word`, the following trigger this as well:
* word-break: break-all
* word-wrap: break-word
Comment 4•5 years ago
|
||
Note that this also affects node.innerText, since it uses the same code.
Blocks: texta11y
Priority: -- → P3
Reporter | ||
Comment 5•5 years ago
|
||
This seems to be fixed now since Firefox 71 with https://bugzilla.mozilla.org/show_bug.cgi?id=1241631.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•