Steps to reproduce
visit following page:
then use IE11 print preview and goto page 2 of print output.
there is some padding or margin at top of page which should not be there and is causing approx 3 lines of output to be hidden.
Obviously this could be my CSS but I have tested using Chromium (Iron) and output is not lost.
Also, switching between page 1 and page 2 sometimes (not always) causes the image on page 1 to lose its scaling so that it becomes enlarged to full size and completely screws up print preview.
So something is amiss with the way its working.
I have no doubt that if I completely restructured my web page so that scrolling was handled by <body> that it would probably work OK but I shouldn’t need to do that, especially since chromium handles it fine.
Comments and activity
I would add that its not just that page it happens, it happens on all multi page print output. Just try it in landscape to see that it happens on a single page in portrait which goes to 2 page in landscape.
running on windows 7 home premium
IE11 11.0.9600.18314 ( update version: 11.0.31 ( KB3154070) )
- Microsoft Edge Team
Changed Title from “IE11 Print dialog error” to “IE11/Edge Print dialog error works in Chrome”
Whilst I’m on a role finding bugs I spotted another one.
The two attachments are of the same page using developer tools in IE11 and Chromium ( Iron )
In the IE11 one you will see that under div class="cycle2-desc" that each
tag has a
tag next to it. Those
tags do not exist in the html anywhere and have been added by either the cycle2 jquery code or IE11. The cycle2 jquery code is at first suspect, However, looking at the Chromium attachment you will see that the
tags have no been added and everything looks as it should be.
So there is a bug in IE11 or the Cycle2 Jquery. I suspect IE11 and also suspect its not quite html5 compliant with regard to putting
which it shouldn’t be putting in anyway.
- Microsoft Edge Team
Changed Assigned To to “Brad E.”
Changed Assigned To to “Bogdan B.”
Changed Status to “External”
Thank you for the report. This issues is caused by some known platform gaps (such as size attribute in @page) that we hope to bridge in the future
This issue has been resolved External. This means this issue may require a new feature to be implemented or other work that is more significant than a typical bug. You may be able to find more information on this issue by searching for related features on status.microsoftedge.com and uservoice.microsoftedge.com.