5 ms·
Holy shit, just why? It makes virtually no difference. Neither applying CSS (they already use a lot) nor loading a file take any time.
by solarkraft 7y ago
Holy shit, just why? It makes virtually no difference. Neither applying CSS (they already use a lot) nor loading a file take any time.
- megous 7y agoYeah, sounds like a non-reason, my user CSS was like 5 lines. I'll have to run an extension that will be injecting JS/CSS into every page, to get the same effect. That will likely be slower. Not a speed improvement exactly. At least it's more powerful. I can replace any rule inside already loaded CSS. Useful to escape this braindead age of "font-size < 16px && font-weight < 400".
- bzbarsky 7y agoIf you have a user CSS, the "keep it working" pref has already been set for you, as of Firefox 68. So everything will keep working as it has.
- kevingadd 7y agoIt has to have been showing up in profiles for them to bother, nobody would go out of their way to disable it otherwise. They added a pref to turn it back on and then disabled it instead of the easy thing (just removing it) which is some engineering effort plus testing effort to make sure the pref works right. Silly to do that for nothing. Antivirus software does add a measurable delay to file operations sometimes, and each file is gonna be in its own sector so I could see them losing at least a few milliseconds there. Applying CSS does add overhead but the average user can't have that many rules in there so I suspect it's purely on the file i/o level.
- bzbarsky 7y agoNot just that, but in an earlier release code was shipped to set the pref for users who already had the file, so that anyone who already had one of these files would not observe any behavior regressions. And yes, file I/O was the issue.
- kevingadd 7y agoYeah, I checked and it was automatically enabled for me, so no regression.
- gregknicholson 7y agoThank you for doing this!
- bzbarsky 7y agoI can't claim credit for it; I hadn't even realized it had happened until I dug a little bit into the history while reading this thread. All I knew was that my userChrome.css was still working fine... ;)