@justpi: Thanks a lot for your CSS code. Mysterious as it looks to me, it works!
@designsimply: Thanks for your attention from the WP staff side, I do not really doubt your willingness to help. But it's clear that in this case, the help I got from justpi was quicker and more to the point.
Now that I seem to have the ear of the WP staff, may I explain myself a little? For I really do not consider myself one of them conservatives who by principle want to keep everything as it is, and will always oppose any change. If that were the case, I would still be working with Windows 98...
My problem is that when WP pushes this infinite scrolling thing onto its entire user base (without asking, without offering a clear no-thank-you alternative) you seem to do so without considering all the obvious disadvantages of this new fad. Before introducing it, did you ever systematically weigh, from a site visitor perspective, the pros of infinite scrolling against the cons of infinite scrolling? I suspect you didn't. I think you just got carried away by your desire to go along with the latest trend.
To name just one of the many problems in this particular case: infinite scrolling may be suited for the visitor who just wants to quickly skim a few of the latest posts on a phone, but it's totally unsuited for a visitor who really wants to go through a blog site in a more serious way. In that case, it's user-unfriendly, especially when it comes to navigation. For when this visitor keeps adding more and more posts (long posts, who knows) to this "infinite" page, the browser scroll bar will shrink to the point of becoming unusable. The visitor will also lose his orientation: if he wants to go back to a just-read post that was halfway down the page, he'll find that in the meantime the page has expanded so that post is now no longer halfway - but where is it now? This user will now have to scroll-search across the page in the hope to come across it again somewhere... This visitor will also lose his orientation in another way, because when an archive is neatly compartimentalized in different pages of roughly the same size, according to known "ergonomic psychology" this forms a kind of orientation raster. Wandering through archive pages 1-2-3-4-5 unconsciously you'll keep better tabs on where in the whole data mass you are, and you can use your browser's Back/Forward buttons to quickly jump back and forward again through the entire archive, jumping (and this is important) with fixed intermediate steps. Infinite scrolling makes this impossible.
I really wonder if WP, when falling for this fad, did seriously consider all the pros against all the cons. Or did WP simply assume that the function of a blog page is the same as that of a Google search page, where the user will scroll down only (rarely back up) and where the user will stop scrolling down once he's found what he's looking for? Thinking that a blog page should work just like a search engine page, would be a grotesque functional misunderstanding...
So designsimply, would you please, if you can, give me the list of pros and cons of infinite scrolling that WP used as a basis for the decision to introduce it? I'm looking forward to your background info!
Thanks to all, Henk