4 ms·
Was it actually a Chrome bug though? It only happened when the Grammerly desktop app was installed. My guess is grammerly is doing something sketchy.
by tedivm 3y ago
Was it actually a Chrome bug though? It only happened when the Grammerly desktop app was installed. My guess is grammerly is doing something sketchy.
- bayindirh 3y agoMaybe adding Grammarly created enough of a lag causing the GIF file to be shown?
- nonethewiser 3y agoThat doesnt hold when you consider they opened the gif in the browser with and without grammarly and it only crashed with. So its not simply a bad gif and chrome.
- AnimalMuppet 3y agoDoes 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.
- majormunky 3y agoIt 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."
- MattDaEskimo 3y agoI'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.
- meandmycode 3y agoThe 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.
- nonethewiser 3y agoBut only in Chrome. Not necessarily inconsistent with what you’re saying, just an interesting wrinkle.
- isleyaardvark 3y agoWhile 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.