Neither Object.entries nor the File constructor are supported in IE11. WebRTC support was only introduced in Safari 11, for example. As much as I'd like to only have to support modern standards, a large portion of people use outdated browsers. If we assume 10%, we would have to either provide additional support to those customers in the form of helping them download a new browser, or cut them off completely. That's a massive decision.
While I agree that these features are well supported, they're not well enough supported to use carelessly.
Apparently yes, they are. That was the reason I raised the question. Anybody with access to a phone or computer is a potential customer, and we've had IE11s and Safari 10s walk past. If you'd like another example, look at native date pickers. Safari 11 still doesn't have one.
Comments
Neither Object.entries nor the File constructor are supported in IE11. WebRTC support was only introduced in Safari 11, for example. As much as I'd like to only have to support modern standards, a large portion of people use outdated browsers. If we assume 10%, we would have to either provide additional support to those customers in the form of helping them download a new browser, or cut them off completely. That's a massive decision.
While I agree that these features are well supported, they're not well enough supported to use carelessly.
Are those "large portion of people" your customers? If not, they don't matter.
IE11 in general does not matter.
Use statistics to make decisions about feature adoption, do not generalize or guess... that's a straw man that'll burn in a meeting.
Apparently yes, they are. That was the reason I raised the question. Anybody with access to a phone or computer is a potential customer, and we've had IE11s and Safari 10s walk past. If you'd like another example, look at native date pickers. Safari 11 still doesn't have one.