1385472 - Error when I click "Pocket" button: "Security Error: Content at about:pocket-saved?pockethost=[...] may not load or link to chrome://pocket/content/panels/fonts/FiraSans-Regular.woff."

Status: NEW

(Firefox :: Pocket, defect, P3)

Description

[Daniel Holbert [:dholbert]]

Whenever I click the Pocket button in my Firefox Nightly toolbar, these get logged to my Browser Console:
=========
Security Error: Content at about:pocket-saved?pockethost=getpocket.com&premiumStatus=1&inoverflowmenu=false&locale=en-US&panelId=10 may not load or link to chrome://pocket/content/panels/fonts/FiraSans-Regular.woff.

downloadable font: download failed (font-family: "FiraSans" style:normal weight:normal stretch:normal src index:0): bad URI or cross-site access not allowed source: chrome://pocket/content/panels/fonts/FiraSans-Regular.woff   firasans.css:1:12
=========

Looks like we're referencing a font that we're not allowed to reference, so it fails (and we must be rendering with some fallback font, I guess).

We should either remove the bogus font reference, or wire it up so that it can succeed.

Comment 1

[Daniel Holbert [:dholbert]]

I'm still seeing this bug in recent Nightlies, BTW.  (My current browser session is 58.0a1 (2017-09-29) -- yes, I need to restart to install a day or so's worth of updates --  and I can reproduce this right now.)

Comment 2

[:Gijs (he/him)]

(In reply to Daniel Holbert [:dholbert] from comment #1)
> I'm still seeing this bug in recent Nightlies, BTW.  (My current browser
> session is 58.0a1 (2017-09-29) -- yes, I need to restart to install a day or
> so's worth of updates --  and I can reproduce this right now.)

Yep, and I would take a patch to fix it, but while it's not breaking any actual functionality I down-prio'd it because we've presumably already shipped this and nobody really cared besides the error spamming up consoles everywhere, so while we're focused on 57...

(this may have happened sooner if it wasn't literally an hour ago that I discovered there's several months of untriaged bugs in this component and so I'm going through them...)