Slashdot Mirror
Chrome Now Uses Scroll Anchoring To Prevent Those Annoying Page Jumps (techcrunch.com)
Google has updated its Chrome browser to fix the annoying page jumps that occur when pages are loading. While developers want pages to load the actual content of a page before additional ads and images appear, "the problem is that if you've already scrolled down, your page resets when some off-screen ad loads and you're suddenly looking at a completely different part of the page," reports TechCrunch. From the report: The latest versions of Chrome (56+) do their best to prevent these jumps with the help of a feature called scroll anchoring. Google tested scroll anchoring in the Chrome beta versions for the last year and now it's on by default. Google says the feature currently prevents almost three jumps per page view -- and, over time, that number will likely increase.
This site really has gone to shit on many levels. Endless page jumping is only the most recent annoyance.
Talking of page-jumps, chrome on iOS does a really annoying page jump when you hit the "load more stories" button...
Does it prevent those incredibly annoying jumps that happen when a website suddenly inserts a header at the top of the page after you scroll down a few lines? Because when I see those, I usually just close the page and make a mental note to not visit that site again.
The only website I have this problem with is Slashdot, which wants to cover the top 3rd of my web browser with an ad.
It didn't work very well when I enables it in testing a few months ago, but we'll see.
Page jumps make me actually angry. It's like a book snapping shut on you mid-sentence.
I'll never understand the rationality behind the google image search features. Or some of the "advanced" features on their text search.
Search for images and the page initially shows a fair number. Scroll down looking for the thing you want, and suddenly you trigger a 2nd pack of images to be loaded, scroll down some more and you trigger a 3rd set.
This means that if you *don't* find the image you want, you have to wait while the 2nd pack loads... except that it could have been loading while you were looking at some of the top images. I don't know why making the person wait for the 2nd pack is in any way useful.
Additionally, when the new pack loads it resets your position in the page and jumps the display somewhere. If you're actually interested in an image at the end of the first pack, you can be looking at it and suddenly the page jumps somewhere else.
I'm sure making the user wait and suddenly yanking the image of interest away is useful somehow. I just can't see how.
This wouldn't be that big of a problem if web designers would properly declare the size attributes on images.
So, two?
Our website has a bootstrap drop-down menu an each item in a list on a page. When the mouse hovered over an item that opened a submenu, the submenu would make the page grow, Chrome scrolled to the bottom, the mouse was no longer over the menu item and the submenu closed, shrinking the page and Chrome scrolled and the mouse was hovering over the menu again.
Rapid cycling of screen position and menu state was Not Good. At least you can turn off the anchoring...
Help! Help! I'm being repressed!
I've gotten so irritated at the damn next button being replaced with some damn link to crap. I've just started blacklisting every damn site I get sent to unfairly. But they keep changing the names of the same basic garbage.
why did this take so long for someone to do?
Simple web pages without "lazy loading" Javascript load faster and the additional burden on the server is negligible compared to the server side scripting most sites use to tie it all together. Web programmers just don't know what they're doing anymore. All they can do is add stuff and make everything a little bit worse every time. An efficient web site doesn't need dozens of third party sites or client side scripting just to display the static page. You guys need to stop turning web pages into Rube Goldberg machines. Turn Javascript off. Can you still read the page? No? STEP AWAY FROM THE KEYBOARD AND WAIT UNTIL PROFESSIONAL HELP ARRIVES!
Doesn't everyone use adblockers?
I never see ads, so I don't need to use one particular browser.
I could have used this on my phone a while back with the slashdot mobile app 2x2 adds. I stopped visiting /. on my phone because of it.
This is easily fixed in MOST cases by web developers simply setting the height and width on image tags so that the space is accounted for before they load. Anyone saying they can't do this for some reason is lazy, stupid., or using some framework/tool that is both. End of story.
I thought that that was better sounding than lab rats.
In the old days you'd avoid this by setting the height of the image/container before it loaded so the browser could reserve space for it while rendering the page.
These days we have more dynamic content loaded with AJAX with variable AR, CSS layouts that have different height images/containers depending on the device width/AR that could change when you rotate your device, not to mention content loaded from second party sources.
We also have faster (client) computers compared to servers so it makes more sense to do the logic on the client-side...
Remember when you used to layout a page so that the images had the width and height set in the IMG tag and everything had a fixed size to avoid *exactly* this problem? Whatever happened to that?
Fuck Google.
Burn the motherfucker down.
Recently I've seen ads from home Depot where the ad is waiting for keyboard input. This causes the page to jump to the ad once the page is done loading.
Super annoying. That shit made me buy a new phone that could be rooted so that i can install adaway.
I rarely notice this on Desktop (probably due to ad blocking), but man, I sure could use this on Mobile.
On Linux.
I am on Chrome 57 and I still the jumps on Slashdot whenever the IBM ad loads. I can see why Google would be concerned. I blacklisted a lot of the ad sites just because of what they did to the screen. I am sure a lot of others did the same. If people blacklist ads, this hits Google's bottom line directly.
Any guest worker system is indistinguishable from indentured servitude.
You have to use chrome, I'll be right thanks.
Maybe now I can research material on imagefap unabated
Hosts files: NoScript has to parse tags to block ads (here is how ads really work (downloading scripts you run to render them on web pages) https://news.ycombinator.com/item?id=10221859/ & hosts does it before NoScript even begins to work & in 1 step blocking them as part of the IP stack itself operating in FAR faster kernelmode - NoScript by comparison works in slower usermode & has to parse page tags (far more expensive & complex process in steps etc.)
APK
P.S.=> For the BEST hosts file builder bar-none APK Hosts File Engine 9.0++ SR-7 32/64-bit https://www.google.com/search?hl=en&source=hp&biw=&bih=&q=%22APK+Hosts+File+Engine%22+and+%22start64%22&btnG=Google+Search&gbv=1/ ... apk
This jumping is because of how Google uses "first render" timing to affect pagerank. They forced developers to use stupid workarounds, and now they are solving the problem caused by the stupid workaround.
Your ad here. Ask me how!
that cause the jumpiness. hell, adblock is telling me it blocked 34 ads right now.
They've had the width and height attributes on HTML tags since the 90s.
uBlock Origin.
I stopped using Adblock+ long ago, because it makes all my web browsers consume more RAM, than when running without it.
TechCrunch is devolving into blog spam. They didn't do anything except reword the Google blog.
Lel mismod
This was solved a long time ago with Noscript. Pages load fast and don't jump, not to mention the security benefits.
The XDA website is the worst at this. Their mobile site is incredibly slow.
Why don't web pages just preallocate the space that will later be filled with content? Seems like this problem never should happen if that were done from the beginning.
Why not render webpages always internally and display them only after rendering is done each time?
Both when a page visited for the first time and each time it auto/manual refreshed.
(If refreshed, the webpage would be replaced as a whole when the updated webpage is rendered ready.)
This would also solve auto-refresh annoyances.
IE user here. I want this, please, please, please! Nothing is more annoying than the bloody page jumps caused by the bloody ad networks and their bloody craptastic delivery systems.
No cheap shots about IE. Or AdBlock, or uBlock, or whatnot. Yeah, you know, I can solve the problem by unplugging from the internet too, you know? Gee, thanks for the tips, so helpful. The fact that all that is necessary is part of the problem, endless workarounds aren't really much of a solution.
Yay! Another old Opera 'feature' they finally copied!