1208763 - Treat chrome-extension:// and moz-extension:// schemes as equivalent

Status: RESOLVED WONTFIX

(WebExtensions :: General, defect, P3)

Description

[Dan Callahan [:callahad]]

The docs for chrome.i18n, https://developer.chrome.com/extensions/i18n, encourage constructing resource URIs by prepending "chrome-extension://" to the value of @@extension_id.

Despite supporting @@extension_id, we only recognize the moz-extension:// scheme. We should tread chrome-extension:// as an alias to moz-extension:// for greater extension compatibility.

For instance, this breaks the Reddit Enhancement Suite: https://github.com/honestbleeps/Reddit-Enhancement-Suite/blob/v4.5.4/Chrome/browsersupport-chrome.js#L116-L117

Comment 1

[Dan Callahan [:callahad]]

This no longer blocks Bug 1208765, as RES has moved away from this API.

Comment 2

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

I think we're going to try to avoid doing this.

Comment 3

[Andy McKay]

Wanting to close based on comment 2, no reports of this blocking anyone either. If you disagree callahad please re-open.

Comment 4

[Dmitry Artamoshkin]

I'm porting extension from Chrome to WebExtensions API and having several fragments in my css files where I'm using "chrome-extension://" scheme, e.g. 
in font-face:
  src: url(chrome-extension://__MSG_@@extension_id__/css/fonts/SourceSansPro-Regular.otf) format("opentype");

or for loading images:
  background: url('chrome-extension://__MSG_@@extension_id__/img/spinner32.gif') center center no-repeat;

Having that alias would be very handy. Otherwise I need to rewrite all occurences of "chrome-extensions".
Or does it have another workarounds? How am I supposed to load local extension files?

Comment 5

[Andy McKay]

In this use case is chrome-extension://__MSG_@@extension_id__/ needed? I'm able to set a CSS like:

    src: url(Fertigo_PRO.otf) format("opentype");

And it resolves to my local extension and loads the font in both Firefox and Chrome.

Comment 6

[Dmitry Artamoshkin]

It's true for backgound, popup, options pages, but it's not working in content-scripts.

Comment 7

[Andy McKay]

Ah thanks, let's re-open then.

Comment 8

[Kris Maglione [:kmag]]

Relative URLs work in all static CSS. Dynamically-generated CSS has other options for creating absolute URLs.

Comment 9

[Dmitry Artamoshkin]

Ok, it works in Firefox, but doesn't work like this in Chrome. It means that I need to add extra modifications to port my extension into Firefox anyway.

The css rule:
background: url('/img/spinner.gif')
injected by content-script into some page
in Chrome: will be loading from the target page
in Firefox: will be loading from extension resources