Jump to content
@matt – nailed it.
“As an aside: the entire issue would be fixed easilly using current tech if we had the ability to tell browsers to not pre-fetch images. i.e., behave as browsers used to. Itâ€™s actually the browserâ€™s â€œperformance enhancementâ€ which is the problem here.”
This is a browser problem, if we want to get this done right – not stick a thumb in the leak, the vendors have to rethink prefetching/rendering and/or give us better means to influence that. A CSS load:none property might be nice for example.
The work being done by @wilto and co is awesome – I don’t think this detracts from that, but hoping for a cleaner solution isn’t a bad thing.