Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
ideas:mistakes [2019/04/17 15:50] fantasaiideas:mistakes [2020/03/10 18:47] fantasai
Line 12: Line 12:
   * ''background-size'' with one value should duplicate its value, not default the second one to ''auto''. Ditto ''translate()''.   * ''background-size'' with one value should duplicate its value, not default the second one to ''auto''. Ditto ''translate()''.
   * ''background-position'' and ''border-spacing'' (all 2-axis properties) should take *vertical* first, to match with the 4-direction properties like ''margin''.   * ''background-position'' and ''border-spacing'' (all 2-axis properties) should take *vertical* first, to match with the 4-direction properties like ''margin''.
 +  * Not quite a mistake, because it was a reasonable default for the 90s, but it would be more helpful since then if `background-repeat` defaulted to `no-repeat`.
   * The 4-value shorthands like ''margin'' should go counter-clockwise (so that the inline-start value is before the block-start value).   * The 4-value shorthands like ''margin'' should go counter-clockwise (so that the inline-start value is before the block-start value).
   * ''z-index'' should be called ''z-order'' or ''depth'' and should Just Work on all elements (like it does on flex items).   * ''z-index'' should be called ''z-order'' or ''depth'' and should Just Work on all elements (like it does on flex items).
Line 18: Line 19:
   * 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 (like 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 dash, ''current-color''. Likewise all other color multi-word keyword names. +  * The ''currentColor'' keyword should have retained the dash, ''current-color'', as originally specified. Likewise all other color multi-word keyword names. 
-  * There should have been a predictable color naming system instead of arbitrary X11 names.+  * There should have been a predictable color naming system (like CNS) instead of the arbitrary X11 names which were eventually adopted.
   * ''border-radius'' should have been ''corner-radius''.   * ''border-radius'' should have been ''corner-radius''.
   * Absolutely-positioned replaced elements should stretch when opposite offset properties (e.g. left+right) are set, instead of being start-aligned.   * Absolutely-positioned replaced elements should stretch when opposite offset properties (e.g. left+right) are set, instead of being start-aligned.
Line 48: Line 49:
   * 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-*.   * 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-*.
   * shape-outside should have had wrap- in the name somehow, as people assume the shape should also clip the content as in clip-path.   * shape-outside should have had wrap- in the name somehow, as people assume the shape should also clip the content as in clip-path.
 +  * It shouldn't be `!important` — that reads to engineers as "not important". We should have picked another way to write this.
 
ideas/mistakes.txt · Last modified: 2023/04/10 22:39 by fantasai
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki