While I agree there ARE some industries that have to support stupid old versions (eg government websites), any other product managers that think they'll be losing business by not supporting IE are misguided.
While I agree there ARE some industries that have to support stupid old versions (eg government websites), any other product managers that think they'll be losing business by not supporting IE are misguided.
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/i...
And the school site has quite an active userbase - students upload assignments via it, parents can live-view all gradings and remarks (and regularly use it), and staff generally access their email via it instead of a client.
[1] https://techcommunity.microsoft.com/t5/windows-it-pro-blog/i...
[2] https://docs.microsoft.com/en-us/lifecycle/announcements/int...
Sure, which can be countered with: "no problem, it will add 30% to the estimate".
Unless the % is significant (over 10%), it's not worth the effort.
One day Safari will enable smooth scroll.
Also don’t forget to check actual conversion and other important metrics for different browsers, not only number of visits.
The problem isn't just IE marketshare. Not every web developer works in e-commerce, on brochure sites or even SaaS apps with a target audience consisting almost entirely of other startups. If you build products for mostly enterprise customers, those customers often dictate what you support, even if they barely even use it anymore. Changing requirements can be difficult.
I remember being asked by a large international company to build a web app in "HTML5 but it must work with IE6" back in the day. Most of their actual users were on Firefox or using iPads.