31–40 of 69 posts
No need to rely on IntersectionObserver() or even for JavaScript to be enabled -- Adtech vendors (like Google) can now detect scroll position server-side!
[0] - https://docs.google.com/document/d/1e8ZbVyUwgIkQMvJma3kKUDg8...
The post says "Firefox: No public signals" - does that mean there is no word from Firefox if it'll be implemented in Firefox?
[0]: https://news.ycombinator.com/item?id=19602877 > Under "privacy considerations": "so slightly more information about the user's scrolling position on the embedding page is exposed" and "a deferred cross-origin image gets an additional piece of information about the user's scrolling position".
Why they say they are pushing this: * "Speed up the load of above-the-fold content, since there will be less competition for network resources during the initial page load" Why don't they just set a low priority for offscreen images and resources? Isn't this the entire premise for HTTP/2, that multiplexing with priorities and flow control would load the important data first? Do servers not implement the spec correctl…
Why they say they are pushing this: * "Speed up the load of above-the-fold content, since there will be less competition for network resources during the initial page load" Why don't they just set a low priority for offscreen images and resources? Isn't this the entire premise for HTTP/2, that multiplexing with priorities and flow control would load the important data first? Do servers not implement the spec correctl…
You seem to be missing a few things: - data usage is correlated with battery usage, which is important on mobile - the http2 prioritization point is only half valid. Two big assumptions that probably don't hold in practice: whether the implementations actually implement priority correctly, all the way through the stack (e.g. perhaps some servers have a suboptimal implementation?), And whether having a bazillion low p…
And what delicious irony if they couldn't solve this with HTTP/2 because of servers not implementing the spec correctly or having weird undocumented quirks (their reason for not enabling pipelining despite it working just fine).
The downside of this is that it assumes that I am always online, and I can never know if a page has finished loading. Say I load an article in a background tab to read later, then go somewhere without WiFi like, say, an airplane. I read the first page, hit the space bar, and see gray boxes. Now I need to either scroll all the way through any article I want to read later (unless "infinite scroll" happens), or save it…
It’s good they’re implementing this, but it will mislead people to thinking the whole website is ready to use. It’s a shame an option couldn’t be “load the rest after page load”.
Why they say they are pushing this: * "Speed up the load of above-the-fold content, since there will be less competition for network resources during the initial page load" Why don't they just set a low priority for offscreen images and resources? Isn't this the entire premise for HTTP/2, that multiplexing with priorities and flow control would load the important data first? Do servers not implement the spec correctl…
I use Google Fi and I use less than one gigabyte a month: not because I'd like to, but because I don't want to pay for mobile data when I don't have to.
Why they say they are pushing this: * "Speed up the load of above-the-fold content, since there will be less competition for network resources during the initial page load" Why don't they just set a low priority for offscreen images and resources? Isn't this the entire premise for HTTP/2, that multiplexing with priorities and flow control would load the important data first? Do servers not implement the spec correctl…
The reality is that lazy loading images really does help webpage performance, especially on mobile. You cannot properly implement it in the browser without additional information from the page developer - because you'll never know which images are so important that they will always need to be loaded, and which ones can be lazy loaded once they're almost in view.
We're talking about the addition of one attribute to the tag here. There's no conspiracy, and there's no ulterior motive.
Why they say they are pushing this: * "Speed up the load of above-the-fold content, since there will be less competition for network resources during the initial page load" Why don't they just set a low priority for offscreen images and resources? Isn't this the entire premise for HTTP/2, that multiplexing with priorities and flow control would load the important data first? Do servers not implement the spec correctl…
You meant to say that are aren't trying to hide it, right?
Earlier quoted context omitted.
You seem to be missing a few things: - data usage is correlated with battery usage, which is important on mobile - the http2 prioritization point is only half valid. Two big assumptions that probably don't hold in practice: whether the implementations actually implement priority correctly, all the way through the stack (e.g. perhaps some servers have a suboptimal implementation?), And whether having a bazillion low p…
Their own customers are using less than 15 GB per month, how much battery could they possibly save on the radio? A single video will use more radio time than days of image downloads in the browser. Furthermore, Google themselves didn't mention battery savings but just fewer bytes sent. And what delicious irony if they couldn't solve this with HTTP/2 because of servers not implementing the spec correctly or having wei…