Open Bug 616605 (css-grid) Opened 14 years ago Updated 1 year ago

[META] CSS Grid Layout

Categories

(Core :: Layout, enhancement)

enhancement

Tracking

()

People

(Reporter: mail, Unassigned)

References

(Depends on 32 open bugs, Blocks 2 open bugs, )

Details

(6 keywords, Whiteboard: [DevRel:P1])

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101202 Firefox/4.0b8pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101202 Firefox/4.0b8pre

I would like to propose the inclusion of plans to develop a draft standard for firefox CSS Grid Alignment Level 3.

Reproducible: Always
Component: General → Style System (CSS)
OS: Windows 7 → All
Product: Firefox → Core
Hardware: x86 → All
QA Contact: general → style-system
Please also ensure that absolute-positioned children are supported inside of grid "cells".

I've noticed that IE 10 supports this in both "grid alignment" layouts as well as in "flexbox" layouts.

I bring this up because Mozilla does not support absolute-positioned children inside of flexbox boxes as seen in Mozilla bug 649701.
Support was added in IE10 and this is the demo page they use to showcase it:
http://ie.microsoft.com/testdrive/HTML5/GridSystem/Default.html

(obviously the "-ms" prefixes would need to be changed to "-moz" etc.)
It has graduated from the dev.w3.org server as "Grid Layout":
http://www.w3.org/TR/css3-grid-layout/
I suspect that css3-grid-layout will supersede/replace css3-layout (see bug 466974). I think implementing css3-grid-layout (this bug) is a better option. The sooner this is implemented the better.
Renaming the bug to reflect the new spec name.

In addition to IE10, there is work happening in WebKit : https://bugs.webkit.org/show_bug.cgi?id=60731

I'm not strongly asking for this particular module but it is clear to me that one layout system needs to be implemented.
Summary: CSS Grid Alignment Level 3 → CSS Grid Layout Level 3
Whiteboard: [parity-ms]
Keywords: css3
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [parity-ms] → [parity-ie]
Any update here? Is that something we want to have?
FWIW, Hyatt's Webkit implementation never progressed, but Julien Chaffraix and others at Google have recently picked this up and are actively developing it: https://lists.webkit.org/pipermail/webkit-dev/2011-November/018570.html
(In reply to Paul Rouget [:paul] from comment #7)
> Any update here? Is that something we want to have?

It is something I want to have, but nobody's working on it (yet).
Alias: css3-grid
Version: unspecified → Trunk
Note: The CSS3 Grid spec uses "display: grid".  However, in current Gecko releases, the style "display: -moz-grid" triggers _XUL_ grid layout (not CSS3 grid layout, which of course isn't implemented yet, since this bug is still open).

When we fix this bug & add support for CSS3 grid, we'll need to either...
 (a) commandeer the existing keyword ("display: -moz-grid") and potentially break existing content that expects the XUL grid model
 (b) use a different display value ("display: -moz-css3-grid" or something)
 (c) ship it unprefixed ("display: grid")

Not sure about the cost-benefits -- just wanted to get that out there (and clarify this for people who might already be using -moz-grid and expecting CSS3 grid behavior).
W3C has published a new update about the draft of CSS Grid Layout:
http://www.w3.org/TR/2012/WD-css3-grid-layout-20120322/
Yup, thanks!  This bug's URL field actually points to an even more up-to-date (and volatile) version than that (the editor's draft)
 --> /me updates URL to point to where the old URL redirects.(s/grid-align/grid-layout/)
Blocks: 709467
Blocks: css3test
(In reply to Daniel Holbert [:dholbert] from comment #10)
> When we fix this bug & add support for CSS3 grid, we'll need to either...
>  (a) commandeer the existing keyword ("display: -moz-grid") and potentially
> break existing content that expects the XUL grid model
>  (b) use a different display value ("display: -moz-css3-grid" or something)
>  (c) ship it unprefixed ("display: grid")

So I think the current approach is (option c) to implement everything unprefixed but behind a pref (`display: grid;` needs Bug 872301 to be fixed then, I think). That means it won't interfere with XUL Grid. 

However, I think it's worth assessing the option of disabling XUL Grid for web content to not confuse web devs. Is there actually any use of XUL Grid in Web content? I though XUL for Web content was disabled at some point, anyway?
Depends on: 914360
New working draft: CSS Grid Layout Module Level 1
http://www.w3.org/TR/2013/WD-css3-grid-layout-20130910/
[Removing "level 3" from bug title, as the spec is now titled "CSS Grid Layout Module Level 1"]
[It's still part of "css3", so that keyword still applies; but each module levels independently now, starting at level 1, except for modules that were covered in css2.1]
Summary: CSS Grid Layout Level 3 → CSS Grid Layout
Alias: css3-grid → css-grid
Depends on: 975501
Depends on: 976787
Depends on: 978212
Depends on: 978478
Depends on: 981300
Depends on: 981752
Depends on: 981754
Depends on: 983175
Depends on: 984760
Depends on: 989755
Depends on: 994592
Depends on: 1000376
Depends on: 1000431
Depends on: 1000592
Depends on: 1002607
Depends on: 1004197
Depends on: 1005567
Depends on: 1008969
Depends on: 1009214
Depends on: 1009272
Depends on: 1009282
Depends on: 1009776
Depends on: 1034361
Depends on: 1056864
Depends on: 1107778
Depends on: 1107783
Depends on: 1107786
Depends on: 1117538
Depends on: 1118820
Depends on: 1136908
Depends on: 1139539
Depends on: 1144096
Depends on: 1145968
Depends on: 1146051
Depends on: 1147423
Depends on: 1151201
Depends on: 1151204
Depends on: 1151212
Depends on: 1151213
Depends on: 1151214
Depends on: 1151243
Depends on: 1151316
Depends on: 1153140
Depends on: 1163432
Depends on: 1163435
Depends on: 1163565
Depends on: 1172327
Depends on: 1174569
Depends on: 1174574
Depends on: 1176775
Depends on: 1176782
Depends on: 1176790
Depends on: 1176792
Depends on: 1176793
Just filed bug 1181227 to have some kind of css grid layout inspector over in devtools.
I don't think this has been discussed in the intent to implement thread, but having a way for users to just see the grid, and areas would probably help them a lot debug problems, and therefore help with adoption.
I suspect just drawing the lines will require a new chrome-only API to be created.

Also, what's the state of the implementation of the spec? It seems that many of the blocking bugs have been fixed already, so I'm wondering if one can already experiment with this.
Keywords: DevAdvocacy
Depends on: 1194446
Depends on: 1194888
Depends on: 1194892
Depends on: 1201932
Depends on: 1201941
Depends on: 1209485
Depends on: 1211260
Depends on: 1217086
Blocks: 914360
No longer depends on: 914360
Depends on: 1226697
Depends on: 1227285
Depends on: 1229165
Depends on: 1230665
Depends on: 1238890
Depends on: subgrid
Depends on: 1251999
Depends on: 1185140
Depends on: 1255393
Depends on: 1258443
Depends on: 1264067
Depends on: 1264607
Depends on: 1266265
Depends on: 1266268
Depends on: 1267555
No longer depends on: 1267555
Whiteboard: [parity-ie] → [parity-ie][DevRel:P1]
Depends on: 1272783
Depends on: 1277934
Depends on: 1278058
Depends on: 1279182
Depends on: 1279641
Depends on: 1278455
Flags: platform-rel?
platform-rel: --- → ?
Depends on: 1281320
Depends on: 1281446
Whiteboard: [parity-ie][DevRel:P1] → [parity-ie][parity-webkit][DevRel:P1]
Depends on: 1282418
Depends on: 1282643
Could some provide an update on status and intention? Thanks
Depends on: 1299133
Depends on: 1300366
Depends on: 1302839
Depends on: 1305244
Depends on: 1304636
Depends on: 1306705
Depends on: 1309407
Depends on: 1309839
Depends on: 1312403
Depends on: 1312379
Depends on: 1313068
Depends on: 1315750
Depends on: 1315857
Depends on: 1316051
Depends on: 1316884
Depends on: 1317168
Depends on: 1317206
Depends on: 1317524
Depends on: 1317578
Depends on: 1317840
Depends on: 1317845
Depends on: 1317870
Depends on: 1319958
Depends on: 1319688
Depends on: 1269642
Depends on: 1321655
Depends on: 1330380
Depends on: 1330866
platform-rel: ? → ---
Depends on: 1335806
Depends on: 1336679
Depends on: 1338108
No longer depends on: 1338108
Depends on: 1339672
Depends on: 1339911
Depends on: 1341507
Depends on: 1346533
Depends on: 1346699
Depends on: 1348519
Depends on: css-grid-1
Depends on: css-grid-2
Depends on: 1349320
Depends on: 1349481
Depends on: 1350069
Depends on: 1350925
Depends on: 1351557
Depends on: 1352314
Depends on: 1355445
No longer depends on: 1355445
Depends on: 1356236
Depends on: 1356820
No longer depends on: 1352314
Depends on: 1351359
No longer depends on: 1351557
Depends on: 1417711
Keywords: meta
Summary: CSS Grid Layout → [META] CSS Grid Layout
Component: CSS Parsing and Computation → Layout
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Whiteboard: [parity-ie][parity-webkit][DevRel:P1] → [DevRel:P1]
Depends on: 1485581
Depends on: 1518585
Depends on: 1519958
Depends on: 1521088
Depends on: 1528030
Depends on: 1531965
Type: defect → enhancement
Depends on: 1566969
Depends on: 1569639
Depends on: 1566690
Depends on: 1569821
Depends on: 1644370
Severity: normal → S3
Depends on: 1795382
You need to log in before you can comment on or make changes to this bug.