Open
Bug 1511200
Opened 6 years ago
Updated 3 years ago
outer scrollport's initial scroll position doesn't respect writing-mode from <body>
Categories
(Core :: Layout: Scrolling and Overflow, defect, P3)
Core
Layout: Scrolling and Overflow
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox65 | --- | affected |
People
(Reporter: dholbert, Unassigned)
Details
Attachments
(3 files)
|
700 bytes,
text/html
|
Details | |
|
700 bytes,
text/html
|
Details | |
|
testcase 2: using direction:rtl on body, instead of writing-mode:vertical-rl (works fine in firefox)
689 bytes,
text/html
|
Details |
STR:
1. Load attached testcase
EXPECTED RESULTS
The page's scrollbars should be snapped to the upper-right position.
(The text should be visible, and no red should be visible.)
ACTUAL RESULTS:
The page's scrollbars are snapped to the upper-left position.
(The text isn't visible because it's way off to the right. The red box is visible, even though it's at the end (left) edge of the document.)
Note: Chrome gives EXPECTED RESULTS here.
Firefox Nightly 65 gives ACTUAL RESULTS, though if I move the 'writing-mode' property to be set on html {...} instead of on body {...}, then we change to give EXPECTED RESULTS.
So we're giving `html` some special treatment that we're not giving to `body`.
Interestingly, we don't have this difference for the "direction" property -- if I rewrite the testcase to use "direction: rtl", then we get EXPECTED RESULTS regardless of whether the style is on `html` or on `body`.
|
Reporter | |
Comment 1•6 years ago
|
||
Edge 17 and Safari 12 give "expected results" here, too. So, we're on our own with our rendering.
|
|
Reporter | |
Comment 2•6 years ago
|
||
|
|
Reporter | |
Comment 3•6 years ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #0)
> though if I move the 'writing-mode' property to be set on html {...}
> instead of on body {...}, then we change to give EXPECTED RESULTS.
My just-attached "reference case 1" demonstrates this.
|
|
Reporter | |
Comment 4•6 years ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #0)
> Interestingly, we don't have this difference for the "direction" property --
> if I rewrite the testcase to use "direction: rtl", then we get EXPECTED
> RESULTS regardless of whether the style is on `html` or on `body`.
This "testcase 2" demonstrates this ^^^. We correctly (and interoperably) start *this* testcase scrolled to the upper-right corner, unlike testcase 1 which we mistakenly scroll to the upper-left.
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•