Open
Bug 1382471
Opened 7 years ago
Updated 7 days ago
Firefox wraps word-broken text under a previous float-left, rather than starting it on the same line.
Categories
(Core :: Layout: Text and Fonts, defect, P3)
Core
Layout: Text and Fonts
Tracking
()
NEW
People
(Reporter: wisniewskit, Unassigned)
References
Details
(Whiteboard: [webcompat])
Attachments
(1 file)
|
263 bytes,
text/html
|
Details |
For the attached reduced test-case, Chrome and Edge begin the text on the same line as the preceding float, while Firefox and Safari begin it on the next line. I'm not certain which is the correct behavior.
|
||
Comment 1•7 years ago
|
||
Interestingly, if we use word-break:break-all instead of word-wrap:break-word in the testcase, Firefox will also begin the text on the same line as the float. I'm also not sure which behavior is correct, though.
|
||
Updated•7 years ago
|
Priority: -- → P3
|
||
Comment 2•5 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Webcompat Priority: --- → ?
|
|
||
Comment 3•5 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
|
||
Updated•4 years ago
|
Webcompat Priority: ? → revisit
|
||
Updated•2 years ago
|
Webcompat Priority: revisit → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
|
|
||
Comment 4•7 days ago
|
||
The testcase still shows a difference, but the linked WebCompat report no longer reproduces as Netflix changed their site. Unsetting the webcompat-priority flag.
Webcompat Priority: P3 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•