inherit
16846
0
Nov 19, 2012 15:20:20 GMT -8
Chris
3,036
December 2003
cddude
|
Post by Chris on Jan 10, 2013 17:11:33 GMT -8
Currently, the page scrolls once onload finishes. Unfortunately, this includes the ads. Meaning, I've started reading the page, scroll down, and it then moves again. This is quite irritating. I don't want it moving once I've moved... especially when, on average, it takes 6.5+ seconds to load a page with ads. (And trust me, it isn't my internet connection that's the issue.)
|
|
#00AF33
Bark Different.
102833
0
1
Feb 12, 2023 16:57:46 GMT -8
RedBassett
I'm a Marxist/Lennonist of the Groucho/John variety.
15,405
April 2007
applecomputer
RedBassett's Mini-Profile
|
Post by RedBassett on Jan 11, 2013 8:12:14 GMT -8
Highly agreed. This has been a major issue for me, again on very good connections.
|
|
inherit
163839
0
May 25, 2017 20:48:34 GMT -8
Maiden
1,020
February 2011
dreamaiden
|
Post by Maiden on Jan 11, 2013 8:20:12 GMT -8
I find this annoying when loading threads but actually quite useful when you've posted and don't want to be put back at the bottom with the reply you've just done. There's usually enough time to click and move on It does make the whole experience a little painful though so I think this feature request is a good idea ^^
|
|
#e61919
2
0
1
Oct 2, 2024 14:45:32 GMT -8
Martyn Dale
$[user.personal_text]
20,088
February 2003
martyn
|
Post by Martyn Dale on Jan 11, 2013 9:27:33 GMT -8
There was a problem ad network which was exasperating this issue which we have had disabled.
That said, we are also planning on making changes to how the jumps work. The intent of waiting until after onload occurred was so images loading in posts, didnt result in the jump being out of place (Since the way they typically work, is to jump as soon as the element loads, meaning as images load, your content could move leaving your screen in the wrong place)
Of course as you have noted, this current system isnt ideal either
|
|
inherit
16846
0
Nov 19, 2012 15:20:20 GMT -8
Chris
3,036
December 2003
cddude
|
Post by Chris on Jan 11, 2013 9:36:25 GMT -8
There was a problem ad network which was exasperating this issue which we have had disabled. That said, we are also planning on making changes to how the jumps work. The intent of waiting until after onload occurred was so images loading in posts, didnt result in the jump being out of place (Since the way they typically work, is to jump as soon as the element loads, meaning as images load, your content could move leaving your screen in the wrong place) Of course as you have noted, this current system isnt ideal either api.jquery.com/load-event/Why not just assign load to #wrapper, which doesn't include ads? From what I just read above, that will solve at least the problem of waiting on ads networks. (All images above the #wrapper should be cached anyways.)
|
|
#e61919
2
0
1
Oct 2, 2024 14:45:32 GMT -8
Martyn Dale
$[user.personal_text]
20,088
February 2003
martyn
|
Post by Martyn Dale on Jan 11, 2013 9:37:37 GMT -8
I was referring to images in peoples posts, such as their signatures, or images they are choosing to display in a post
|
|
inherit
16846
0
Nov 19, 2012 15:20:20 GMT -8
Chris
3,036
December 2003
cddude
|
Post by Chris on Jan 11, 2013 9:50:05 GMT -8
I was referring to images in peoples posts, such as their signatures, or images they are choosing to display in a post Right. And if I read that jquery api page correctly, this waits for the images in the posts to load (since they're inside #wrapper), and then would call the jump method.... again, if I read it correctly.
|
|
#e61919
2
0
1
Oct 2, 2024 14:45:32 GMT -8
Martyn Dale
$[user.personal_text]
20,088
February 2003
martyn
|
Post by Martyn Dale on Jan 11, 2013 9:51:42 GMT -8
Ill throw that to the devs involved. This may already be something they were already considering. I just know the "bug" is on the list haha
|
|