Hacker News Reader

Hacker News

Comment by gregmac | Hacker News Reader

Full thread

gregmac

Support for these things:

Smooth scrolling CSS: Not IE, Edge or Safari. https://caniuse.com/#search=scroll-behavior

HSL: Everywhere. https://caniuse.com/#search=hsl

Details element: Not IE, Edge. https://caniuse.com/#search=details

Progress element: Everywhere. https://caniuse.com/#search=progress

Meter element: Not IE. https://caniuse.com/#search=progress

CSS variables: Not IE. https://caniuse.com/#search=css%20variables

View on HN

Also, while the author is correct about the core functions of these elements, most cannot be animated or applied a transition between states.

Not a deal breaker functionally speaking, but sometimes a subtle transition is useful so as to be less jarring.

IE support may not be all that relevant these days when even Microsoft disparages its continued use.

Tell that to all 50,000 people in my company, and the product owner I'm working for, who are forced to use it by Infrastructure, and 0.0% of our customers.

typically I still see 5% IE11 users for the regular consumer sites I touch. however much I want to not support IE there is no way to motivate it from a business perspective.

Depending on how much it costs in extra developer hours supporting an older browser it might actually make quite a bit of sense for many companies, especially smaller ones without a well established product.

How much does that 5% bring in profit. If that is more than the amount it costs to keep the support. Then keep it.. other wise remove.

Purely from a business perspective you are correct.

Can not put a price on accessibility though (screenreader, forced IE use, etc.).

Especially for content websites I don't think there is a non-economic reason to justify non-accessible content.

We still have around 10% IE11 usage on our site …

Commenting so I can find this later. Thank's. I have a webcomic and only use about 80 lines of html. This is very attractive to spruce it up a bit.

>In addition to working when users scroll to anchors, if you Ctrl+F on a page with html{ scroll-behavior:smooth; }, it smooth scrolls to the result.

This does not work in Firefox, either.

Reply on news.ycombinator.com