4 ms·
This wasn't really the point of the article, which in fact says the workaround was patched in Chrome 118.
by Wowfunhappy 1y ago
This wasn't really the point of the article, which in fact says the workaround was patched in Chrome 118.
- irrational 1y agoBecause the author reported it. Personally I would have told the ublock origin developers instead of google.
- Wowfunhappy 1y agoTo what end? So Google can see how it works and still patch it?
- deryilz 1y agoYeah, this was my thought process. I get the appeal, but I don't think a million-user open-source extension is gonna start relying on a clear bug to function.
- scotty79 1y agoAt least it would make them work for it.
- Wowfunhappy 1y agoIt would be creating more work for the Ublock Origin developer[1]; as far as I can tell it wouldn't be creating any extra work for Google, which has to patch the issue anyway. 1: Assuming he even elected to do it; I know I wouldn't.
- account42 1y agoAccording to the article it would have been two additional lines for the extension developers.