4 ms·
What... Did you even read the article? This isn't true at all. --- Supported Everywhere: - Typing Effect (@keyframes) - Drop Shadow - Smooth Scrolling - "
by WORMS_EAT_WORMS 5y ago
What... Did you even read the article? This isn't true at all.
---
Supported Everywhere:
- Typing Effect (@keyframes)
- Drop Shadow
- Smooth Scrolling
- "center" (flexbox)
- Truncate Text (uses line-camp)
- Resize
- Modals (uses :target)
- calc
- Style Empty (:empty)
- Position Sticky (minus some table elements in old versions)
- Scoll Snap (partial support in even IE)
- Dynamic Tooltips (is just pseudo elements...)
- Caret color (except old IE)
- Fancy Text (uses background clip, so all but old IE)
---
Not Supported Everywhere:
- Cursors (mobile, obviously...)
- ::selection (mobile ignores)
- Custom Scrollbars
---
I think if you put it side-by-side like this you really see how inaccurate your comment is...
- Ancapistani 5y agoYes, I read the article - via Safari on my 11” iPad Pro. Things that work: - Typing Effect (@keyframes) - Drop Shadow - "center" (flexbox) - Truncate Text (uses line-camp) - Modals (uses :target) - calc - Style Empty (:empty) - Position Sticky - Scroll Snap - Dynamic Tooltips (when using touchpad) - Fancy Text Things that don’t work: - Smooth Scrolling - Resize - Cursors (even when using the touchpad cursor) - ::selection (even using Safari in “Desktop mode”) - Custom Scrollbars I could test due to not having a live example: - Caret color
- drdec 5y agoThe following did not work for me in IE: - Drop shadow - Custom cursors - Smooth scrolling - Truncate text to a number of lines - Custom scrollbars - Sticky position - Scroll snap - Fancy text - The CodePen CSS button
- crazygringo 5y agoIE usage is under 1% now. It's really only used by people for accessing specific legacy apps and internal websites. Microsoft is ending support for it. There is no longer any reason developers building general-audience websites, web apps, or libraries should care about IE support. It's not part of the general conversation anymore. You only need to cater to IE if you're a developer on one of those legacy sites, or maintain a library that has been around for so long it's still actively used by those legacy sites.
- reaperducer 5y agoIt's really only used by people for accessing specific legacy apps and internal websites. And healthcare. And government. And a lot of other non-Silicon Valley and non-hobby industries.
- crazygringo 5y agoThose are the types of legacy apps and internal websites I was referring to. What did you think I was talking about instead?
- drdec 5y agoI understand that and I happen to be one of those developers that has a customer that requires IE to be supported. So I was interested in the behavior of the site under IE. My experience testing the site in IE was different than that of another poster, so I thought I would document it. I apologize for causing you whatever consternation prompted you to react in this way, it certainly wasn't my intent and wasn't anticipated.
- pmlnr 5y ago> Supported Everywhere Let me guess, "Everywhere" is only the Chrome based, latest browsers?
- WORMS_EAT_WORMS 5y agoCheck the stats on caniuse and get back to me. These would be mostly supported everywhere, partially supported, or with prefixes. The only argument being "but not on IE". Which, 100% of these work on almost all versions of Edge. Edge is provided side-by-side with Internet Explorer these days (mostly...). Internet explorer market share is near zero. Also reminding you that these are just CSS properties (meaning fallbacks are dead-simple or it just looks/behaves boring-er and doesn't break anything).
- runarberg 5y agoEven custom scrollbars work everywhere with different prefixes[1]. It just needed a couple of extra (unprefixed) rules for the missing firefox support: .tile--custom-scrollbar { scrollbar-color: rebeccapurple gold; scrollbar-width: auto; } 1: https://caniuse.com/css-scrollbar https://caniuse.com/css-scrollbar