It would be much more useful to document the _minimum_ required versions. In locked-down corporate environments, it's pretty common to be stranded on older versions until gatekeepers decide to push an upgrade. I've seen some places running versions that are as much as full a year behind. "Current" doesn't tell us anything more than a list of checkmarks would.
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Hello @MV10 ... AFAIK, this is only because Blazor is in preview. I'll tag this for RTM, and we'll get firm versions there for 3.0 RTM.
@MV10 ... see #14842 for discussion on this one. We're going to leave it at "Current."
@guardrex thanks for the follow-up. Disappointing. Does "Current" mean Microsoft is committed to automatically guaranteeing full-support the moment a new browser version drops? The decision makes zero sense to me, the page is pretty much worthless this way. Oh well.
guaranteeing full-support the moment a new browser version drops?
Yes ... in the sense that if you hit a 🐞 with a new browser release, they should† assist/advise/fix/workaround the scenario.
†I'm a contractor, so I can't speak for MS directly. This is my assessment based on their remarks.
Does "Current" mean Microsoft is committed to automatically guaranteeing full-support the moment a new browser version drops?
Yes. If you come to us with a bug that only happens in the latest version of one of these browsers then we will support you. If you ask for support for an issue that is specific to an older browser version we will still consider the impact, but we will likely ask you to update your browser.
Most helpful comment
Hello @MV10 ... AFAIK, this is only because Blazor is in preview. I'll tag this for RTM, and we'll get firm versions there for 3.0 RTM.