Closed
Bug 1360243
Opened 7 years ago
Closed 5 years ago
HTML DOM scrollTop Property unsupported with printing device
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: C.Krueger.B, Unassigned, NeedInfo)
Details
Attachments
(1 file)
773 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20170418123315 Steps to reproduce: I have partially visible contents in <div> tags, which are scrolled to specific locations. (I do so as a preparation step for printing out larger contents with controlled page breaks.) Actual results: The scrolling for the printing device is ignored. It always starts at the top position. Expected results: WYSIWYG: the scrolling of the screen should be taken over when using print media. (Chromium 58.0 shows this IMHO correct behaviour.) How to reproduce: Open the attached file in Firefox and examine the difference between scrolling on screen and printer.
Updated•7 years ago
|
Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
Updated•7 years ago
|
Component: DOM: Core & HTML → Printing: Output
Comment 1•7 years ago
|
||
Hmm, I guess we could try to guess the scrolling position when cloning nodes for printing. But it would be rather a guess only. Printing may affect to the layout quite a bit so whether the position is in right location isn't clear. In practice the right solution is probably to modify the page in beforeprint event listener so that the expected layout can be achieved. (or perhaps some printing specific .css would work too)
Comment 2•7 years ago
|
||
FWIW, on linux using Chrome to print that page is all wrong. I don't see any text.
Comment 4•5 years ago
|
||
2019-03-06
This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.
The request for information has not been answered, and we can't move forward on the bug so we are closing it.
If the defect is still present, please reopen this bug with an updated report.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•