Page break in one table causes headers for all tables on the page to repeat
Reported by
mitch.ga...@gofmx.com,
Oct 3 2016
|
|||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Example URL: https://jsfiddle.net/9ao5v7h5/ Steps to reproduce the problem: 1. Cause a table to break across pages 2. Add a second table after the page-broken one 3. Observe the repeated header of the page-broken table also contains the header of the second table What is the expected behavior? Only the header for the table that's broken across pages is repeated. What went wrong? Headers are repeated for all tables on the page, not just the table that was broken across pages. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 53.0.2785.116 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0
,
Oct 4 2016
,
Oct 4 2016
Please find the attached chrome and Firefox screenshots, as we observed the same behaviour in both the browsers (Chrome-53.0.2785.143, Firefox). Could you please elaborate the expected behaviour for the same to reproduce the issue.
,
Oct 4 2016
,
Oct 4 2016
Sorry, should have indicated that the page breaking behavior occurs when printing. To reproduce, click the "Print" button in the JSFiddle (https://jsfiddle.net/9ao5v7h5/) and then observe the table header on the second page of the output. The expected behavior is demonstrated in the Firefox and IE 11 outputs (see attached), where only the table that's broken across pages repeats its header. Chrome's behavior (see attached) is to repeat the headers of all tables on the page, in the same visual space, even tables that aren't broken across pages.
,
Oct 6 2016
Able to reproduce the issue on windows mac and Linux using Chrome stable (53.0.2785.143),beta (54.0.2840.50) . But this is working fine on Dev(55.0.2873.0) and canary(55.0.2882.0). Seems the issue got fixed on later versions. Worked on reverse bisect and below is the info Manual Bisect: ------------ first Good build:55.0.2862.0 last Bad build:55.0.2861.0 Bisect Tool Info: ---------------- https://chromium.googlesource.com/chromium/src/+log/5dc5867ab6200abb2f02392a16267ecec62d676e..8bf47bb4e1d0ea9599bc443906fc26c3ce86f152 suspect: ------- https://chromium.googlesource.com/chromium/src/+/8bf47bb4e1d0ea9599bc443906fc26c3ce86f152 robhogan@ Please reassign if this is not related to your change.
,
Oct 6 2016
Yup, this is fixed in both unstable branches.
,
Oct 6 2016
Any idea on when this patch will be release to Google Chrome? I am on "Version 53.0.2785.143 m" and still see this issue. We are having a lot of clients complaining about this issue and are having them switch to IE to get around this issue for the time being.
,
Oct 6 2016
,
Oct 7 2016
[Automated comment] Request affecting a post-stable build (M53), manual review required.
,
Oct 7 2016
[Automated comment] Less than 2 weeks to go before stable on M54, manual review required.
,
Oct 7 2016
[Automated comment] Request affecting a post-stable build (M53), manual review required.
,
Oct 7 2016
We don't have any M53 Stable release plan for Chrome Desktop.
,
Oct 7 2016
+ bustamante@ for M54 Merge Review
,
Oct 7 2016
Approving for M54, this is pretty visible when it happens, and the CL looks safe.
,
Oct 10 2016
Looks like Team Chrome has made some progress. When can we expect this fix pushed out in Production? The situation is pretty bad with the prints right now.
,
Oct 10 2016
Thanks for the fix, verified in latest canary- 56.0.2886.0 , works as expected. IMPORTANT: M54 will be promoted to Stable soon! Please make sure to merge the fix before 4:00 PM PT today, Monday- 10/10 if you want to make the fix to STABLE channel.
,
Oct 10 2016
,
Oct 10 2016
Thanks for the merge. Confirming the fix landed in M54 - https://chromium.googlesource.com/chromium/src.git/+/ee7ca0fdc96ab4ba61d0be876c8e779adced302d Updating labels accordingly.
,
Oct 11 2016
@robhogan@chromium.org When will this fix be available in my browser? |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by ligim...@chromium.org
, Oct 3 2016