by dbushell on 3/29/25, 10:27 AM with 74 comments
by preinheimer on 3/29/25, 12:40 PM
I ran my worst client demo ever a few months ago. It was like our product simply didn’t work. A lot of pulled hair and frustrating debugging later we discovered that a recent update to the 1Password extension broke ours. They were subscribing to an auth event, but not returning, this timed out so our subscriber was never called. So our extension would tell the browser to change proxy servers, then sit ready to provide credentials, but the request would never come. 1Password’s support team was better than grammerly’s, but it’s hard to convince an unknown PM to prioritize something, especially if you’re speaking to them via a support team.
We’ve since discovered that there’s some Russian extension you need for government websites that has the same issue.
by karaterobot on 3/29/25, 3:16 PM
by jFriedensreich on 3/29/25, 12:48 PM
by olevzhyn on 3/29/25, 9:06 PM
That was never intentional, and we are using various techniques to prevent this from happening. Unfortunately, that wasn’t enough. The article clearly shows that there’s room for improvement.
We temporarily added an exception for dbushell.com as a quick fix. In the meantime, we’re working on a change to ensure proper style isolation; such issues must never be the case.
Thank you!
by Aldipower on 3/29/25, 12:29 PM
I am trying to detect Google Translate and print a warning then.
by kstrauser on 3/29/25, 3:02 PM
by emptysea on 3/29/25, 3:40 PM
Chrome’s Google translate is also notorious for breaking react based sites.
It ends up being a tedious triage process to ignore each new extension issue. We use the client side filtering to reduce our ingest volume. In general we have to have a lot higher thresholds to handle the noise vs our backends.
by lelandfe on 3/29/25, 5:14 PM
--primary-color: transparent
by dbushell on 3/29/25, 10:27 AM
by MartijnHols on 3/29/25, 4:47 PM
by nikolay on 3/29/25, 9:06 PM
[0]: https://chromewebstore.google.com/detail/microsoft-editor-sp...
by jgalt212 on 3/29/25, 4:46 PM
- Access your data for all websites
- Display notifications to you
- Access browser tabs
> They could also, you know, not inject their code into every web page ever, unless the extension is actually used?I guess we know why Grammarly never has any problems raising more funding.
by vhantz on 3/29/25, 2:53 PM
by regularjack on 3/29/25, 3:38 PM