5 ms·
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 rena
by MattDaEskimo 3y 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.
- 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.