So I’ve made a small discovery even if it hasnt helped me find a solution quite yet. If I go to my firefox profile folder and open prefs.js I can search for toolkit.legacyUserProfileCustomizations.stylesheets and see that it is clearly listend and enabled. However, if I go to my prefs.js in my firedragon profile that setting is oddly completely missing. I cannot append it to the file, as it gets wiped when firedragon is relaunched. I tried making a user.js in the root of my profile and added user_pref("toolkit.legacyUserProfileCustomizations.stylesheets", true); as the only thing in the file, and this saw no change either.
Edit- Could this simply be because firedragon enables this setting by default, therefore it’s not listed? I see now that disabling the option has it appear in the prefs.js. Think I’m back to nothing.
Floorp (or Firefox upstream) enables it by default, we don’t have it set anywhere for FD.
I do not have the setting in my pref.js. I’m not sure how that file really works, I have had to mess with it in the past and it was not consistent in logic, as it is not now since my CSS works and I do not have the setting at all in pref.js.
Hello. If you check my github issue on floorp I had a response where someone said I can just ignore the userchrome file and dump the .css into the CSS folder. I tried that, and on floorp the theme kinda renders, but on firedragon I am again seeing no change at all. On both firedragon and floorp I have the Floorp.css and the Assets folder inside of /chrome/CSS/, and on floorp the theme tries to activate, however I am still seeing no change in firedragon.
That reminds me, that file is not part of the Release ZIP and I don’t have it on my machine.
It does not render at all for me.
This is your folder structure?
[🔴] × ls ~/.firedragon/usvfwpfj.test/chrome/CSS/
drwxr-xr-x - frank 7 Dec 00:49 chrome
drwxr-xr-x - frank 7 Dec 00:49 GTK
drwxr-xr-x - frank 7 Dec 00:49 Screenshots
.rw-r--r-- 110k frank 7 Dec 00:49 Echelon.css
.rw-r--r-- 17k frank 7 Dec 00:49 LICENSE
That reminds me, that file is not part of the Release ZIP and I don’t have it on my machine.
I was going to ask you about that, as I noticed as well that it is not in the release zip and was wondering why it was in the install instructions.
My folder structure is the same, except for me having the Floorp.css in the root CSS folder instead of Echelon as part of testing, and I have the Assets folder in the root of CSS as well. These steps get me rendering issues on Floorp, and no change here on firedragon.
Sorry for the screenshot, I am doing this one on a different machine and can’t copy off of it.
This is on Floorp and nothing. Since the instructions mention the use of the Echelon/userChrome.css file and we can’t find it, it is possible to check with the guy who created that theme?
7ncgu0p6.aero/chrome/CSS
❯ ls (base)
drwxr-xr-x - scrubby 7 Dec 00:49 Assets
.rw-r--r-- 2.1k scrubby 7 Dec 00:49 aero_button_glow.uc.css
.rw-r--r-- 109k scrubby 7 Dec 00:49 Floorp.css
This is my floorp CSS directory where it attempts to load the theme, I’m confused as to why this wouldn’t work on your end.
Sorry if I sound stupid, but on that gitgud repository I cannot find any way to create an issue, find an associated forum or any way to contact the dev, I had looked previously. Am I missing something there? I’ve not used that specific git site before.
I think you have to Sign In first and then you probably will see the button to create an issue.
I tried, since it’s powered by GitLab I thought I could use my GLab account, but it asks to create a Sapphire Account, I did not atm.
Sounds weird, people who are not signed in wouldn’t be able to see the ISSUE tab/pane, that does not make sense to me, maybe it is somewhat locked. However there is recent activity and there MRs pushed by other people, so some kind of interaction seems possible.
The README also doesn’t say anything about opening issues. Maybe the maintainer disabled that feature.
EDIT: Where are the other folders on your installation? Aero, GTK, JS… Just outside the CSS folder?
Floorp is under heavy dev for v12 which will include rewritten code and more features
That last point makes me think of 2 options right now:
We spend time trying to fix it on FD (needs to work 100% on Floorp first, that’s a dependency) at the risk of re-spending time trying to fix it once v12 comes out.
We wait for v12, make sure it works in Floorp v12 and then look into FD v12.
I do not know based on your experience, but based on mine the very most of the time it is well worth waiting for the new version to come out as a base to start troubleshooting. Things evolve quite fast so the wait is not 9 years like on Slackware (from v14 to v15).
Let me know what you think. It depends how bad you need that theme to work in the very short term too.
