981300, 1194446, 1201941, 1266265, 1269642, 1278058, 1300366, 1302839, 1306705, 1312403, 1315750, 1316884, 1317206, 1317524, 1317578, 1317840, 1317845, 1321655, 1330866, 1339672, 1341507, 1356236, 1519958, 1521088, 1531965, 976787, 978212, 981752, 981754, 983175, 984760, 989755, 994592, 1000431, 1000592, 1002607, 1004197, 1005567, 1008969, 1009214, 1009272, 1009282, 1009776, 1034361, 1056864, 1117538, 1118820, 1144096, 1145968, 1146051, 1147423, 1151201, 1151204, 1151212, 1151213, 1151214, 1151243, 1151316, 1153140, 1163432, 1163435, 1163565, 1172327, 1174569, 1174574, 1176775, 1176782, 1176792, 1176793, 1185140, 1194888, 1194892, 1209485, 1211260, 1226697, 1227285, 1229165, 1230665, 1238890, 1251999, 1255393, 1258443, 1264067, 1264607, 1266268, 1272783, 1278455, 1279182, 1279641, 1281320, 1281446, 1282418, 1282643, 1299133, 1304636, 1305244, 1309407, 1309839, 1312379, 1313068, 1315857, 1316051, 1317168, 1317870, 1319688, 1330380, 1335806, 1346533, 1346699, 1349320, 1349481, 1350069, 1350925, 1351359, 1356820, 1417711, 1485581, 1528030
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
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
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).
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/)
Cross referencing: Chromium bug: https://code.google.com/p/chromium/issues/detail?id=79180 Opera: http://my.opera.com/ODIN/blog/show.dml/40630922#comment83173332 Ie10 demo: https://ie.microsoft.com/testdrive/HTML5/GridSystem/Default.html Should look like http://www.thegridsystem.org/
(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?
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
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.
Whiteboard: [parity-ie][DevRel:P1] → [parity-ie][parity-webkit][DevRel:P1]
Could some provide an update on status and intention? Thanks
3 years ago
platform-rel: ? → ---
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
You need to log in before you can comment on or make changes to this bug.