RmDebArc_:tux:@toot.io to Firefox@lemmy.ml · 1 年前#Firefox doesn't need any new features to be more attractive for users, it just needs to make CSS theming more accessibles3.toot.ioexternal-linkmessage-square70fedilinkarrow-up1328arrow-down137file-text
arrow-up1291arrow-down1external-link#Firefox doesn't need any new features to be more attractive for users, it just needs to make CSS theming more accessibles3.toot.ioRmDebArc_:tux:@toot.io to Firefox@lemmy.ml · 1 年前message-square70fedilinkfile-text
#Firefox doesn’t need any new features to be more attractive for users, it just needs to make CSS theming more accessible Theme: https://github.com/Godiesc/firefox-one #FirefoxCSS #browserwar #customization @firefox
minus-squareunrushed233@lemmings.worldlinkfedilinkarrow-up1·1 年前Tell me more about that. How does it work?
minus-squareQuail4789@lemmy.mllinkfedilinkEnglisharrow-up1·1 年前Its like userchrome but for the contents of the webpage. You match on the url and write css that overrides the site’s css.
minus-squareunrushed233@lemmings.worldlinkfedilinkarrow-up1·1 年前So basically like a user style that you would use in Stylus? What are the differences, advantages/disadvantages?
or userContent.css
Tell me more about that. How does it work?
Its like userchrome but for the contents of the webpage. You match on the url and write css that overrides the site’s css.
So basically like a user style that you would use in Stylus? What are the differences, advantages/disadvantages?
my dude, this isn’t google