H. G. Muller wrote on Fri, Oct 13, 2017 08:16 AM UTC:
The Earlier comments link appears only at the bottom, because the value needed for it is determined by the id of the last comment displayed on the page, and it doesn't know what this is until it has displayed a page full of comments.
OK, I see. I noticed that when I accidentally put a piece of text in a table between a </td> and a <td> element (instead of the reverse), it renders that text above the table. This might just be making use of undefined browser properties, however.
JavaScript could solve it, of course: you could just define an empty <div> at the start of the page, and at the end of the page emit a <script> that would fill it with the required <a> element. This would then occur in the client browser, and cause no server load. It would not work when JavaScript is turned off, then. But to make the life of people that do that easier, you could initially fill the <div> element at the top with an <a> that refers to an in-page tag at the bottom. Then at least they have a one-click method to get to the 'Earlier Comments' link.
OK, I see. I noticed that when I accidentally put a piece of text in a table between a </td> and a <td> element (instead of the reverse), it renders that text above the table. This might just be making use of undefined browser properties, however.
JavaScript could solve it, of course: you could just define an empty <div> at the start of the page, and at the end of the page emit a <script> that would fill it with the required <a> element. This would then occur in the client browser, and cause no server load. It would not work when JavaScript is turned off, then. But to make the life of people that do that easier, you could initially fill the <div> element at the top with an <a> that refers to an in-page tag at the bottom. Then at least they have a one-click method to get to the 'Earlier Comments' link.