4 ms·
Because forms could be easily hidden behind other elements, and checking if those forms are hidden that way comes at the expense of CPU. Autofill is a bad idea
by ravenstine 9y ago
Because forms could be easily hidden behind other elements, and checking if those forms are hidden that way comes at the expense of CPU.
Autofill is a bad idea in general. I've never willingly used it, yet somehow I'll discover that somehow there's still autosaved form data in my browser. Better turn the thing off all together.
- paulryanrogers 9y agoFeels like the number of things to turn off is growing out of hand.
- jasonkostempski 9y agoIt's been way out of hand for a long time and every update of every crucial piece of software has something new. The only major software I haven't felt to need to comb through all the settings looking for new useless features, telemetry, nag screens, re-enabled previously disabled garbage, etc. after every update is Linux.
- y4mi 9y agoLinux is a kernel though. you don't need to comp through the windows NT changelog either. Its the bundled adware that's the problem, and you can get that in some linux distributions as well.
- jasonkostempski 9y agoSorry, Xubuntu.
- SimeVidas 9y agoI’m not a browser engineer, but I’m pretty sure checking if an element is rendered on the screen is not CPU intensive. Browsers maintain an entire rendering tree (parallel to the DOM) for that exact reason.