![]() ![]() How do I know it’s a Chromium issue? Because I was able to inspect our extension’s background page (see comment #4), see that no errors were occurring, and that events dispatched locally were firing, whereas identical events that should be dispatched to the extension based on external things happening (such as clicking our browser action button) were not firing or not getting delivered to the extension. Our initial suggestion to users was to disable and re-enable our extension, and that seemed to do the trick.įive days later, the issue randomly reproduced on my machine, and I was able to confirm that it is a Google Chrome / Chromium problem, not a problem with our extension, and I registered an issue on the Chromium issue tracker, along with screen recordings that confirm the reproduction and provide some extra detail. The Chrome web store has also been a very good distribution channel for us, so we rely quite a bit on our extension.Īround April 10th, we started getting reports from several users that clicking the CrankWheel button in their browser was not causing anything to happen. My company, CrankWheel, has an optional Chrome extension that improves the ergonomics of our telesales-oriented screen sharing web app, and which is required by a handful of features mostly used by enterprises. BTW, there are two separate US $4,000 bounties for whoever can find a reliable repro or a fix. This post documents some of the things we’ve tried, and details how you can help. The bug is very elusive and remains hard to reproduce, even after 8 weeks of non-stop legwork. We are certain it’s a bug in Google Chrome itself. ![]() TL DR: After one of the updates for Chrome 100, my company’s browser extension stopped working for a small percentage of users, and after lots of digging, it looks like the same issue occurs in several of the most popular Chrome extensions out there. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |