undefined | Better HN

0 pointsAnimalMuppet2y ago0 comments

Does Grammerly hook something in Chrome? If not, then it's still probably a Chrome bug, even if some second-order effect of Grammerly is necessary to trigger it.

0 comments

majormunky2y ago

It looks like the desktop Grammerly app hooks into all sorts of things, "An all-in-one writing assistant that works on your desktop and in your browser. Use it in apps, word processors, email clients, and more."

MattDaEskimo2y ago

I'm thinking the same thing. It could be that Grammerly injects it's own loading spinner with the same filename into the HTML.

I wish they tried to simply rename the file instead of remove it.

meandmycode2y ago

The pr seems to suggest it's not the filename though given the new file was named the same and didn't crash.

I would guess grammarly is hooking chrome and potentially trying to read metadata about images, and the particular gif had metadata in a format they hadn't expected.

nonethewiser2y ago

But only in Chrome. Not necessarily inconsistent with what you’re saying, just an interesting wrinkle.

isleyaardvark2y ago

While something like that is worth a shot, the PR they shared showed the file as being ‘assets/images/loader-spinner.gif’. If the file name was the cause that bug would be everywhere.

j / k navigate · click thread line to collapse