Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This wasn't really the point of the article, which in fact says the workaround was patched in Chrome 118.


Because the author reported it. Personally I would have told the ublock origin developers instead of google.


To what end? So Google can see how it works and still patch it?


Yeah, 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.


At least it would make them work for it.


It 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.


According to the article it would have been two additional lines for the extension developers.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: