search

aminomancer / uc.css.js

A dark indigo CSS theme for Firefox and a large collection of privileged scripts to add new buttons, menus, behaviors and other opinionated features. The theme is similar to other userChrome stylesheets, but it's intended for use with an autoconfig loader like fx-autoconfig, since it uses JavaScript to implement its more functional features.
Other
337 stars 27 forks source link

userChrome.css.mac-ui-fonts #25

Closed Mitezuss closed 2 years ago

Mitezuss commented 2 years ago

It is not a bug... just a question

How can i check if is working ? I did not see any effect (have installed all fonts) (i tried on fresh install)

Can give me some picture to compare ?

Thanks

aminomancer commented 2 years ago

There's a reason it says this lol

<!-- Please don't change or delete the template -->

What operating system? SF Pro is Apple's font so enabling this pref on macOS shouldn't have any significant effect. Might change the weights and stuff but the font is the same. If you're on Windows or Linux then show me a screenshot of something, I can identify the font.

You can easily tell whether it's working by opening the browser toolbox (Ctrl+Shift+Alt+i, or right-click my toolbox button if you have the script) to the "Style Editor" tab, find uc-misc.css, and delete line 480 where it says font-family: SF Pro Text.... If you have the font installed correctly, the font in your tabs and menus should immediately shift. If you don't, then you won't see any change since the SF Pro Text part will be ignored and it'll then proceed to Segoe UI then sans-serif in that order.

aminomancer commented 2 years ago

Did you download the fonts from Apple directly? You need to download the .dmg file, and then if you're on windows, open it in 7-zip, and double click the .pkg file inside the archive, then double click Payload~, then ., then Library, then Fonts, then select all the fonts in there and drag and drop them to your desktop or something. Then select all of them, right click > Install. Or whatever the equivalent is on linux. Right now you only need to do this with SF Pro (the first one on the website, SF-Pro.dmg), but I may incorporate the other fonts in the future, and they're all really good fonts, so I recommend installing all 5 anyway.

Mitezuss commented 2 years ago

Hi, thank for the reply

EDIT: Nevermind, now is working. (was a problem with uc-misc.css)

aminomancer commented 2 years ago

If there's a problem with uc-misc.css then I need to know what it is so I can fix it

Mitezuss commented 2 years ago

@aminomancer

Was a problem mine with the uc-misc.css, but your .css is working fine.

Regards.

PD: one extra question (:d just for know, i can not find info on google). is there a option like:

@supports -moz-int-pref

? maybe not =( (just bool -.-, should be cool have a int to choice)

aminomancer commented 2 years ago

I don't understand. You're editing uc-misc.css? Why? If you want to add custom rules you need to add them in custom-chrome.css, that's the only reason it exists. If you edit uc-misc.css then you're gonna lose your edits every time you update the stylesheet... and this theme gets updated almost every day.

No, -moz-bool-pref is a totally unique feature. It only works because it's boolean. @supports is boolean so any function fed into it must be boolean too. It would be theoretically possible to implement something like @supports -moz-string-pref("pref.name", "value") but that would require changing how @supports works I think. Btw, you can answer those kinds of questions yourself by using searchfox.

And really, -moz-bool-pref shouldn't exist. It's not really a good idea to have it. It should probably be removed. It's only exposed to Firefox's internals, so anyone wanting CSS to be aware of prefs could just make a script that sets an attribute based on the pref. Then the CSS can be aware of the attribute instead of the pref. That's safer.