Open
Bug 1242660
Opened 8 years ago
Updated 2 years ago
[css-writing-modes] Fragmentation issues with vertical writing-mode
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
NEW
People
(Reporter: MatsPalmgren_bugz, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: testcase)
Attachments
(1 file)
|
2.34 KB,
text/html
|
Details |
Compare the attached testcase with Chrome. I think the layout in Chrome make more sense, specifically: In the top columnset: we don't fragment the wrapper* at all even though it doesn't fit inside the columnset. In the next, we seem to fragment the wrapper* but not its last child that overflows. Also, the border skip sides seems wrong. In the bottom columnset: we should probably shrinkwrap the columnset height around its contents, same as if it were an ordinary block. * wrapper = the block with the red border
|
||
Updated•7 years ago
|
Blocks: writing-mode
|
||
Comment 1•7 years ago
|
||
Mats,
1-
What is the <y> element? Is such element part of your test?
2-
Your test involves multi column layout properties, direction property and orthogonal flow. I am convinced we need smaller tests, basic tests for each of the 5 single issues you report. You even have 2 nested orthogonal code contexts! (<body> uses 'writing-mode: horizontal-tb' and then you have <!-- vertical / horizontal / vertical -->. This is excessively complex and not a reasonable code scenario to expect on the web.
3-
line 8: position:relative;
I do not see the goal or purpose of such declaration.
4-
The top columnset. The wrapper (red-bordered) will fragment if there is no nested orthogonal flow: if .hl {writing-mode: horizontal-tb;} is disabled, unchecked.
5-
The bottom columnset. At least 2 bug reports are related to such code scenario: bug 1348839 and bug 1269152
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•