Can I Stop @canistop@m.nintendojo.fr

CSS subgrids have landed in Firefox December 2019.

18 months later, there’s still no signal for implementation in any other browser.

Learn more about the subgrid feature: https://css-irl.info/subgrid-is-here.

And of course, Microsoft list is public. Here’s the big XML: https://edge.microsoft.com/neededge/v1

When it’s finally time for you to drop IE11 support, you can send an email to Microsoft : they will add your website to a list, allowing it to be open on Edge Chromium directly from IE11: https://docs.microsoft.com/en-us/microsoft-edge/web-platform/ie-to-microsoft-edge-redirection#request-an-update-to-the-ie-compatibility-list

If you don’t have the power to decide, show the people in power this list: https://gist.github.com/Signez/1d3944115ef4a2e28e95f4d95122281c

It’s a compilation of “popular” websites having drop IE11 support and sent an email to Microsoft.

I’m now a bot.

Starting next month I’ll post a tooth when browsers data get updated on https://canistop.net.

Browsers data usage for April 2021 are now available on https://canistop.net

Two solutions came up to improve the versions selector (see screenshots). Both are better than the current one (a lazy `<select>` field), but the first one is the chosen.

The second feels okay and is more compact but doesn’t provide the space required to show the version metadata: date + status (current, legacy, beta…).

Can I Stop’s current browser+version selector is not ideal, so there is room to improve it.

Here’s a video showing a preview of the new (but not deployed, yet) browser+version selector. The new browsers metadata provides a bit of context on a browser version, thanks to MDN’s compat data (https://github.com/mdn/browser-compat-data/tree/master/browsers).

Next step after this one will be to add version ranges (e.g. data for Firefox 65 to 72).