Slashdot Mirror


Google Chrome To Feature Built-In Image Lazy Loading (bleepingcomputer.com)

An anonymous reader writes: Future versions of Google Chrome will feature built-in support for lazy loading, a mechanism to defer the loading of images and iframes if they are not visible on the user's screen at load time. This system will first ship with Chrome for Android and Google doesn't rule out adding it to desktop versions if tests go as planned. The feature is called Blink LazyLoad, and as the name hints, it will implement the principle of "lazy loading" inside Chrome itself.

Google engineers reported page load speed improvements varying from 18% to 35%, depending on the underlying network. Other browser makers have been notified of the Chrome team's plan, but none have provided input if they plan to implement a similar feature. Compared to most JS-based lazy loading scripts that only target images, Google implementation will also target iframes.

131 comments

  1. Will scrolling remain smooth? by Anonymous Coward · · Score: 0

    Cause if not I dont want it.

    Not that I use Chrome anyway.

    1. Re:Will scrolling remain smooth? by Anonymous Coward · · Score: 3, Funny

      Yes, it will remain perfectly smooth for people who don't use Chrome

    2. Re:Will scrolling remain smooth? by Anonymous Coward · · Score: 0

      We have the technology now to squeeze every last bit out of bandwidth, the savings being promptly donated to needy charities. So start helping others and quit bitching about a couple fractions of a second!

    3. Re:Will scrolling remain smooth? by jellomizer · · Score: 4, Interesting

      Your not seeing the big picture.
      Those megabytes you save per month, that you don't notice. Account for Exabytes of Ads Images, that their resources will not need to send onto sites that the information will not be seen.

      If you are going to charge per click why bother wasting your resources downloading data that will not be clicked.
      If you are charging for impressions, why scam your customers with extra charges until it actually has an impression.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    4. Re:Will scrolling remain smooth? by Anonymous Coward · · Score: 0

      1. A statement =/= bitching in of itself. Fractions add up. More resources =/= "using them irresponsibly, and wastefully is OK"

    5. Re:Will scrolling remain smooth? by sexconker · · Score: 1, Flamebait

      Fuck smooth scrolling. Just jump x lines down instantly, please. I don't want an animation, and I certainly don't need an animation that requires the GPU to do work for no reason. The distinct sound an Intel iGPU makes when smooth scrolling is torture to my ears. Even regular scrolling pisses me off. The only thing worse is the metallic whine of an M.2 SSD under load.

    6. Re:Will scrolling remain smooth? by rickb928 · · Score: 1

      So this is a revenue reducer. Excellent.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    7. Re:Will scrolling remain smooth? by Anonymous Coward · · Score: 1

      Yes, because touchscreen devices will really appreciate that.

      Just because you put your ear so close to the PCB you think you can hear the electrons vibrating doesn't mean nobody else should get a smooth scrolling experience.

    8. Re:Will scrolling remain smooth? by jellomizer · · Score: 1

      Actually it is a cost reducer.

      Sending Ads that will not be viewed is just wasting googles money sending the traffic. And if google can show a higher impression rate with their services then all the better.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    9. Re:Will scrolling remain smooth? by DontBeAMoran · · Score: 2

      Damn, is your father a dog or something?

      --
      #DeleteFacebook
    10. Re:Will scrolling remain smooth? by tepples · · Score: 1

      Then add a setting to enable smooth scrolling only for scrolling initiated by touch, not for scrolling initatied by arrow keys, the mouse wheel, or the up or down arrows on the scroll bar.

    11. Re:Will scrolling remain smooth? by Anonymous Coward · · Score: 0

      Nope. Lazy Loading, as currently done in jQuery basically makes you do a bunch of extra crap in the HTML, and then the Jquery script detects when the page has moved and goes "do I show this now?"

      It's fine for things like image carrosel's (where 90% of it might not be visible when the page loads,) but it's a truly awful thing when used on sites like Twitter, where it leaks memory like hell, and after a few hours of the page auto-updating, the tab inevitably crashes.

    12. Re:Will scrolling remain smooth? by Anonymous Coward · · Score: 0

      Doesn't matter. They broke HTTP. Chrome is dead.

    13. Re:Will scrolling remain smooth? by sexconker · · Score: 1

      I'm about 18 inches away from the NUC on my desk. If drag a scroll bar up and down I can hear an annoying clicking sound, almost like a softer, faster version of a hard drive (the system is running a M.2 SSD). This has been true for Intel iGPUs for over a decade. I have to disable shit like smooth scrolling, font smoothing, etc. on my work machines to reduce it (but not eliminate it). I'm fine with disabling them, because I generally hate those things anyway. It's a problem when I'm on a site that uses some god awful Google web font that expects you to have font smoothing / subpixel rendering bullshit enabled, then cranks the text size down.

      The last laptop I purchased (not for my own use, fuck laptops) has a Samsung SSD in it and it makes an awful whine when under load. This can be heard from across the room. Thankfully, its so fast that it's rarely under load. (Originally the laptop had a Toshiba SSD that had this issue, but to a lesser extent. I had to get it replaced because one of the USB 3 ports was shorted out.)

      Plenty of people have similar complaints the newer SSDs and complaints about coil whine have existed for ages.

    14. Re:Will scrolling remain smooth? by vlueboy · · Score: 1

      Plenty of people have similar complaints the newer SSDs and complaints about coil whine have existed for ages.

      Yes! It's good seeing I'm not the only one. For other /.ers who think we're crazy, I think there are two things in play
      0) Somewhat healthy hearing and not having reached the 40's.

      1) SSD noise. Work refreshed the HDD laptop with an new SSD system from the same maker (Dell's Elitebook) around 18 months ago. I'm surprised I stopped noticing it a few months after resigning to my fate. It took me about 5 months of hearing the coil whine from up to 6 feet away whenever the drive is spinning up.

      2) Scrolling whine. It sounds like a mix between white noise from radio stations and the SSD noises. It doesn't affect every brand of PC I've used, and it's only been present when using headphones as I scroll. I've experienced it on PCs as far back as a 386. Most recently on a Pentium 4, IIRC. It rarely comes out thru the speakers, if at all, so I'll second tepples in the issue being leaking from shoddy electronics.

    15. Re:Will scrolling remain smooth? by houghi · · Score: 1

      Why would Google want to block ads that are not from Doubleclick? Oh, wait. They are not doing it for our good, they are doing it for their good and by accident it is also for our good.

      Just because they are the enemy of our enemy does not them our friends.

      --
      Don't fight for your country, if your country does not fight for you.
    16. Re: Will scrolling remain smooth? by Anonymous Coward · · Score: 0

      SSDs don't "spin up" and they don't contain coils or switching power supplies.

    17. Re:Will scrolling remain smooth? by Shirley+Marquez · · Score: 1

      Hearing sounds from the computer that are related to display activity is common; I have experienced it on both laptop and desktop computers. It's not that you're hearing the displayed electrons directly. The actual cause is crosstalk between the wires that carry the video signal and the ones that carry audio to your speakers or headphones.

      One way to eliminate the problem is to move audio D/A conversion out of the computer. Listen through a USB headset or speakers, or use an external audio interface.

    18. Re: Will scrolling remain smooth? by Shirley+Marquez · · Score: 1

      SSDs don't contain coils or switching power supplies. But the motherboards and PSUs that provide power to them do, and they are a possible source of coil whine. Display noises can come from the switching power supply in the monitor as well as the one in the computer.

      Another common source of noise is crosstalk between the audio circuits in the computer and other signals that are present. You won't hear that kind of noise if you don't have any speakers or headphones connected, and it will usually go away if you switch to a USB headset or an external audio interface.

  2. Sigh by JMJimmy · · Score: 2

    Taking control and functionality away from the web developer because browser developers think they know what's best for everyone.

    1. Re:Sigh by sirber · · Score: 1

      View it as less javascript in your website, and as faster loading in other websites that you have no control over them.

      --
      Be or ben't
    2. Re:Sigh by Anonymous Coward · · Score: 1

      So everyone that loads an image offscreen and moves it onscreen once it loads so you don't see broken images while the page is loading will just have their pages break. Thanks Google!

    3. Re:Sigh by sirber · · Score: 1

      Why would one do that? KISS

      --
      Be or ben't
    4. Re:Sigh by Anonymous Coward · · Score: 0

      What the fuck? Ever heard of a progressive JPEG?

    5. Re:Sigh by JMJimmy · · Score: 1

      A simple slideshow? A row based thumbnail gallery? There are all sorts of systems that need this kind of functionality for smooth operation. There are alternate ways to do it but they're clumsy and screw up SEO.

    6. Re:Sigh by sexconker · · Score: 1

      Maybe just let the image load normally?

    7. Re:Sigh by Anonymous Coward · · Score: 5, Insightful

      You do realize that this is how the web is supposed to be, right? Web developer develops a page, the browser determines how to render the page. This is exactly how things are supposed to be.

    8. Re:Sigh by Anonymous Coward · · Score: 0

      because browser developers

      Specifically Google. I mean they couldn't even get along enough with the other WebKit developers, Blink is going to be so splintered away from the rest of the web if they keep this nonsense up.

    9. Re:Sigh by Dog-Cow · · Score: 0

      Anything that harms SEO is a blessing.

    10. Re:Sigh by squiggleslash · · Score: 1

      A hack that has no guarantee of working anyway will break if Google implements something obvious that probably should have been in every browser from Mosaic onwards? Heavens forfend!

      --
      You are not alone. This is not normal. None of this is normal.
    11. Re:Sigh by harrkev · · Score: 1

      Taking control and functionality away from the web developer because browser developers think they know what's best for everyone.

      Yes, because clearly you WANT to load that advertisement further down on the page. That is clearly more important than the image right in front of you.

      --
      "-1 Troll" is the apparently the same as "-1 I disagree with you."
    12. Re:Sigh by Anonymous Coward · · Score: 5, Informative

      You keep talking but keep ignoring the fundamental underlying philosophy of how the web was developed.... it is when fucktard developers insist on overriding the browser that problems happen. There is no requirement for a webpage to render for the entire page if it is not visible. Please stop making stuff up, admit you don't understand, educate yourself and then comment.

    13. Re:Sigh by Anonymous Coward · · Score: 0

      Aaand they do. They're just choosing to download and display the portion that's visible first, and save the off-screen stuff to download after the visible stuff is done, so the user has a better experience.

    14. Re:Sigh by viperidaenz · · Score: 2

      Browsers are supposed to render everything in the viewport. Ie: only the visible part. Once the content of the viewport is determined, anything else is wasted cycles.

      There is no HTML standard that says a browser needs to render the entire page. In fact there a provisions for displaying content before the entire page is even retrieved.
      eg: The table element was designed so a browser could start rendering it before the element was retrieved.

    15. Re:Sigh by Anonymous Coward · · Score: 0

      Taking control and functionality away from the web developer because browser developers think they know what's best for everyone.

      But neither of these solutions gives power to the end user.

      My two pet peeves with modern web design are (1) position:fixed CSS wankery wasting my vertical space on a fucking menu bar, and (2) lazy load.

      For #1, I'd like a client-side preference to make that attribute Just. Not. Work. Fuck the webdev who designed it. Fuck having to reload a Javascript bookmarklet or go into the element inspector and remove the offending element altogether. (I used to effectively have this with a MITM proxy, but that didn't work so well when everything went HTTPS :)

      For #2, I've got a pile of RAM available, but my bandwidth is often intermittent and slow. The more webdevs (and now, browserdevs) try to "help" me by forcing lazy-load on their users, the more I find myself wanting client-side option to turn every IMG tag with SRC="uselessthumbnail.png" data-src="therealimage.jpg" into "SRC=therealimage.jpg" and let the images load in the background at full resolution. The machine can sit there and fill its pipe with a thousand images for a few minutes, I can put it in Airplane Mode, get on the plane, and have a lightning-fast web "experience" without a single byte of further transmission.

      Tinfoil hat moment: lazyload was never intended to help the user; it was intended as a mechanism for forcing the user to turn Javashit on and scroll up/down the entire page in order to see the graphs and charts and images -- and in so doing, trigger all the analytics and tracking scripts that indicate the user actually read the entire article.

    16. Re:Sigh by JMJimmy · · Score: 1

      Which would make a load-index attribute worthwhile, so that images load in the order of importance instead of as chosen by the browser. Otherwise you're just deferring the load time until scrolling which means they could scroll right past something that hasn't loaded yet.

    17. Re:Sigh by harrkev · · Score: 1

      Wouldn't the browser be in the perfect position to know where each image will be? I mean, the browser is the one that HAS to know, since it has to display those images.

      --
      "-1 Troll" is the apparently the same as "-1 I disagree with you."
    18. Re:Sigh by Anonymous Coward · · Score: 0

      No but progressive AUTO...

    19. Re:Sigh by JMJimmy · · Score: 1

      Actually, if they are designated as "supporting the suggested default rendering" they are required to:

      In the absence of style-layer rules to the contrary (e.g., author style sheets), user agents are expected to render an element so that it conveys to the user the meaning that the element represents, as described by this specification.
      An element is being rendered if it has any associated CSS layout boxes, SVG layout boxes, or some equivalent in other styling languages.

      - https://www.w3.org/TR/2017/REC...
      - https://www.w3.org/TR/2017/REC...

    20. Re:Sigh by JMJimmy · · Score: 1

      I should have also quoted this, which specifically addresses the issue of off screen elements:

      NOTE: Just being off-screen does not mean the element is not being rendered. The presence of the hidden attribute normally means the element is not being rendered, though this might be overridden by the style sheets.

    21. Re:Sigh by JMJimmy · · Score: 1

      Depends on how the developer wants it rendered. There are many techniques which will trigger a repaint cycle on the displayed content to add layers to create an effect. Using jQuery's animate() is a simple example of where the developer would know the load-index that would work best for the animate() cycle but the browser would not know until after it repaints. Currently loading these images off screen allows the animation to execute in a predictable manner once it verifies the images have been rendered.

    22. Re:Sigh by JMJimmy · · Score: 0

      You should really know what the fuck you're talking about before ranting and calling people "fucktards"

      https://www.w3.org/TR/2017/REC...

    23. Re:Sigh by JMJimmy · · Score: 1

      That's not how it works.

      Here's the specification: https://docs.google.com/docume...

    24. Re:Sigh by harrkev · · Score: 1

      Thanks. I didn't know that. I am more of a hardware guy.

      --
      "-1 Troll" is the apparently the same as "-1 I disagree with you."
    25. Re:Sigh by JMJimmy · · Score: 1

      There are valid, non-tracking, reasons for lazyloading, however, I agree with you completely. The control scheme should always be User>Developer>User-agent

    26. Re:Sigh by Anonymous Coward · · Score: 0

      Did you even bother to read the link you provided as evidence of your being right?

    27. Re:Sigh by Anonymous Coward · · Score: 1

      not quite, web developers are supposed to develop the page to spec. Browsers are supposed to render the page according to spec. As such web developers can depend on how iframes, scripts images etc can be consistently rendered or available. lazy loading breaks that. I could understand if it was lazy background loading where they do the visible first then pass off the rest to background threads, but by doing it this way you make a shitful experience for users that don't want the top section of the screen, which is usually just ad laddened bullshit anyway.

    28. Re:Sigh by Anonymous Coward · · Score: 2, Insightful

      Just to elaborate a bit more as you are apparently slow, the first freaking sentence of your link says "*User agents are not required to present HTML documents in any particular way. ".

      This is an important part of the way the web is supposed to work. You see way back n the day, the founders of the web understood that people would be viewing the web on different hardware, and in the future it would be viewed differently. Some folks might be sight imparted and be using readers. Some would not be able to support graphics, some may be limited in other ways. HTML was the language sent to the browser and the browser would be responsible for HOW to display it.

      Yes, we now support CSS and with the introduction of CSS3, the server is able to suggest (note, not control) how a page is laid out. If a browser chooses to ignore one of the W3C's suggestions, it is free to. Really, this is by design. It is not a flaw. So if your browser chooses to render images that aren't displayed immediately, it is free to. If it chooses to not render them, that is also fine.

      Web developers really need to understand this. It is one of the underlying tenets of the web and it really, really makes me sad when folks who make their living doing this stuff just don't get it.

    29. Re:Sigh by Anonymous Coward · · Score: 0

      And you ignore the very first sentence in your link :*User agents are not required to present HTML documents in any particular way. " You demonstrate your lack of understanding.

    30. Re:Sigh by JMJimmy · · Score: 1

      If you continue reading that paragraph you'll come to a link for the "supporting the suggested default rendering". ie: being standards compliant.

      Upon clicking that link you'll find this:

      User agents that are designated as supporting the suggested default rendering must, while so designated, implement the rules in 10 Rendering. That section defines the behavior that user agents are expected to implement.

      ie: if you're in standards mode you MUST render below the fold as described (see "Off-Screen" note and various expectations on rendering non-hidden elements)

      In quirks mode they're free to do whatever they want. Which mode it's to be rendered in is also something the developer specifies.

    31. Re:Sigh by thegarbz · · Score: 1

      Taking control and functionality away from the web developer because browser developers think they know what's best for everyone.

      Based on the internet I see today, yes they really know much better than nearly all web developers.

    32. Re:Sigh by JMJimmy · · Score: 1

      As posted before, you need to continue reading the paragraph, click on the link where you'll find the "not required" means quirks mode/non-standard compliant user agents can do whatever they want but a standards compliant one must follow the rendering specified in the standard.

    33. Re:Sigh by KingMotley · · Score: 1

      I suggest you go back and re-read the entire spec, because it completely supports the Anonymous Cowards' perspective.

      It goes into very very specific details that not only suggest he is correct, but actually says this it even suggests doing so "In particular, even user agents that do implement the suggested default rendering are encouraged to offer settings that override this default to improve the experience for the user, e.g., changing the color contrast, using different focus styles, or otherwise making the experience more accessible and usable to the user."

      Sorry, but the spec is almost screaming to please do this. LazyLoading (intelligently) will improve the experience for the user.

    34. Re:Sigh by JMJimmy · · Score: 1

      Allowing opt-in by the user to override the default is completely fine. The browser complies with the user's preferences which fits with the User>Developer>Browser paradigm. The way the proposal is setup is that it would be opt-out, ie: break the standard in favour of speed

      I actually talked with one of the people who are proposing this and he agreed that it does break the standard. His view was that the standard could be rewritten to accommodate it or the proposal could be changed to opt-in, which would allow developers or users to decide which elements were lazy loaded. I think he's underestimating how much it would break to make it work with the standard. Since there are no downsides to an opt-in system that's probably where it'll end up.

    35. Re:Sigh by Waccoon · · Score: 1

      What bugs me is that most browsers lay out the page based on image dimensions, and hardly anyone seems to use the width and height attributes. Loading images on demand isn't bad if the page layout is static.

      Wait... what am I saying? For better or for worse, what web developer uses static page layout anymore? Most likely as soon as the browser launches, every web page will use Javascript to preload images -- for SPEED -- and lazy load all the content!

    36. Re:Sigh by Anonymous Coward · · Score: 0

      Not since HTML3.2 mate - I've always groused about the changes made in HTML4 and even more so in 5 which only serve to tighten the control developers have on the way stuff displays, to the point where I can ONLY use Chrome for a lot of the bigger sites.

      We should all go back to HTML3.2! Sites loaded so much faster in the HTML3 days... and that was with modems! It's insane that we have connections 100 times faster and web pages take *longer* to load than they did then! And what do HTML4 and 5 add that isn't just either sparkle, or stuff that only works in Chrome anyway??

    37. Re:Sigh by Anonymous Coward · · Score: 0

      Thanks. I've given up arguing with him... I was developing for the web back when Mosaic was the shit and have been saddened by the lack of fundamental understanding of the philosophy of the web. Most likely he's a young kid with no appreciation for theory...

    38. Re:Sigh by viperidaenz · · Score: 1

      Images in HTML 5 are replaced elements
      The content of replaced elements is not part of the CSS rendering model, so is not required to "render" the element as far as HTML/CSS is concerned.

      Sma thing goes with videos, a browser is not required to download the video file to render a element.

    39. Re:Sigh by JMJimmy · · Score: 1

      That only applies of scripting is off. If scripting is on (default) it *must* immediately replace (render) the image when it's downloaded.

    40. Re:Sigh by viperidaenz · · Score: 1

      There is no requirement stating when an image must be downloaded.

      Where does it say a browser must immediately render a replaced element with it's content when it's downloaded?

      You started whinging about standards compliance but now you've stopped referencing standards.

      Please enlighten me, I must have missed something.
      Also, HTML5 compliance does not require a browser supports Javascript, so scripting being on or off has nothing to do with it.
      In reference to JavaScript/ECMA262 "User agents are not required to support the languages listed above."
      https://www.w3.org/TR/2014/REC...

    41. Re:Sigh by JMJimmy · · Score: 1

      HTML5 does specify this sort of thing:

      An img element has a current request and a pending request. The current request is initially set to a new image request. The pending request is initially set to null. The current request is usually referred to as the img element itself. ...
      In a browsing context where scripting is disabled, user agents may obtain images immediately or on demand. In a browsing context where scripting is enabled, user agents must obtain images immediately.

    42. Re:Sigh by viperidaenz · · Score: 1

      oh right, the "living standard"
      Which will say that until someone submits a pull request to change it. Like Google, who are a member of WHATWG

    43. Re:Sigh by JMJimmy · · Score: 1

      Entirely possible - however in this case highly unlikely. The reason that line exists at all is because with scripting you *need* the ability to load images off screen. A basic animation that you don't want something as heavy as video or a canvas element is done that way. Something simple, like loading a logo with negative values so that it starts off screen and gradually makes it's way on screen. That's an expected function and there's no reason any developer should think they can't do that in a browser.

      The simple answer is that they'll make it opt-in so that the developer controls it and the user can override it but the user will have to expect some things will break if they do.

  3. SYNC/ASYNC by darkain · · Score: 1

    As long as they include a SYNC/ASYNC parameter to the HTML elements to override the user agent's behavior, we're all good here. In fact, being able to manually specify ASYNC without any JS at all would be freaggin godsend as a developer!

  4. So... the 90s are back? by Anonymous Coward · · Score: 0

    I'm pretty sure that is what many browsers did in the 90s all the time.

    1. Re:So... the 90s are back? by DontBeAMoran · · Score: 1

      We're back in the 90s?

      Note to self: buy thousands of Bitcoins and sell them all around Christmas 2017.

      --
      #DeleteFacebook
    2. Re: So... the 90s are back? by Anonymous Coward · · Score: 0

      Side note to self: don't fuck that pretty waitress, it's YOUR MOTHER!!!!

  5. For Chome on Android I want the laziest loading. by Anonymous Coward · · Score: 0

    No loading of images at all.

  6. But the adverts and miners will still load by Anonymous Coward · · Score: 0

    Say no to Googzilla, stick with the XUL browsers, extending your freedom.

  7. Are you high? by Anonymous Coward · · Score: 1

    This is to be implemented as an html attribute, so control is still in the hands of developers. It's a great idea, frankly.

    Lazy load JS has all kinds of problems. You know how pages jump around while you scroll? That is JS lazy loading. If it is implemented natively in the browser, then the browser can do things like figure out which images to pre-load and when to do it based on variables that JS does not have access to (network speed, latency, current load...). Further, it is guaranteed to use much fewer resources than lazy-loading JS, which hooks into onscroll and onresize events, then loops over _every_ lazy-loaded image on the page, calculates its position relative to the window, and _then_ lazy loads. It is a complete and utter hack.

    Hell, I would be perfectly happy with a simple "defered" attribute on image tags, like we have with script tags. Then I could just chuck this hacky shit to the curb.

    1. Re:Are you high? by JMJimmy · · Score: 1

      If they're doing it as an HTML attribute they should scrap "deferred" and do "load-index". Developer can choose when to load images then and anything below the line can be "deferred" by placing the load-index after the above the line content. It could also be easy to set this via JavaScript for dynamic loading to different screen sizes.

    2. Re:Are you high? by JMJimmy · · Score: 2

      I located the specification and this is not exactly being implemented as an HTML attribute. It's being implemented by default and for iframes it has an attribute to turn it off. That attribute does not exist for images.

      If they made it the opposite so that you need to specify you want an image/iframe lazyloaded - I'd have no problem with that. The developer is given a new tool to optimize but isn't forced into anything.

      Also, it breaks the 5.2 rendering standards

    3. Re:Are you high? by Anonymous Coward · · Score: 0

      That's just pointless busy-work for site devs, since the browser knows what's on-screen already.

  8. What's the benefit? by Anonymous Coward · · Score: 0

    Sure, this reduces page "load time" but it's the part of the load time you don't care about - content below where you're looking. All this means is when you scroll down you'll have to wait for more stuff to load that would otherwise have loaded in the background.

    1. Re:What's the benefit? by viperidaenz · · Score: 1

      When I'm on my phone I don't want the dozen or so images of "look what [celebrity] looks like now, you won't believe it!" ads to waste my data allowance.

  9. NeW wOrd by Anonymous Coward · · Score: 0

    DeFunCt

    Did you now ot? DO now.

  10. Infinitely yes! by Anonymous Coward · · Score: 0

    Yes. Do this. Stop these dumb browser-overriding features.
    I'm getting rather annoyed at all these so-called features in browsers that are saying a big "fuck you" to web-developers.
    I'd rather just have it opt-in for developers. Say an HTML attribute on the tag you want to lazy-load. We already have a "lofi" attribute for images and I think video.

    I better be able to turn this shit off or that browser is getting dropped hard.
    It damn well better stay on crapdroid Chrome. (a browser that continues to get buggier with time)

    1. Re:Infinitely yes! by DontBeAMoran · · Score: 1

      We already have a "lofi" attribute for images and I think video.

      What is this "lofi" attribute you're speaking of?

      --
      #DeleteFacebook
    2. Re:Infinitely yes! by DontBeAMoran · · Score: 1

      If you are referring to lowsrc, I hope you're aware that it has been deprecated and replaced in HTML5.

      --
      #DeleteFacebook
  11. Even better is by Spy+Handler · · Score: 1

    installing an ad blocker (I recommend uBlock Origin) so most of that crap don't get loaded at all.

    Even best is disabling javascript. I recommend "Quick Javascript Switcher".

  12. Wut about full-screen adverts that load first? by Anonymous Coward · · Score: 0

    I really hate going to a web site, wait for it to load and then suddenly BOOM! a full-page image is the first thing the appears before all the other parts of the web page. Where's the "X" so I can close it? Huh, it doesn't have one? Why can't I scroll past this? Oh, it's covering up the scroll bar.

    It's like trying to watch a movie that I paid for at the theater but before the projector starts, a really loud guy sitting in the seat in front of you stands up, turns around and starts yelling you about some product or service he thinks you might be interested in because the movie kinda is about that. He won't shut up and he's blocking the screen until you agree to read the brochure he's holding out in front of him.

    Yeah, that's why we all hate advertisements -- not because we purposely want to web page NOT to get ad revenue it's because the ads are really obnoxious.

    1. Re:Wut about full-screen adverts that load first? by Merk42 · · Score: 1

      I really hate going to a web site, wait for it to load and then suddenly BOOM! a full-page image is the first thing the appears before all the other parts of the web page. Where's the "X" so I can close it? Huh, it doesn't have one? Why can't I scroll past this? Oh, it's covering up the scroll bar.

      Sounds like that ad doesn't follow The Coalition for Better Ads standards, and as such, will be blocked by Chrome as of February 15th.

    2. Re:Wut about full-screen adverts that load first? by tepples · · Score: 1

      Which only means viewers will be seeing a lot more "To continue, unblock our ads in Chrome and disable tracking protection in Firefox" notices on websites, including websites linked from Slashdot stories.

    3. Re:Wut about full-screen adverts that load first? by Merk42 · · Score: 1

      That's fine, you can either agree to the terms, or not visit the site.

    4. Re:Wut about full-screen adverts that load first? by viperidaenz · · Score: 1

      Or won't be blocked by anything if they're hosted by the site you're visiting. Like what quite a few news websites are doing now on their mobile optimised pages.

  13. Hate hate so much hate by DNS-and-BIND · · Score: 0

    I fucking hate this. Instead of "middle click to open new tab in background, come to page all loaded" it's now "scroll down, wait irritatingly long for images to load, scroll down again and it takes forever again, repeat forever." Yaknow, maybe it's not worth saving a few megabytes for things like this.

    But if designers aren't constantly designing new things that nobody needs, they're going to be out of work. So I don't see this kind of user-hostile design stopping any time soon. Designers will never put their future employment opportunities behind what users want.

    --
    Shutting down free speech with violence isn't fighting fascism. It IS fascism!
  14. It'll be Awful by Okian+Warrior · · Score: 4, Interesting

    Taking control and functionality away from the web developer because browser developers think they know what's best for everyone.

    Gab.ai has this for their pages, and it's awful.

    Scrolling down, you have to wait a moment or two to load each image as it comes into view. It's a complete time waster.

    I run the slider up and down a few times to activate all the images, then go browse another page while the Gab page loads. I can't imagine doing this for *all* pages on the internet - it would be an unacceptable wast of my time.

    It's similar to the google image search, which only shows a quarter page of thumbnails, but if you scroll down it suddenly loads another quarter page... jumping the slider and causing you to lose your place while scanning through the images.

    Again, it's intended for some purpose which is not "convenience of the viewer". We're not the customer, so it probably saves their real customers (the advertizers) somehow.

    Both of these are for non-phone browsing, for which data rates and caps don't apply. I can see why phone browsing might want to save data, but why inflict this on desktop PCs?

    1. Re:It'll be Awful by hackertourist · · Score: 1

      I couldn't agree more. My usual MO is to load a bunch of tabs in the background, in the expectation they'll be done downloading/rendering/jumping around before I open the tab. This way, I rarely have to wait for a webpage to finish loading, which is bliss.
      RAM and bandwidth are cheap enough that I can afford to have lots of background tabs, all fully rendered and waiting for me.

      This 'feature' would break that.

    2. Re:It'll be Awful by tepples · · Score: 1

      It'd also break my MO with a laptop: load a bunch of documents in browser tabs to read later, close the lid to put it into suspend, board the bus, open the laptop, and read.

    3. Re:It'll be Awful by Anonymous Coward · · Score: 0

      I couldn't agree more. My usual MO is to load a bunch of tabs in the background, in the expectation they'll be done downloading/rendering/jumping around before I open the tab. This way, I rarely have to wait for a webpage to finish loading, which is bliss. RAM and bandwidth are cheap enough that I can afford to have lots of background tabs, all fully rendered and waiting for me. This 'feature' would break that.

      And while we're on the subject, look at this shit:

      https://www.bloomberg.com/news/features/2018-01-31/facebook-really-wants-you-to-come-back

      Load this page with Javashit turned off - you load the same 2-megabyte full-sized .GIF as you do with Javashit turned on. Because it's tagged as .lazy-img__image { ... filter: blur(5px); }

      Fucking webdevs. Same bandwidth cost to end user and to the publisher; the only difference is that the site is intentionally degraded to people who don't enable Javashit in order to support the webdevs' lazy loading.

    4. Re:It'll be Awful by bill_mcgonigle · · Score: 1

      If you're reading down normally, why does the browser need to preload more than two pages worth of images? If you do read down normally you'd never notice if it's loading a page ahead. It sounds like Gab is too aggressive for its use case. If you rocketed down to the bottom it would be like a normal page load time, no?

      I can see why phone browsing might want to save data, but why inflict this on desktop PCs?

      You know lots of people around the world live on metered home Internet connections, right?

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    5. Re:It'll be Awful by Anonymous Coward · · Score: 0

      My guess is this inflates the amount of time a user spends on a page.  I bet staying on one page for 2 seconds is worth more than two pages for 1 seconds.

    6. Re:It'll be Awful by JMJimmy · · Score: 1

      You're assuming you've got a quality connection that's able to keep up and your WiFi is not dropping packets (common problem in old apartment buildings due to reflection issues/signal conflicts)

  15. Could be good, could be bad by Anonymous Coward · · Score: 0

    On a fast connection this could work, but it seems odd that we have browsers that preload tabs when you so much as accidentally mouse over them to give better responsiveness but don't fully load the tab that has focus to save on bandwidth. Don't thess goals seem a little, well, contradictory?

    Also on some (poorly written) webpages the width of say the text changes depending on the size of the images to either side. I would imagine it would be rather vexing to have the width of the central element changing as you scrolled.

  16. Talk to rest of Google by Imazalil · · Score: 1

    Kinda odd as the rest of Google is figuring out how to waste more of our data by cramming preloaded "suggested" items into their apps (Android Chrome & Maps for example).

    Also, expect to see new memory-usage benchmark-advertorials - Look how much less memory Chrome uses! It's magic!

  17. GOOGLE IS THE PROBLEM by Anonymous Coward · · Score: 0

    Don't they realize the other hand is bloating webpages up with their near monopoly on online advertising? Plus their analytics, big CSS fonts, and promotion of more and more javascript frameworks etc.

    captcha:domineer

  18. Shutup antisemitic retard APK by Anonymous Coward · · Score: 0

    I see that retard Alexander Peter Kowalski is posting his antisemitic conspiracy rants again.
    He really needs to lean to lay off the InfoWars but sure seems to like to make even Alex Jones look sane by comparison.
    Maybe I should stop disproving his security advice and maybe he will stop lashing out and making posts like the one above.
    Although posts like the one above and his other ravings do show a severe mental disability.

  19. Moron web developers by williamyf · · Score: 0

    If moron web developers indicated the size (both in pixels and MB) of every image they use, and used preogresive Mpeg everywhere an mpeg is used, browser developers would need to resort less to hacks like this

    JMNSHO

    --
    *** Suerte a todos y Feliz dia!
    1. Re:Moron web developers by viperidaenz · · Score: 1

      What about moron /. commenters who confuse "progressive jpeg" with "preogresive mpeg"?

    2. Re:Moron web developers by williamyf · · Score: 1

      Touche!

      But the point Still stands.

      --
      *** Suerte a todos y Feliz dia!
  20. Satellite and cellular home Internet have caps by tepples · · Score: 1

    non-phone browsing, for which data rates and caps don't apply.

    You appear not to have priced out satellite Internet, fixed cellular Internet, or DSL in some parts of Iowa. They still very much have caps. (Source: Exede.com; Verizon.net)

  21. Commercials in cinema by tepples · · Score: 1

    Anonymous Coward wrote about prestitial ads on websites:

    It's like trying to watch a movie that I paid for at the theater but before the projector starts, a really loud guy sitting in the seat in front of you stands up, turns around and starts yelling you about some product or service he thinks you might be interested in because the movie kinda is about that. He won't shut up and he's blocking the screen until you agree to read the brochure he's holding out in front of him.

    You mean like the commercials that movie theaters have been showing for decades to supplement box office revenue? I imagine theaters do this because the movie studio gets a cut of ticket sales, but not of overpriced popcorn or these ads.

    Chrome will soon block ads on sites that use prestitial ads with countdown or any prestitials on mobile.

  22. Making fonts smaller by tepples · · Score: 1

    Don't they realize the other hand is bloating webpages up with their near monopoly on online advertising?

    What else would you suggest for a site to continue to pay its writers? Each site selling static ad space to advertisers? Paywalls? Or firing all employees and becoming a butcher, as Slashdot user bingoUV suggested?

    Plus their analytics, big CSS fonts, and promotion of more and more javascript frameworks etc.

    By "big CSS fonts", do you mean large point size or large byte size?

    If the latter: Say a site uses a lightweight JS library built on the advances in vanilla JS since IE <= 11 sunset, self-hosts it, self-hosts Matomo (formerly called Piwik) for analytics, and offers a meaningful functionality subset when JS is off. How is the site supposed to make its fonts smaller to download?

  23. Site Testing by Anonymous Coward · · Score: 0

    How will this affect web site testing?

    I'm already fighting with waits in Selenium to deal with other javascript lazy loading issues.

  24. Doesn't take an SOB to hear processor load by tepples · · Score: 1

    I'm no son of a bitch, but I can still hear noise in the 100-8000 Hz band when the CPU and GPU loads change on some machines. I'm not quite sure if it's electrical noise leaking into the audio output or magnetostriction in the power supply.

    1. Re:Doesn't take an SOB to hear processor load by Shirley+Marquez · · Score: 1

      If you hear it even if you don't have speakers or headphones connected it's in the power supply, or in the switching regulators on the motherboard or video card. The lowest voltage provided by a typical computer power supply is 3.3 volts; the lower voltages that are used on modern CPUs and GPUs are produced by regulators elsewhere. In some Intel CPUs the regulator is on the CPU die.

  25. Replacements for lowsrc by tepples · · Score: 1

    W3C's official replacement for lowsrc= is to use formats that support incremental loading, delivering a low-detail image early in the file and the difference between low- and high-detail images later. JPEG has progressive refinement, and PNG has Adam7 interlacing. But not all formats support this; for instance, I don't see a way to make it work for an SVG illustration or for anything animated.

    What other replacement did you have in mind, if any?

    1. Re:Replacements for lowsrc by DontBeAMoran · · Score: 1

      The only other solution is CSS-based, resolution-range-dependent images. Which is a neat idea if implemented properly in the browser and used correctly by the coder.

      --
      #DeleteFacebook
  26. Does preparing for scroll "waste cycles"? by tepples · · Score: 1

    Browsers are supposed to render everything in the viewport. Ie: only the visible part. Once the content of the viewport is determined, anything else is wasted cycles.

    Is it necessarily "wasted cycles" to prepare for further scrolling of the viewport? My use case often involves loading a document, disconnecting from the Internet, and then scrolling the viewport to the remainder of the document.

  27. This could be Great by Big+Bipper · · Score: 1

    Now all we have to do is figure a way to tell the browser that all the adds are off the visible section of the page and we'll never see them.

    --
    You live and learn, or you don't learn much.
    1. Re:This could be Great by Fly+Swatter · · Score: 1

      It is google, pretty sure they already have countermeasures for that, it is their business model after all.

  28. Progressive MPEG? Since when? by tepples · · Score: 1

    preogresive Mpeg

    I've heard of progressive JPEG and Adam7-interlaced PNG for still images, but not progressive MPEG. The closest thing I can think of is a CSS trick to display a JPEG filmstrip as an animation, where the underlying JPEG is stored progressively.

    1. Re:Progressive MPEG? Since when? by williamyf · · Score: 1

      You are absolutely right. I meant progresive JPEGs.

      Sorry.

      But, on the bright side, thanks to you I learned about Adam7, and this CCS trick.

      So, something good came out of my absentmindedness....

      --
      *** Suerte a todos y Feliz dia!
  29. Failure to RTFA; exclude domains from search by tepples · · Score: 1

    [Dealing with anti-adblock in] websites linked from Slashdot stories

    not visit the site.

    And get moderated down for making uninformed comments based on not having read the featured article.

    Now how should I tell a major web search engine which domains (plural) I don't want to visit so that it doesn't return them in search results that it presents to me? Google Search limits the number of -site:example.com terms that I can add to each query.

    1. Re:Failure to RTFA; exclude domains from search by Merk42 · · Score: 1

      Now how should I tell a major web search engine which domains (plural) I don't want to visit so that it doesn't return them in search results that it presents to me? Google Search limits the number of -site:example.com terms that I can add to each query.

      Same way you used to tell the Yellow Pages not to list business you don't want to visit.

    2. Re:Failure to RTFA; exclude domains from search by tepples · · Score: 1

      Did the Yellow Pages allow businesses that you don't want to visit to clog up almost the entire first page of results in a particular category?

    3. Re:Failure to RTFA; exclude domains from search by Merk42 · · Score: 1

      Now you're talking about ads on the Google (and others?) search results page itself , my how this goalpost has moved.
      But yes, people were allowed to advertise in the Yellow Pages, with those ads being of larger sizes if they chose to spend more.

    4. Re:Failure to RTFA; exclude domains from search by tepples · · Score: 1

      I'm not talking about ads on Google Search. I'm talking about organic results on Google Search when the organic results that require consent to tracking as a condition of viewing the document outnumber the organic results that do not.

    5. Re:Failure to RTFA; exclude domains from search by Merk42 · · Score: 1
      Which again, goes to what I said

      Same way you used to tell the Yellow Pages not to list business you don't want to visit.

      ...meaning Google, Yellow pages et al, are meant to be a listing of results matching a search term, not any sort of filtering based on the company doing a thing you don't like.
      If, somehow, you'd want Google to implement this feature, you'd have to consent to Google tracking you to figure out what particular things a website does that you don't like.

  30. Bottom line by reboot246 · · Score: 1

    If your website pisses me off because of the way it loads (no matter which browser I'm using), I'm simply never coming back there.

    While I'm bitching, if you use light gray text on a barely darker gray background, may you rot in Hell forever.

  31. the law of totally expected consequence by epine · · Score: 1

    This is all a huge exercise in gaming metrics, a natural by-product of Google's OKR system, according to the Law of Totally Expected Consequence.

    I define a page as being loaded as when I can scroll down without noticing that the page wasn't really loaded in the first place.

    From my vantage point, load times are getting worse and worse.

    If the system instruments itself to determine the amount of image load delay exposed to the end user, and then adjust the loading threshold to the activity patterns of the user, so that the exposed delay occupies a sweet spot between interactivity and network efficiency, that would constitute a benchmark refined, rather than a benchmark gamed.

    I'll even allow them to conduct a weighted average on visible load delay where page cruft is multiplied a small number (negative values, in many scenarios, are highly encouraged).

    YouTube is presently pissing me off, because they are loading the video element itself, without so much as the page title or upload date visible for three to four seconds. I hardly ever stick around to watch a video with comments disabled. It's a sign of fear on the part of the channel creator, and that fear is almost always fully justified. But I regularly have to wait for four seconds now with a mostly white screen to decide whether the video makes the cut.

    The system is loaded, all right, by design.

  32. Increased marketing too.. No thanks by Anonymous Coward · · Score: 0

    Just in time prefetching / speculative loading is not new. It's a marketing wet dream. It would be OK if pages were downloaded the same regardless of how they are rendered. Instead ad companies will be able to tell when content is viewed since it won't be _loaded_ until needed. They could still schedule requests based on initial load, just don't tie it to presentation events like scrolling, mouse over, etc.

    * Don't know why Slashdot is shadowbanning posts but trying again.

  33. INVASION of the JUDENoidz (JEWgle) by Anonymous Coward · · Score: 0

    Jews believe this of all they call goyim/gentiles (any non-jew): Jews = biggest racists of all (for which they "jew guilt" you for no less! They're hypocrites known as thieves all thru history or were Argentines in the 1940 under Perrone, Spanish inquistion & Spain 1492 (Christopher Columbus the jew https://duckduckgo.com/?q=%22C... sailed to the US for them to create it), France (1306), Egypt (despoiled/robbed by jews), Arabs (pre & post 1948), England (1330 Edward longshanks), Romans under titus, Russia pogroms and Germany who got rid of them from their nations nazi german's too? No. Driven into DESERTS ages ago! Don't wonder why after all those exilings above. Should anyone doubt any of this see Jacob Javits' crony Rosenthal spill the beans on it https://www.youtube.com/watch?v=D4zMVZ8HnFI/ where he called all Christianity fools for helping Israel and the biggest scam of all time per their beliefs below from their Talmud. This is the province of the synagogue of Satan (Khazar/Pharisees whom Jesus Christ himself kicked to the curb out of the temple & they killed him for it. Jeremiah did the same to them also + the Essenes could not stand them either breaking away from the pharisee corruption):

    Maria Abramovic satanist spirit cooker pal of Hillary Clinton the Voodoo queen is a jew https://www.google.com/search?...

    Just like Hillary Clinton's mentor Saul Alinsky author of rules for radicals book dedicated to Lucifer

    "Most Jews do not like to admit it, but our god is Lucifer â" so I wasnâ(TM)t lying â" and we are his chosen people. Lucifer is very much aliveâ Harold Rosenthal http://www.thetruthseeker.co.u...

    Jewish rabbi openly admits to satan worship use white children's blood they kill for passover bread, infiltrating and subverting the catholic church, creating the Jesuit order https://www.youtube.com/watch?... and https://www.youtube.com/watch?...

    Barbara Spectre, a jew, tells everyone it's jews orchestrating the muslim migrant problem in Europe https://www.youtube.com/watch?v=MFE0qAiofMQ/ . No migrant raping of women in Poland. Tons in Sweden. Do the math. Use common-sense. This is to get muslims and other goyim/gentiles to wipe one another out as incompatible cultures that will clash and always have.

    Rabbi A. Finkelstein ADMITS their greatest enemies are ARABS and WHITES (blacks too) whom they wish to kill one another in a 'theater of war' which they find AMUSING https://www.youtube.com/watch?...

    Finkelstein also admits JEWS DID 9/11 https://www.youtube.com/watch?... profiting by it (and that 3,000 jews employed there did not show up for work that day knowing about it beforehand).

    Finkelstein also admits JEWS are going to destroy the U.S. Dollar and dumping it for other world currencies and gold to destroy the United States.

    George Soros who funds groups to create division in the USA?? A jew. One who sold his own jew people into death for the nazis.

    Zucker now FIRED @ CNN is another frying publicly for lying about "russians" and John Bonifield a producer @ CNN said it is bs. Van Jones did also.

    Bernie Madoff (who made off with everyone's money, especially construction union pensions) shows the thieving nature of the JUDEN!

    Eric Schmidt had to step down @ JEWgle (a jew).

  34. Shipping browsers? by Anonymous Coward · · Score: 0

    This laziness is fine as long a I can turn it off. I want a checkbox that reads "no slouching"

    Why is google "shipping" browsers? Odd word choice.

  35. Great by Anonymous Coward · · Score: 0

    Now how about not auto-playing YouTube videos by default, Google?

  36. Shit! there goes my ad revenue by Anonymous Coward · · Score: 0

    All my 1x1 tracking pixels are at the bottom of the page.

  37. -site: query tedium; first-party tracking by tepples · · Score: 1

    Google, Yellow pages et al, are meant to be a listing of results matching a search term

    A list of domains to exclude from results could be construed as "a search term", as the same functionality is available with -site: terms. My practical problems are that 1. entering a long list of -site: terms every time is tedious, and 2. Google Search caps the number of -site: terms in one query. My ideological problem is the intent inherent in the fact that Google Search used to let a logged-in user store what amounts to a list of -site: terms to apply to all queries but has since removed this feature.

    you'd have to consent to Google tracking you to figure out what particular things a website does that you don't like.

    I'd let Google track my use of Search to save my domain blacklist, but not my visits to third-party sites operated by companies not part of Alphabet.