<thead> not printing on every page in Chrome
See original GitHub issue<thead>
doesn’t print on every page when Bootstrap is loaded. See the test case.
Actual:
Expected:
Operating System: Windows 10 Pro 10.0.17134 Browser: Chrome 72.0.3626.109
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Why thead content is not repeating in each and every print ...
It's working fine in the normal mode but when I rotate my th then it is visible in the first print page but...
Read more >17205 – THEAD & TFOOT should be printed on every page
Yes, the specification says "may be" printed on every page, rather than "shall be" or "must be". This goes beyond consistency with other ......
Read more >thead not printing on every page in chrome when bootstrap css ...
When you the bootstrap stylesheet link in head the table will print the thead content on each printed page as intended. When bootstarp...
Read more >962435 - Table with thead and tfoot incorrect layout ... - Monorail
3729.157 using Ubuntu 14.04. As we have observed that the print page with body in first page and foot in second page from...
Read more >Print Preview broken in last update - Google Support
The one-page document is split across 7 to 8 pages with one element on each page. Problem did not occur in Chrome for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Turns out this code from your test case is invalid HTML, and somehow kills the table header:
Error:
There are a number of
<thead>
bugs outstanding in Chrome, but you are correct that this particular one was resolved (I confused Verified and Confirmed as a bug status).Chromium bug #937227 filed, unsure if this needs to be fixed but we’ll at least see what the developers have to say.
@wouldBeNerd no worries, that’s what we’re here for.