3 ms·
Don’t forget `display: contents` in which the element is instructed not to generate a box at all (neither inline nor block; I guess like `display: none` without
by runarberg 6y ago
Don’t forget `display: contents` in which the element is instructed not to generate a box at all (neither inline nor block; I guess like `display: none` without hiding the content).
But I think the spec maintainers are aware of this and CSS Display Module 3[1] allows multi-keywords so you can do stuff like:
display: block grid;
or:
display: run-in ruby;
or even:
display: inline flow-root list-item;
1: https://drafts.csswg.org/css-display/#the-display-properties https://drafts.csswg.org/css-display/#the-display-properties
- c-smile 6y agoThat is not a fix - just a cosmetic change that does not solve anything. display/flow MUST BE [1] different properties as they define orthogonal concepts. We should be able to define them separately. main { display: block; flow:grid; } @media handheld and (width < 100mm) { main { flow:vertical; } } Yet none from display shall go to visibility:none (as in my Sciter [2]). I've seen too many times errors like this: main table { display:none; } main.full table { display:block; } Which is obviously wrong, <table> element should have display:table or display:inline-table; [1] https://tools.ietf.org/html/rfc2119 https://tools.ietf.org/html/rfc2119 [2] https://sciter.com https://sciter.com