5 ms·
The following did not work for me in IE: - Drop shadow - Custom cursors - Smooth scrolling - Truncate text to a number of lines - Custom scrollbars - Sticky po
by drdec 5y ago
The 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.