←back to thread

Et Tu, Grammarly?

(dbushell.com)
279 points dbushell | 2 comments | | HN request time: 0.421s | source
1. preinheimer ◴[] No.43515079[source]
My extension problem story is a bit different. We distribute an extension that makes it easy to switch between proxy servers for geolocation testing.

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.

replies(1): >>43516584 #
2. horsawlarway ◴[] No.43516584[source]
Yeah, similar boat here. 1pass still breaks opening the chrome sidepanel UI from content scripts in other extensions. They screw up the trusted flag that indicates the event is coming from a user interaction.

Ultimately, as someone in the extension space for more than a decade now, Google is really at fault... Manifest v3 is just crappier than it should be in a LOT of ways (entirely outside the politics of the ad blocker changes - which is a whole different can o worms).

Overall, I think the quality of the chromium codebase feels a lot lower than it used to.