Canonical.css now v2 and CC0

#1

Post by marxo » Fri, Nov 24, 2017, 3:05 PM UTC

Re: Canonical.css now v2 and CC0

#2

Post by Freak_NL » Fri, Nov 24, 2017, 3:11 PM UTC

The README doesn't mention which browsers it supports (presumably at least the Chrome/Firefox/Edge evergreens?). I would add that, and perhaps a comparison of sizes between this and Normalize.css.

Re: Canonical.css now v2 and CC0

#3

Post by marxo » Fri, Nov 24, 2017, 3:15 PM UTC

Freak_NL wrote: post #2

The README doesn't mention which browsers it supports (presumably at least the Chrome/Firefox/Edge evergreens?). I would add that, and perhaps a comparison of sizes between this and Normalize.css.

Thanks for the tip, I'll be improving that in the patch releases soon.

Until that is done: It supports IE11, FF48+, Edge and Chrome. Mobile browser tests are on the way. Some things are ported from Normalize.css for backword compatibility, but the goal is to remove them as soon as IE11 drops below 1%.

Re: Canonical.css now v2 and CC0

#4

Post by Freak_NL » Fri, Nov 24, 2017, 3:26 PM UTC

marxo wrote: post #3

Freak_NL wrote: post #2

The README doesn't mention which browsers it supports (presumably at least the Chrome/Firefox/Edge evergreens?). I would add that, and perhaps a comparison of sizes between this and Normalize.css.

Thanks for the tip, I'll be improving that in the patch releases soon. Until that is done: It supports IE11, FF48+, Edge and Chrome. Mobile browser tests are on the way. Some things are ported from Normalize.css for backword compatibility, but the goal is to remove them as soon as IE11 drops below 1%.

Yeah, that sounds sensible. Having IE11 support is probably the biggest deal breaker for most web developers interested in this kind of project now.

Re: Canonical.css now v2 and CC0

#5

Post by marxo » Fri, Nov 24, 2017, 3:53 PM UTC

Freak_NL wrote: post #4

marxo wrote: post #3

Earlier quoted context omitted.

Thanks for the tip, I'll be improving that in the patch releases soon. Until that is done: It supports IE11, FF48+, Edge and Chrome. Mobile browser tests are on the way. Some things are ported from Normalize.css for backword compatibility, but the goal is to remove them as soon as IE11 drops below 1%.

Yeah, that sounds sensible. Having IE11 support is probably the biggest deal breaker for most web developers interested in this kind of project now.

In the future there might be a file version with IE11 and without IE11 support. IE11 is currently at 3,7% globally, so I still see considerable use there.

Re: Canonical.css now v2 and CC0

#6

Post by Freak_NL » Mon, Nov 27, 2017, 12:36 PM UTC

marxo wrote: post #5

Freak_NL wrote: post #4

Earlier quoted context omitted.

Yeah, that sounds sensible. Having IE11 support is probably the biggest deal breaker for most web developers interested in this kind of project now.

In the future there might be a file version with IE11 and without IE11 support. IE11 is currently at 3,7% globally, so I still see considerable use there.

I meant that a lot of developers are now treating IE11 as the lowest supported version, so having it is a must. Having two branches (one without IE11) is probably the best.