Layout request:Is it possible to change the loading order so that pages with many,many pictures immediately reserve the space for the images, and only once page structure is solid do the download of the image contents?The current method of making an unloaded image show as a one-line, which then POPs up to size only when its image is fetched, makes the image-heavy threads impossible to use before they are fully loaded.And as this can take many seconds, even a minute or two on a slow connection, it makes navigation of image-heavy pages like the spacex construction update pages a bit of a pain.I'd much rather have a stable screen with blank image blocks slowly being filled, than a page that jerks and scrolls each time an image is finally loaded.
Quote from: Pete on 11/27/2019 04:42 pmLayout request:Is it possible to change the loading order so that pages with many,many pictures immediately reserve the space for the images, and only once page structure is solid do the download of the image contents?The current method of making an unloaded image show as a one-line, which then POPs up to size only when its image is fetched, makes the image-heavy threads impossible to use before they are fully loaded.And as this can take many seconds, even a minute or two on a slow connection, it makes navigation of image-heavy pages like the spacex construction update pages a bit of a pain.I'd much rather have a stable screen with blank image blocks slowly being filled, than a page that jerks and scrolls each time an image is finally loaded.I haven't noticed that issue with images that are actually stored on NSF.The issue I see is with embedded tweets, and there's nothing NSF can do about that because NSF doesn't know the size so it can't tell the browser. So the browser can't reserve space because it doesn't know the size until the tweet is actually fetched from Twitter. Any fix would have to be in the browser in the way that it loads embedded content with no size specified.
For tweets, reserve a reasonable amount of space at first, then refine. There isn't too much variability in the vertical size of a twitter card.
Quote from: dglow on 11/29/2019 04:49 pmFor tweets, reserve a reasonable amount of space at first, then refine. There isn't too much variability in the vertical size of a twitter card.That will still cause jitter unless buffer space is left empty.
Quote from: Lar on 12/01/2019 02:22 pmQuote from: dglow on 11/29/2019 04:49 pmFor tweets, reserve a reasonable amount of space at first, then refine. There isn't too much variability in the vertical size of a twitter card.That will still cause jitter unless buffer space is left empty.What do you propose instead? Some refinement jitter seems preferable to the jumpy 'zero-to-everything' behavior we have now.
One minor upgrade ... the embedded tweet thing is great, but it would be helpful if it understood and automatically removed the "?s=xx" suffixes, which catch a lot of people out--- Tony
Quote from: dglow on 12/01/2019 07:26 pmQuote from: Lar on 12/01/2019 02:22 pmQuote from: dglow on 11/29/2019 04:49 pmFor tweets, reserve a reasonable amount of space at first, then refine. There isn't too much variability in the vertical size of a twitter card.That will still cause jitter unless buffer space is left empty.What do you propose instead? Some refinement jitter seems preferable to the jumpy 'zero-to-everything' behavior we have now.it sounds like it'd be an improvement to me, so if it's easy to do I am in favour..... I'm just pointing out that it won't always prevent all jitter. Also I'm not one of the web boffins here.
As we're doing "how about"s...How about a way to hide threads one 'never' wants to see again. It becomes tricky because 'never' is a long time so a proper implementation would require a way to show hidden threads and un-hide selected ones (although I personalty could live without this refinement - gone forever would be just fine). For bonus points make the feature available only to L2 subscribers.For even more points make available to mods (in whatever form Chris finds most useful) a report of the number of people who've hidden each thread (and, perhaps, who they are). Threads with very high numbers being candidates for locking, removal, etc.It's all about raising the signal to noise ratio which, it seems to me, is slowly but surely falling in some nooks of the site. YMMV.
[...]How about a user option to reverse order the posts (most recent first)?Often what I want to read is most recent.
Quote from: Pete on 11/27/2019 04:42 pmLayout request:Is it possible to change the loading order so that pages with many,many pictures immediately reserve the space for the images, and only once page structure is solid do the download of the image contents?The current method of making an unloaded image show as a one-line, which then POPs up to size only when its image is fetched, makes the image-heavy threads impossible to use before they are fully loaded.And as this can take many seconds, even a minute or two on a slow connection, it makes navigation of image-heavy pages like the spacex construction update pages a bit of a pain.I'd much rather have a stable screen with blank image blocks slowly being filled, than a page that jerks and scrolls each time an image is finally loaded.Seconded.
