Re:I discovered a browser bug
by jaffathecake on Thursday June 21, 2018 @11:51AM
(#17366230)
Sure, but priorities are a thing. I don't think it's fair to compare this to an origin model exploit.
[ Parent
| on HN ]
Re:I discovered a browser bug
by MatthewPhillips on Thursday June 21, 2018 @12:09PM
(#17366407)
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?
Re:I discovered a browser bug
by philipwhiuk on Thursday June 21, 2018 @01:24PM
(#17367234)
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.
Re:I discovered a browser bug
by abritinthebay on Thursday June 21, 2018 @11:26PM
(#17371066)
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