2 ms·
https://www.caniuse.com/css-marker-pseudo https://www.caniuse.com/css-marker-pseudo 18% support. It's going to be a long time before you can rip out all those l
by gwern 6y ago
https://www.caniuse.com/css-marker-pseudo https://www.caniuse.com/css-marker-pseudo 18% support. It's going to be a long time before you can rip out all those list marker CSS hacks. :(
- onion2k 6y agoWon't that jump to about 60% a few days after the Chromium based browsers have updated though? It's only 18% now because Chrome, Edge and Chrome for Android aren't ready yet. Thats still far too low to use it without a fallback, of course, but it's high enough to justify using it as a progressive enhancement.
- gwern 6y agoI don't know about how fast it'll go to 60%, but what's the 'progressive enhancement' about it? You still have to implement and debug the old list markers, and you'd use the new elements to do just the same thing, so why bother until you can rip out the old code and replace it entirely?