51–60 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!
What? As far as I know this feature is completely client-side.
The post says "Firefox: No public signals" - does that mean there is no word from Firefox if it'll be implemented in Firefox?
There is an open Firefox bug about it: https://bugzilla.mozilla.org/show_bug.cgi?id=1535749 But the last comment raises concerns about privacy implications it may have. So, I think that right now it is unclear whether Firefox will eventually implement it and in what form.
Firefox is also planning to add support for off-screen image lazy-loading. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1535749
No need to rely on IntersectionObserver() or even for JavaScript to be enabled -- Adtech vendors (like Google) can now detect scroll position server-side!
What? As far as I know this feature is completely client-side.
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…
> Most phone plans are unlimited or have data capable of watching movies. On what do you base this claim? My experience is the opposite - most people I know have less than 3GB/month. Do you have any actual data?
It is also my experience that unlimited bundles (which aren't unlimited anyway, they're just limited to an amount that virtually nobody hits which is quite a difference from "we can make them use as much data as we want") are rare rather than the norm.
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…
Tons of web pages (especially e-commerce sites where initial visible page load time is critical) already do this, just with more complicated code.
The new attribute’s value names look poorly chosen. “Lazy” and “eager”. Why don’t they use existing vocabulary like “deferred“ for lazy, and a new, equally professional word for eager.
Earlier quoted context omitted.
Wow, how can this conspiracy-theory-like nonsense be voted to the top of the comments? I thought Hacker News was a rational place. 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 t…
No we're talking about every website having to make this work because the default is to not require loading the resources or else be blamed for not being compliant with a spec forced on them by Google through their browser monopoly. Google should need some really good evidence to support this. What points do you disagree with, and why? Where are the metrics? If it's better performing than just priorities and flow con…
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…
Wow, how can this conspiracy-theory-like nonsense be voted to the top of the comments? I thought Hacker News was a rational place. 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 t…
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…
Wow, how can this conspiracy-theory-like nonsense be voted to the top of the comments? I thought Hacker News was a rational place. 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 t…
Wasn't part of the spec and Mozilla is doing it via a page permission. Just Google about the chrome autoplay audio and you'll see plenty of issues about how they rollout features.
Google has shown this is exactly what they plan to do with their Monopoly before with chrome-specific features that require the developer to be aware of.