New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 776878 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Nov 9
Cc:
█ krajshree@chromium.org
pdr@chromium.org
rdevlin....@chromium.org
█ nainar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

tabs.insertCSS in an extension no longer works for web fonts

Reported by k...@luminance.org, Oct 20 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Steps to reproduce the problem:
1. use tabs.insertCSS to insert a .css file that loads one or more web fonts, for example the css for https://fonts.google.com/specimen/Lato

What is the expected behavior?
The web font should be loaded or an error should be emitted in the console of the extension's background page or the actual webpage

What went wrong?
The font doesn't load

WebStore page: https://chrome.google.com/webstore/detail/viramate/fgpokpknehglcioijejfeebigdnbnokj?utm_source=chrome-app-launcher-info-dialog

Did this work before? Yes A month ago

Chrome version: Version 64.0.3245.0 (Official Build) canary (64-bit)  Channel: canary
OS Version: 10.0
Flash Version: 

My guess is something subtle has changed such that the way I load the font isn't kosher anymore, but I don't know what. The .css file is embedded in the extension because loading it off Google's servers would cause unpleasant stalls sometimes, and the woff2 files are also embedded in the extension. I've attached the .css file to make it easy to find it.

This latest Canary rollout broke a bunch of other stuff too so it's unpleasant that developer tooling remains near-nonexistent in this area (injected stylesheets and other extension content).
lato-woff.css
3.0 KB View Download

Comment 1 by k...@luminance.org, Oct 20 2017 

I forgot to mention that I also have Lato installed locally, so the local() references in the .css should at least be applied even if the woff2 files are rejected, but they aren't either. My rules that set an element's font to vmLato *are* being injected and show up in devtools, but computed styles show that Chrome is not using the font.

Comment 2 by rkalavakuntla@chromium.org, Nov 7 2017

Cc: rdevlin....@chromium.org pdr@chromium.org
Components: -Platform>Extensions Platform>Extensions>API
Labels: Needs-Triage-M64

Comment 3 by nainar@chromium.org, Nov 9 2017

Cc: nainar@chromium.org
Could you test this again now that https://chromium.googlesource.com/chromium/src.git/+/3857f5dccf0f16288947c8c3c79b2a9a5bbd72b5 has landed?

Comment 4 by krajshree@chromium.org, Jan 3 2018

Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback
kg@ - Could you please check the issue using latest canary #65.0.3309.0 as the issue seems to have been fixed as per comment #3.

Thanks...!!

Comment 5 by swarnasree.mukkala@chromium.org, Nov 9

Status: WontFix (was: Unconfirmed)
As there is no update from the reporter since a long time, marking this issue as WontFix.
Please feel free to raise a new bug if any issues are observed on the latest Chrome builds.

Thanks..
►

Sign in to add a comment