It's been 2 (nearly 3) years since the final version of the official spec, but 5 years since any significant changes to the spec draft. IE10 was released in 2012 with a partial IndexedDB implementation, and Edge is still missing features that Chrome and Firefox had 5 years ago.
And I was being facetious, I know I'm not a normal user. Some normal users would like to play a video game I wrote that won't run in Edge due to missing IndexedDB features, though.
Yeah, but I'm willing to bet normal everyday users don't use terms like "browser experience" either.
In fact, I'm pretty sure that anyone who understands the concept of different browsers (rather than referring to whatever standard browser they have as "the internet"), uses Edge primarily to download Chrome or Firefox.
If MS had lots of people complaining about sites that didn’t work or said ‘Edge not supported’ to people who went there and that was because the site needed IndexDB I’m sure they would have added it. It clearly isn’t a huge issue for them.
I can see people saying ‘If I use Edge my phone doesn’t sync bookmarks and stuff like Chrome so I use Chrome.’
I don’t think saying things like ‘people only use it to download Chrome’ is helpful. It’s not IE 7. It’s a perfectly fine browser.
That said, most of those who understand there are multiple browsers likely do so due to a time when, yes, IE was -terrible-...and so all their saved stuff, preferred plugins, etc, are in Firefox or Chrome. So their first act on getting a new computer is to reinstall and sync that stuff. Not "give that new Microsoft browser a spin".
After a Win10 user does that, they will have not one but two unused browsers lingering on their PC (both IE11 and Edge). I name this ship Bloaty McBloatface.
And I was being facetious, I know I'm not a normal user. Some normal users would like to play a video game I wrote that won't run in Edge due to missing IndexedDB features, though.