Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6104767
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T13:52:46+00:00 2026-05-23T13:52:46+00:00

having trouble deciding whether or not it makes sense to put paging information about

  • 0

having trouble deciding whether or not it makes sense to put paging information about a stats table in a <tfoot> element of the table.

information like “Page 1 of 13” and links to “next” & “prev,” etc.

w3c <table> reference & examples don’t do <tfoot> justice, IMO.

so, doing something like:

<table>
<caption>Stats Table!</caption>
<thead>
<tr>
    <th>1</th>
    <th>2</th>
    <th>3</th>
</tr>
</thead>

<tfoot>
    <tr>
        <td colspan="3">
            <a href="">prev pg</a>  <a href="">next pg</a>
        </td>
    </tr>
</tfoot>

<tbody>
    <tr>
        <td>a</td>
        <td>b</td>
        <td>c</td>
    </tr>
    <tr>
        <td>x</td>
        <td>y</td>
        <td>z</td>
    </tr>
</tbody>

with some minor styling looks like this (click for example on jsfiddle)

does this seem to fit into proper semantics of html tables? any references as to why or why not?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T13:52:46+00:00Added an answer on May 23, 2026 at 1:52 pm

    I would say yes, that would be acceptable.

    Traditionally, the <tfoot> is usually used to duplicate header information when a table must be broken across boundaries (think printed pages and things of that nature). It also can be used as a static footer when the <tbody> elements are rendered in a scrolling panel. I believe that is close enough to what you’re trying to do.

    As a side note, I’m glad to see you’ve placed the <tfoot> before the <tbody>. I can’t begin to count how many times I see people put it at the bottom.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm having trouble deciding whether not this code should compile or if just both
I'm having trouble deciding if I want a project of mine to be web-based
I'm learning MVC and am having trouble deciding when I should create a new
I am having trouble deciding if a controller action, which is called by AJAX,
I'm having trouble deciding between the two. They both seem like great plugins but
I'm having trouble deciding on a way to model this type of relationship... All
I am having trouble deciding between two possible design choices. I have a web
I'm brand new to the MVC coding style and i'm having trouble deciding if
I'm having some trouble deciding which approach I should take. I want to allow
I'm having some trouble deciding how two classes should interact and the problem I'm

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.