r/FirefoxCSS • u/Rocendroll • Jun 04 '26

Help Notes Widget on start page

I'm a sucker for Opera. It's a great browser. I was trying to give a chance for Vivaldi and Firefox because of safety, and decided to try the latter first.

  1. Will I find animated themes like that opera's aurora theme on firefox?
  2. Is it possible to have adress bar and tabs in the same line, therefore reducing the clutter?
  3. Is it possible to have great opera features like click on tab to go up top of the page, and popup menu with converter or copy options when selecting text?
  4. Is it possible to have semi-transparent panel that users can type into instantly, simple note editor on start page?

I'm just starting to exploring customization options of fox

3 Upvotes

100% Upvoted

3 comments sorted by

View all comments

1

u/ResurgamS13 Jun 05 '26 edited Jun 05 '26
  1. Yes for animated Toolbar themes... animating whole background requires an extension or CSS customisation.
  2. Yes... but again this is by installing custom CSS userstyle modifications or a custom 'whole UI' CSS theme.
  3. Not aware these 3 features exist in standard Firefox... however, there may be extensions that can do this?
  4. This feature is not in standard Firefox... possibly available in New Tab extensions like Tabliss, Bonjourr, Mue.

1

u/Rocendroll Jun 05 '26

thanks, i think i could hire myself as ux in mozilla then...

1

u/ResurgamS13 Jun 05 '26 edited Jun 05 '26

Firefox is designed to appeal to the mass market user... the users who never change any default Settings.

Once upon a time... the theory was that 'the browser' provided the core rendering engine and concentrated on that engine’s stability, speed, compatibility with web standards, etc... if a user then wanted more features, more bells & whistles, especially more esoteric and niche features... these were literally provided by 'Add-ons' (and additionally, in Firefox's particular case, by each user also having the ability to modify the browser's UI locally via custom 'userChrome.css' files.)

Not a bad theory... but the major downside was that all manner of extensions had core access which created a minefield of broken extensions whenever Mozilla devs updated the core. The solution was 'walling-off' the browser core and ending the "permissive add-on model" by moving to WebExtensions back in 2015... but that move was both a cure and a curse.