Sure, but priorities are a thing. I don't think it's fair to compare this to an origin model exploit.

Yeah, this is a UI bug in devtools for a feature not a lot of people use. Plus web worker bugs always get pushed to the bottom of the queue for every browser. So I don't have any problem with how long my weird issues take to get fixed.

It's more about comparing to Firefox where you usually get a quick response which at least conveys that the person on the other end understands what is being reported. I'm fine with the eventual outcome here. A comment acknowledging that it's a real bug (or not) would have been better, but being assigned to someone sort of acknowledges that, I guess.

> Plus web worker bugs always get pushed to the bottom of the queue for every browser.

Why is that?

It's pretty rare to use in user-code. It might be well used in libraries, but I guess the standard developer experience is using libraries not writing them.

Of course it’s rare because it’s unreliable and buggy as shit across browsers atm (tho a lot better than it was).

So... somewhat self-fulfilling

They should take this kind of bugs seriously.

What would you rather happen? Browser vendors hire more people such that they can fix every valid bug ever filed?

Maybe.

A first good step would be if the billion dollar company would try to come up to the standard of the non profit.

*trillion dollar company.