UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 OPR/57.0.3098.116

Example URL:

Steps to reproduce the problem:
1. Some icon fonts allows you to generate the actual font files with different glyphs to save the space, for example https://icomoon.io/

2. Generate font icomoon.ttf for one site with
3. Generate font icommon.ttf for Chrome extension with different glyph
4. Put 1st font on the website
5. Use 2nd font in the extension
6. The font used in the extension will be rendered correctly
7. The font used on the website will be using the cached version of the font used in the extension, thus missing the correct glyphs

What is the expected behavior?
The same font files should be checked for the file size / crc checksum to distinguish them from each other, even if the font filename is the same, because it could have different glyphs in it

What went wrong?
Local (I assume remote too), fonts with the same filename, but with DIFFERENT glyphs in it (like those in icon fonts, when you can select glyphs to be included in the final compiled font files) are rendered incorrectly when 2 different sites/extensions uses the same font name. I guess it's a bug in the caching mechanism, it should detect differences in the font files by checking exact font file size or it's checksum.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? Yes 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 70.0.3538.102  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 32.0 r0

Don't reuse the same resources from the cache across the website / extension even if the resource filename is the same.