userContent.css is not loaded for profiles using XDG directories on Linux
Categories
(Core :: DOM: CSS Object Model, defect)
Tracking
()
People
(Reporter: DeepChirp, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
69.33 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:147.0) Gecko/20100101 Firefox/147.0
Steps to reproduce:
- Start Firefox 147 on Linux and create a new profile using the XDG directory layout (profile located under
~/.config/mozilla/firefox/...). - In the new profile directory, create a folder named
chrome. - Inside that folder, create a file
userContent.csswith the following contents:@-moz-document domain("example.com") { body { background: red !important; } } - In
about:config, set:toolkit.legacyUserProfileCustomizations.stylesheets = true - Restart Firefox.
- Open https://example.com.
Control experiment:
Create another profile using the legacy directory layout under ~/.mozilla/firefox/... and repeat the same steps.
Actual results:
- When using an XDG-based profile (
~/.config/mozilla/firefox/...),userContent.cssis never loaded. - The background of example.com does not change.
- DevTools Inspector shows no rules from userContent.css.
- However,
userChrome.cssdoes work in the same XDG profile.
In contrast:
- When using a legacy profile under
~/.mozilla/firefox/...,userContent.cssworks normally, and example.com turns red.
This indicates that only userContent.css fails under XDG, while userChrome.css loads correctly.
Expected results:
userContent.css should load normally in XDG-based profiles, just like in legacy profiles.
The background of example.com should become red, and the rules from userContent.css should appear in the Inspector.
Comment 1•11 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Startup and Profile System' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•11 months ago
|
Comment 2•11 months ago
|
||
:gerard-majax, since you are the author of the regressor, bug 259356, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 3•11 months ago
|
||
Redirecting to Thinker, because I'm not working on that anymore
Comment 4•11 months ago
|
||
Could you provide the content of about:support?
| Reporter | ||
Comment 5•11 months ago
|
||
Comment 6•11 months ago
|
||
According to what is provided, userContent.css is loaded. Please check legacyUserStylesheets in the file .
One of differences between userContent.css and userChrome.css is userContent.css will be used in the content processes while userChrome.css should be used in the chrome/parent process. ~/.config/mozilla is denied by the sandbox broker. I am not sure if a content process is able to load it although ~/.config/mozilla/<profile>/chrome is read-only.
| Reporter | ||
Comment 7•11 months ago
|
||
I'm sorry, I don't understand what you mean. I have already enabled toolkit.legacyUserProfileCustomizations.stylesheets. userChrome.css works, but userContent.css doesn't. However, when I use the old configuration path(~/.config/mozilla/<profile>/chrome), both work – even with the same file content. I don't know how else to troubleshoot this. Perhaps you could try to reproduce it locally.
Comment 8•10 months ago
|
||
The severity field is not set for this bug.
:mossop, could you have a look please?
For more information, please visit BugBot documentation.
Updated•10 months ago
|
Updated•10 months ago
|
Updated•10 months ago
|
Description
•