Closed
Bug 1309839
Opened 9 years ago
Closed 9 years ago
[css-grid] Grid container's baseline must respect grid-order
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
VERIFIED
INVALID
People
(Reporter: jfernandez, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160802213348
Steps to reproduce:
1- load the attached test case
Actual results:
The grids are baseline aligned using the their blue box child (see result.png)
Expected results:
The grids are baseline aligned respecting the grid-order (see expected.png)
| Reporter | ||
Updated•9 years ago
|
Product: Firefox → Core
Version: 45 Branch → Trunk
| Reporter | ||
Updated•9 years ago
|
Component: Untriaged → Layout
Comment 1•9 years ago
|
||
Thanks for the report. Can you attach the expected.png file please?
Flags: needinfo?(jfernandez)
Updated•9 years ago
|
Summary: [css-grid] Gird container's baseline must respect grid-order. → [css-grid] Grid container's baseline must respect grid-order
| Reporter | ||
Comment 2•9 years ago
|
||
Comment 3•9 years ago
|
||
There's a typo in testcase: "grid-colum: 1" (in three places). After correcting that,
the testcase renders as "expected.png" in Nightly.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•9 years ago
|
Flags: needinfo?(jfernandez)
| Reporter | ||
Comment 4•9 years ago
|
||
(In reply to Mats Palmgren (:mats) from comment #3)
> There's a typo in testcase: "grid-colum: 1" (in three places). After
> correcting that,
> the testcase renders as "expected.png" in Nightly.
Sorry about the typo, but it was when writing the test case for the bug; it was correct in the one I used to detect the bug. Actually, it doesn't work as expected in my build after correcting it. I might have an old build so I'll update and rebuild to verify.
| Reporter | ||
Comment 5•9 years ago
|
||
I've verified it works as expected in latest trunk.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•