Update comments in line with any changes browsers have introduced. Minor reordering of rulesets.
Doesn't work in Firefox.
Don't attempt to normalize `q` because it prevents the browser from automatically adapting the quotes used based on the value of a `lang` attribute.
Don't visually break `pre` text over multiple lines. Trigger a scrollbar when the preformatted text is too wide for its container.
Chrome, Firefox, and Opera set `vertical-align: -0.2em`. The browser implementations aren't great. They scale badly with font size and when the height of the element is changed. Aligning them to the baseline, as IE does, helps make their alignment consistent with other similar elements.
Leave the default baseline alignment in place. Fix gh-280
Fix the cursor style for Chrome's increment/decrement buttons on `input[type="number"]. For certain `font-size` values of the `input`, it causes the cursor style of the decrement button to change from `default` to `text`. Fix gh-283
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
All browsers that support `figure` apply margin of `1em 40px`. Fix gh-262
Address Firefox not inheriting `font` properties for `optgroup`. Fix gh-102
Normalize.css makes some convenience changes to the default table rendering. This change removes the 1px of padding around table cells.
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
Fixes an issue in Firefox  and Chrome . The implicit width of `fieldset` can be determined by the width of descendants rather than the parent container. This change (adding `min-width:0`) makes the `fieldset` behave like a `div` in this regard.  https://bugzilla.mozilla.org/show_bug.cgi?id=504622  http://stackoverflow.com/questions/8084343/google-chrome-fieldset-overflow-bug Close #272
The Component(1) spec was updated to require a `repo` property.
* Recommend that normalize.css is used as library code (i.e., not modified). * Add a note that v1 is no longer actively developed.