Open Bug 1613927 Opened 6 years ago Updated 3 years ago

DevTools Fonts panel does not react to dynamically applied font faces

Categories

(DevTools :: Inspector, enhancement, P3)

72 Branch
enhancement

Tracking

(Not tracked)

People

(Reporter: me, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

  1. Opened https://www.kijijiautos.ca/
  2. Opened Developer Tools -> Inspector -> Fonts
  3. Reloaded the page
  4. Opened Fonts -> All Fonts on page
  5. Copied the URI of the first font

Actual results:

The shown and copied URI was https://www.kijijiautos.ca/static/fonts/LarsseitRegular-kern-5b5db003.woff2

After pasting "½" anywhere on the page the URI is updated with the correct value. Correct value is also shown if the developer tools are open after the page load.

Expected results:

The URI should have been https://www.kijijiautos.ca/static/fonts/LarsseitRegular-hint-all-1bd7b3f0.woff2

The page in question uses "2 stage font loading" as described on https://www.zachleat.com/web/css-tricks-web-fonts/

Component: Developer Tools → Inspector: Fonts
Product: WebExtensions → DevTools

Indeed, the Fonts panel does not react to dynamically loaded resources, like font files / font faces.

Until this is addressed, the workaround is to click any node in the Elements panel, then copy the font face URL from the All Fonts section. The node selection makes the Fonts panel do a fresh query for matching fonts which will catch any recently loaded fonts.

Status: UNCONFIRMED → NEW
Type: defect → enhancement
Ever confirmed: true
Priority: -- → P3
Summary: Developer tools cache old value of overridden font-face → DevTools Fonts panel does not react to dyanamically applied font faces
Summary: DevTools Fonts panel does not react to dyanamically applied font faces → DevTools Fonts panel does not react to dynamically applied font faces
Component: Inspector: Fonts → Inspector
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.