| ▲ | t1234s 5 days ago | |
Don't feature like this waste bandwidth and battery on mobile devices? | ||
| ▲ | babanooey21 5 days ago | parent | next [-] | |
It preloads pages on mouse hover over the a href link. On mobile there are no mouse hover events. The page can be preloaded on "touchstart" event which almost definitely results in page visit. | ||
| ▲ | MrJohz 5 days ago | parent | prev | next [-] | |
The point of this proposal is to bring this feature under the control of the browser, which is probably better placed to decide when preloading/prerendering should happen. It's already possible to do something very similar using JS, but it's difficult to control globally when that happens across different sites. Whereas when this feature is built into the browser, then the browser can automatically disable prerendering when the user (for example) has low battery, or is on a metered internet connection, or if the user simply doesn't want prerendering to happen at all. So in theory, this should actually reduce bandwidth/battery wastage, by giving more control to the browser and user, rather than individual websites. | ||
| ▲ | radicaldreamer 5 days ago | parent | prev | next [-] | |
Not to mention laptops! Loads of people use those on battery power | ||
| ▲ | youngtaff 5 days ago | parent | prev [-] | |
Putting aside the lack of hover on mobile (there are other ways to trigger it) It’s not clear it will waste battery on mobile… not sure if it’s still the case but mobile radios go to sleep and waking them used a non-trivial amount of energy so preloading a page was more efficient than let the radio go to sleep and then waking it Need someone who’s more informed than I am to review wether that’s still the case | ||