Skip to content

Conversation

@GregParis
Copy link

Hi,
Some purposes:

  • why do you keep Details and its child Summary as they are not supported by IE and Firefox?
  • i notice that chrome apply bold on lighter font when using <i> , i fixed it by using:
    i { font-style: oblique;}

I see you will remove hgroup > nice!

necolas and others added 30 commits August 19, 2012 20:41
No longer supports IE 6/7, Firefox < 4, and Safari < 5.

* Make use of `inherit` to simplify some of the rules.

* Remove a lot of padding and margin normalization, particularly for
  typographic elements, because modern browsers share common base
  styles.

* Add `quotes` normalization. While all target browsers support
  `quotes`, they don't share a common set of quote styles. Opera and IE
  use "curly" quotes whereas other browsers do not. Browsers don't
  appear to set different quotes depending on the language (via the
  `lang` attribute) of the content.

* Remove all list normalizations and they aren't needed anymore.

* Remove a handful of form normalizations that targetted IE 6/7 or
  Firefox 3.
Add 'styles' property to component.json to play nice with 'component'.

'Component' is another component package manager.
See: https://github.com/component/component
* Make consistent use of tense in code comments.
* Update the comment style to match a more common convention.
* Remove an unintentional newline.
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.
The HTML Working Draft has added `main` as a new element.
`word-wrap: break-word` was only needed for IE 6/7, and `white-space:
pre` is the default for all supported browsers.

Fix gh-159
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
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
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/
* Mention v1's support for legacy browsers.
* Provide link to project page for easy download.
* Include Bower install command.
Bower doesn't currently use several properties that were included.
Keep `styles` for now, for Component(1).
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
GitHub have redirected all `username.github.com` pages to
`username.github.io`.
Includes process for maintainers while there is no automation in place.

Close gh-175
Ignore files that don't need to be installed.
necolas and others added 29 commits January 24, 2014 22:04
Don't visually break `pre` text over multiple lines.

Trigger a scrollbar when the preformatted text is too wide for its
container.
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.
Doesn't work in Firefox.
Update comments in line with any changes browsers have introduced.

Minor reordering of rulesets.
Use a test-like presentation to make it clearer what the test file is
looking to test. Don't use the file as a dumping ground for every HTML
element. This change makes the tests more focused and useful.

Fix gh-276
Fix gh-284
Fix gh-285
Additional details to clarify the esoteric parts of normalize.css.

Fix #353
Firefox ESR is currently at Firefox 31, which doesn't require box-sizing
prefixes.

Fix #400
@necolas necolas closed this Dec 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.