Define Pure's browser support

[ericf]

Pure should have explicitly defined browser support so people know what to expect it will work on when using it.

Also, I think it things like when vendor prefixes should be used need to be defined. e.g. Do we need to use vendor prefixes on rules which modern browsers (that auto update) now support without prefixes, because people may be using older versions that need the prefix?

[ghost]

#26

[tilomitra]

@ericf I mentioned the browser support in #26. I agree that we should outline this on the home page of the site. This should be an issue on https://github.com/yui/pure-site/ rather than here.

[ericf]

I think it should be in the README.md too.

[evangoer]

Agreed this should not only be on the home page of the site, but also in this repo's README.md or possibly in a CONTRIBUTORS.md. The reason to add the info here is more around setting expectations for what is acceptable in a PR.

[ericf]

The reason to add the info here is more around setting expectations for what is acceptable in a PR.

Good call @evangoer

[CharliePops]

It would love to see a PureCSS alternative version supporting only IE8+(as normalize does). I think that most of websites being built nowdays are targeted for IE8+. Besides, it would make PureCSS even smaller size :).

[tilomitra]

@CharliePops The code needed to support IE7 is pretty minimal. I doubt it would make much of a difference once gzipped. Pure uses Normalize 1.x, which supports legacy browsers such as IE6 and 7. Since it's just CSS, I think it makes sense to support older browsers. That's where most of this layout help is needed anyway. Modern browsers are pretty good when it comes to CSS. Also, just because we support legacy browsers doesn't mean we can't use the sexy new CSS3 properties. They all gracefully degrade on older browsers.

[tilomitra]

Added this info to the README.md. Closing this out.