Should you support old browser versions?

Should you support all browser versions in your robotc application?

That's a good one. The answer for today is as little as possible. I think the common answer from services we see is stable version minus two versions for Chrome.

Okay.

In Firefox it might include the Enterprise support release version, which is bit behind it, updates less frequently and only gets security updates. And this often comes in the Context of what APIs does this browser version support? It used to be a major headache when we were in like 2015 or so when new APIs were added. These days it's relatively stable. Last time I saw it was when someone was complaining about the connection state property not being implemented in Firefox. That was Firefox 112, 113 that shipped it.

I think there's. On the flip side, there's a notion for people that Chrome at least is always running the latest version. And the answer is yes, but. And it's yes, but if you have an Electron application that wraps it, then you don't you run your own version that you've selected. Yes, but it depends. If you're in the enterprise setting, your customers might use an enterprise Chrome installation that might not be upgraded so quickly.

Yes.

So it really depends on the types of users that you have, which might force you to use older versions as well. But then you need to test against them versus working only with consumers. Whereas you'll say, well, you know, let's take the last 2, 3, 4 versions and be done with it.

Yes. And I mean, the problem you really have is how do you test these versions? Getting hold of all the Chrome versions is hard, unless you use Chromium, then it's okay. But you need to have your automated end to end test suit and then run it nightly, make sure nothing broke. Because you. In the CI setting, you only want the current version of the browser, maybe Beta and Canary.

Yes. Okay, thank you.

Thank you.