| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| ideas:mistakes [2017/12/02 18:44] – fantasai | ideas:mistakes [2018/10/08 13:54] – fantasai |
|---|
| * The top and bottom margins of a box should never have been allowed to collapse together automatically as this is the **root of all margin-collapsing evil**. | * The top and bottom margins of a box should never have been allowed to collapse together automatically as this is the **root of all margin-collapsing evil**. |
| * Partial collapsing of margins instead of weird rules to handle min/max-heights? | * Partial collapsing of margins instead of weird rules to handle min/max-heights? |
| * Tables (and other non-blocks, e.g. flex containers) should form pseudo-stacking contexts. | * Tables (like other non-blocks, e.g. flex containers) should form pseudo-stacking contexts. |
| * The ''currentcolor'' keyword should have a dash, ''current-color''. | * The ''currentcolor'' keyword should have a dash, ''current-color''. |
| * There should have been a predictable color naming system instead of arbitrary X11 names. | * There should have been a predictable color naming system instead of arbitrary X11 names. |
| * ''font-family'' should have required the font name to be quoted (like all other values that come from "outside" CSS). The rules for handling unquoted font names make parsing ''font'' stupid, as it requires a ''font-size'' value for disambiguation. | * ''font-family'' should have required the font name to be quoted (like all other values that come from "outside" CSS). The rules for handling unquoted font names make parsing ''font'' stupid, as it requires a ''font-size'' value for disambiguation. |
| * Flexbox should have been less crazy about flex-basis vs width/height. Perhaps: if width/height is ''auto'', use flex-basis; otherwise, stick with width/height as an inflexible size. (This also makes min/max width/height behavior fall out of the generic definition.) | * Flexbox should have been less crazy about flex-basis vs width/height. Perhaps: if width/height is ''auto'', use flex-basis; otherwise, stick with width/height as an inflexible size. (This also makes min/max width/height behavior fall out of the generic definition.) |
| * :empty should have been :void, and :empty should select items that contain only white space | * <del>:empty should have been :void, and :empty should select items that contain only white space</del> FIXED in the spec, waiting for implementations to check for Web-compat... |
| * ''table-layout: fixed; width: auto'' should result in a fill-available table with fixed-layout columns. | * ''table-layout: fixed; width: auto'' should result in a fill-available table with fixed-layout columns. |
| * 'text-orientation' should have had ''upright'' as the initial value (given the latest changes to 'writing-mode'). | * 'text-orientation' should have had ''upright'' as the initial value (given the latest changes to 'writing-mode'). |
| * We probably should have avoided mixing keywords (span) with idents in the [[https://github.com/w3c/csswg-drafts/issues/1137|grid properties]], possibly by using functional notation (like ''span(2)''). | * We probably should have avoided mixing keywords (span) with idents in the [[https://github.com/w3c/csswg-drafts/issues/1137|grid properties]], possibly by using functional notation (like ''span(2)''). |
| * comments shouldn't have been allowed basically everywhere in CSS (compare to HTML, which basically only allows them where content goes), because it makes them basically unrepresentable in the object model, which in turn makes building editing directly on top of the object model impossible | * comments shouldn't have been allowed basically everywhere in CSS (compare to HTML, which basically only allows them where content goes), because it makes them basically unrepresentable in the object model, which in turn makes building editing directly on top of the object model impossible |
| | * The alignment properties in Flexbox should have been writing-mode relative, not flex-flow relative, and thus could have reasonably understandable names like align-inline-* and align-block-*. |
