Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.
userChrome.css vs. Add-on
I've heard that running too many Add-ons can impact browser performance; is that equally true of the same functionality in userChrome.css ?
For example: With Firefox 4, users wanting to change the minimum tab width no longer can use "browser.tabs.tabMinWidth" in about:config .
To restore this functionality, an Add-on has been created*, or one can add an entry to userChrome.css
Which is more efficient performance-wise?
- Custom Tab Width 1.0.1
- This userChrome.css entry is working for me:
min-width: 0px !important; max-width: 950px !important;
Toutes les réponses (1)
While it's possible for userChrome.css to slow down Firefox (depending on what it contains), the snippet you posted here is fairly efficient and should not cause any measurable effect on performance.
The add-on may or may not slow down Firefox, depending on how it is written. The author of that add-on is a member of the Firefox development team, and should be aware of common performance problems, so I would expect that the add-on will also not cause any slow-down.