You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found no existing issue matching my feature request
This request is related to Millennium, and not a request for a specific theme/addon
Describe the feature you'd like!
After a long time using SFP, I'm trying out Millennium for its plugin support. I noticed that some themes weren't loading correctly since the css is loaded before the steam css, so you need to put !important after a lot of things you would need to otherwise, or else steam's default css will take over.
It's a relatively small change but it would be nice to have millennium css moved to the end of <head>, or after <body>, which is where the Stylus extension injects.
Anything else?
Millenium load order
Stylus load order example
The text was updated successfully, but these errors were encountered:
This one I made is the main one I noticed, it's just a snippet for more compact webkit context menus: compact-menu-webkit.css
Expected (SFP):
Millennium:
in devtools
adding !important to everything would technically solve this but that feels like more of a workaround than a solution
JunkiEDM
changed the title
[Suggestion] Ensure millennium css is injected after steam css
[Suggestion] Ensure millennium css is ordered after steam css
Jan 19, 2025
Before Requesting
Describe the feature you'd like!
After a long time using SFP, I'm trying out Millennium for its plugin support. I noticed that some themes weren't loading correctly since the css is loaded before the steam css, so you need to put
!important
after a lot of things you would need to otherwise, or else steam's default css will take over.It's a relatively small change but it would be nice to have millennium css moved to the end of
<head>
, or after<body>
, which is where the Stylus extension injects.Anything else?
Millenium load order
Stylus load order example
The text was updated successfully, but these errors were encountered: