Screenshots on some Washington Post articles includes page elements in wrong location on page
Categories
(Firefox :: Screenshots, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | affected |
People
(Reporter: eddiebrace, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0
Steps to reproduce:
-
Go to a Washingtonpost.com article such as this.
-
Take a screenshot including the headline, top photograph, and any other elements of your choice
-
Compare image to page as rendered by browser
Actual results:
Page banners appear in front of page context despite being located differently on webpage. This seems to be a problem when the screenshot tool requires scrolling down the page to capture the entire desired image.
Expected results:
Cropped image shows portion of page as it appears in browser.
| Reporter | ||
Comment 1•3 years ago
|
||
| Reporter | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Reproduced on latest Nightly 108.0a1 (2022-10-23) under Win 10 64-bit, thus confirming.
Comment 3•3 years ago
|
||
I can reproduce this, but I'm not sure what we need to do to fix it. For any page with position:fixed or position:sticky elements, those elements will move as you scroll the page - for example to expand the box you wish to capture. So a header that you see at the top of the page is actually half way down the document if you've scrolled down. Unless you scroll back up the fixed position elements will get captured as-is, where they overlap the rest of the content.
One relatively quick fix might be to always scrollTo the top of the selected area before actually sending the capture request.
This is one case where not having a preview hurts the user as a preview would make it immediately clear that all is not well.
Description
•