Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V1 #866

Closed
wants to merge 32 commits into from
Closed

V1 #866

wants to merge 32 commits into from

Conversation

Devurl
Copy link

@Devurl Devurl commented Oct 3, 2021

Root Color

necolas and others added 30 commits Aug 20, 2012
GitHub 301 redirects the URL without a trailing slash to the URL with a
trailing slash.
* Consistent use of tense.
* Small change to use common comment style.
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.
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`.

Known issue: this does not normalize IE 6/7 as `hr` cannot be reliably
styled in those browsers.
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 6+ 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 and IE 6/7 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/
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.
Commit: 121c082

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
Please see 690f8ab to see the full description in v2.
@necolas necolas closed this May 20, 2022
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.

None yet

5 participants