[Lin][macOS][Fx57] userContent.css @import not working when e10s is enabled

[aris-t2]

[Lin][macOS][Fx57] userContent.css @import not working when e10s is enabled

[MarkRH]

One thing, make sure the top of userChrome.css doesn't have @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); in it or the @import won't work. Just in case anyone else reads this. I only mention it because I was importing Aris's stuff into my existing userChrome.css.

[grahamperrin]

… browser.tabs.remote.autostart.2 …

Lesser-known, I find this boolean easier (to toggle, without memorising any integer):

browser.tabs.remote.force-disable

[Aris-t2]

I can confirm this for the userContent style "top level image", but this projects alternative appearance settings for about:addons and about:preferences are working with and without electrolysis (multiple content processes).

Strange this issue only affects Linux and macOS, but not Windows.

[Corben78]

Looks like @import is also not working properly in userChrome.css for me. Wether e10s is enabled or not.
When I put the content of the css files I want to include (e.g. classic_squared_tabs.css, tabs_below_navigation_toolbar.css, tab_close_on_active_tab_only.css, tab_close_show_on_hover_only.css) directly in the userChrome.css file, it's working.

[Aris-t2]

So the problem is Firefox/Mozilla, right? Nothing I can't change about then.

[Corben78]

Yeah, I think it's on Mozilla's side to fix this. As mentioned in the starting post, this is just a hint that @importmight not work properly, if other's are stumbling over these issues and wonder.

[Corben78]

Oh dear. I made a mistake.
The @import is working in userChrome.css.
I was commenting out lines with // instead of /*, as I thought this is for single line comments allowed.
Just realized when using /* all settings from userChrome.css are working. Mea culpa.

The issue for userContent.css is present on Firefox Quantum (57) for Linux though.

[Aris-t2]

So still no progress on this one.
It is more likely userContent.css support ends before that bug is fixed.

[Aris-t2]

Looks like the issue is fixed.

Tested with:
Ubuntu 18.04
Firefox 60 (64 bit)