getBoundingClientRect() wrong when printing |
|||||||||
Issue descriptionChrome Version: 56.0.2924.87 (Official Build) (64-bit) OS: Mac OS X 10.12.3 What steps will reproduce the problem? (1) Open the attached HTML. Use a browser window size different from print size. (2) View the JavaScript console output. Observe the logged width and height values. (3) Open print preview (cmd-P on Mac) and dismiss. Observe the logged width and height values during print preview are the same as before, but should be different. Observe also that the print preview showed the SVG elements were resized correctly for layout. What is the expected result? getBoundingClientRect() should return the width and height of the element in print layout. What happens instead? getBoundingClientRect() returns the width and height of the element in the original client layout. Please use labels and text to provide additional information. This bug prevents redrawing SVG charts (e.g., D3) so that they print correctly, unless the browser window happens to be at approximately the same size as the printed page. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Mar 1 2017
,
Mar 5 2017
,
Aug 16 2017
,
Aug 16 2017
Based on the report for http://crbug.com/753706, this seems like a fairly important issue. Raising priority and marking as blocking.
,
Jan 7 2018
I faced the same issue. Two remarks: SVG is unrelated to the issue. If we replace <svg> to <div> in the above example, the behavior would be the same. You also can test the incorrect resize behavior by switching portrait/album paper orientation, choose other paper size or custom fields in Google Chrome Preview. I also found a possible workaround: we can use an `event.matches` field in the `matchMedia` event handler to calculate only valid element sizes when necessary. I added this workaround to the latest `test-print.html`. Thanks, anomaly@chromium.org for building good test example.
,
Jan 10 2018
,
Jan 11
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 12
From the printing side, we have no idea how getBoundingClientRect() works. So it's up to Blink folks to figure this one out.
,
Jan 14
,
Jan 17
(6 days ago)
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by anomaly@chromium.org
, Mar 1 2017Hmm, the plot thickens. In the original repro, I attached to the 'resize' event. In this update, I also used matchMedia('print'). When opening and dismissing print preview, this fires twice (!) (once before resize, once after), and the first one has the correct width and height for printing, but the second reverts to the original values. This will be enough for me to implement a temporary Chrome-specific work around, but there appears to be something(s) broken here.2.0 KB
2.0 KB View Download