Closed Bug 1425469 Opened 8 years ago Closed 6 years ago

[css-writing-mode] Text overflows the viewport for nested writing modes

Categories

(Core :: Layout, defect, P3)

59 Branch
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: huijing, Unassigned)

References

Details

(Keywords: DevAdvocacy, Whiteboard: {DevRel:P2])

Attachments

(3 files)

Attached file testcase.html
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20171215100105 Steps to reproduce: 1. Apply writing-mode: vertical-rl to the body element 2. Apply writing-mode: horizontal-tb to the main element (nested within the body element) Actual results: The text in the main element overflows the viewport. Expected results: The text should wrap as per normal and not overflow the viewport.
Attached image chrome.jpg
Attached image firefox.jpg
Attachment #8937068 - Attachment description: Correct rendering on Chrome → chrome.jpg
Keywords: DevAdvocacy
Whiteboard: {DevRel:P2]
Priority: -- → P1
Priority: P1 → P3
writing-mode set to <body> should propagate to the document root element. " The principal writing mode of the document is determined by the writing-mode and direction values specified on the root element. (...) if the root element has a <body> child element [HTML5], the principal writing mode is instead taken from the values of writing-mode and direction on the first such child element instead of taken from the root element. " 8. The Principal Writing Mode https://www.w3.org/TR/css-writing-modes-3/#principal-flow Right now, this propagation is not performed in Firefox. That's bug 1102175 In the mean time, as a work around, Chen Hui Jing, if you apply 'writing-mode: vertical-rl' to the <html> element (instead of the <body> element), then you should get comparable rendering with Chrome.
See Also: → 1102175
(In reply to Gérard Talbot from comment #3) > In the mean time, as a work around, Chen Hui Jing, if you apply > 'writing-mode: vertical-rl' to the <html> element (instead of the <body> > element), then you should get comparable rendering with Chrome. Okay. Thank you for the update. Will follow bug 1102175.

When I load attachment 8937067 [details] in Firefox 71.0a1 buildID=20191014095234, I get expected results.

Resolving as FIXED (due to fix in bug 1102175)

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: