My hypothesis is that it's more important for a user to get the focus
style they expect *within* their browser than it is to have consistent focus
styles *between* browsers. In particular, replacing Chrome's default focus
style (esp. just for links) seems presumptuous.
Component designers/developers can make the decision on when to modify
these browser defaults.
Fix gh-216
Inherit all `font` properties.
Inherit `color` for form controls. Chrome and Safari on OS X will not
inherit `color` as they heavily restrict the author-defined styles that
will be respected for that element.
Fix gh-157
Commit: 907890983e
The change caused problems with `body` background color no longer
bubbling up the the `html` element.
It also prevented you from setting `color` or `background` styles on
`html` before the normalize.css styles.
It might not be possibly to safely address – within normalize.css –
the problem that it was trying to avoid.
Fix gh-188
System color schemes (in particular, custom themes in Windows and Linux
distros) affect Firefox, IE, and Opera. Normalizing the web site/app's
root background and text color prevents these unwanted settings from
being used. Chrome doesn't apply system-level schemes to websites.
Fix gh-170
By default, browsers set `text-transform:none` on most form controls in
order to prevent `text-transform` being inherited from ancestor nodes.
However, the `button` and `select` elements are exceptions.
* Firefox and Opera do not apply `text-transform:none` to `select`.
* Chrome, Safari, and IE 8+ do not apply `text-transform:none` to
`button.
It's not suitable to set `text-transform:inherit` because all other form
elements intentionally avoid it. Safari will not honour that style for
`select`, and Chrome will only do so when the `select` element is
clicked.
Further details:
http://tjvantoll.com/2012/07/10/default-browser-handling-of-the-css-text-transform-property/
Chrome, Safari, and Firefox all adjust the margin of `h1` at several
levels of nesting within HTML5 sectioning elements. This change ensures
that the margin, like the font-size, does not vary in these contexts.
Fix gh-160
Firefox uses different `box-sizing` and `height` values to all other
browsers. Firefox doesn't currently support `box-sizing` without the
`-moz-` prefix, so we use both the vendor-prefixed and unprefixed
properties to ensure that it matches the `content-box` value of other
browsers. It also requires the `height` to be set to `0`.
Fix gh-133
The Android 4.0.* work around - `html input[type="button"]` - requires
the addition of `html` to the selector for disabled inputs, otherwise
disabled button inputs still have the `pointer` cursor.
Add 'styles' property to component.json to play nice with 'component'.
'Component' is another component package manager.
See: https://github.com/component/component
