1623466 - Cannot screenshot some websites [e.g. Tantek.com homepage]

Status: REOPENED

(Firefox :: Screenshots, defect, P4)

Description

[lewiscowles]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36

Steps to reproduce:

Visit Tantek.com, click elipsis, screenshot, full-page.

Actual results:

Nothing happens. No errors, no messages. Nada

Expected results:

Either take screenshot or give me an error code / reason why; in a way that:

I understand what I've done
I understand what Tantek has done
I understand what has gone wrong

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:ianbicking, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 3

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 4

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 5

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 6

[Firefox Bug Husbandry Bot]

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.

Comment 7

[Emma Malysz]

Thanks for reporting, :lewiscowles.

Going to move this to webcompat and cc tantek

Comment 8

[lewiscowles]

To confirm in-case anyone needs to know, this is still a bug in Firefox 82.0.2 (64-bit)

Interesting thing I just checked is that the page scrolls without issue, and that it prints to XPS / OXPS

I don't know how the screenshot renderer works, but printing (possibly another renderer) works as does scrolling the whole document.

My guess is that each visible part of the screen can be rasterised, and it is just the screenshot tool which does not.

I Don't know that this helps, but from a crude and broad set of thoughts it suggests the page could (abstractly) be saved in a raster format in full.

Comment 9

[Karl Dubost💡 :karlcow]

I don't think this is a bug for Tantek to solve.
It seems that the screenshot service fails for some websites with a specific scenario.
So webcompat Product is not the right place for this.

Comment 10

[Karl Dubost💡 :karlcow]

In the Browser Toolbox I get.

1604542630643	[e-mail]	WARN	Loading extension '[e-mail]': Reading manifest: Invalid extension permission: mozillaAddons
1604542630643	[e-mail]	WARN	Loading extension '[e-mail]': Reading manifest: Invalid extension permission: telemetry
1604542630644	[e-mail]	WARN	Loading extension '[e-mail]': Reading manifest: Invalid extension permission: resource://pdf.js/
1604542630644	[e-mail]	WARN	Loading extension '[e-mail]': Reading manifest: Invalid extension permission: about:reader*
1604542630671	[e-mail]	WARN	Loading extension '[e-mail]': Reading manifest: Invalid extension permission: mozillaAddons
1604542630671	[e-mail]	WARN	Loading extension '[e-mail]': Reading manifest: Invalid extension permission: telemetry
1604542630671	[e-mail]	WARN	Loading extension '[e-mail]': Reading manifest: Invalid extension permission: resource://pdf.js/
1604542630671	[e-mail]	WARN	Loading extension '[e-mail]': Reading manifest: Invalid extension permission: about:reader*
[Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"  nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 684"  data: no] L10nRegistry.jsm:684:19
[Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"  nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 684"  data: no] L10nRegistry.jsm:684:19
1604542633866	Toolkit.Telemetry	WARN	TelemetryStorage::_scanArchive - have seen this id before: dbf00568-bbf0-2045-bb2b-182168c4d9d6, overwrite: false
[Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"  nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 684"  data: no] L10nRegistry.jsm:684:19
Key key_application of menuitem Application could not be found menu.js:292

​

Comment 11

[Dennis Schubert [:denschub]]

(In reply to Karl Dubost💡 :karlcow from comment #9)

I don't think this is a bug for Tantek to solve.

Well.

The screenshots UI is working by injecting an iframe pointing to a moz-extension:// URL into the site. The screenshots webextension works fine, but in Tantek's CSS, there's a

iframe:not(.auto-link):not(.auto-embed):not(.twitter-tweet):not(.twitter-share-button):not(.auto-responses):not([srcdoc]) {
    display: none;
    visibility: hidden;
    margin-left: -10000px;
}

so the screenshots iFrame(s) are invisible.

That's probably something that can be worked around by making the screenshot-iframe-rules !important, though.

Comment 12

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:emalysz, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 14

[Sam Foster [:sfoster] (he/him)]

This is fixed in the new implementation, so I'm blocking on bug 1789727. As soon as we flip that pref and make the new stuff the default, this and its dupes can be considered fixed.

Comment 15

[lewiscowles]

@sfoster this is indeed fixed. Tested on Firefox on OSX on Apple Silicon

https://bugzilla.mozilla.org/show_bug.cgi?id=1860831#:~:text=Thanks%20for%20filing,about%3Aconfig.
is there a way you can link to the patch that fixed it. I'm terribly curious about such things.

Thank You!

Comment 16

[Sam Foster [:sfoster] (he/him)]

This problem still reproduces on various websites using the web extension implementation of Screenshots. That is what we ship by default - even in Nightly. Until the non-extension version becomes the default - which will entail a patch to flip the screenshots.browser.component.enabled pref to true - we have to consider this an open bug.

The extension needs to inject a <iframe> into the content document to host the overlay UI. This is the root cause of a number limitations and bugs. In the new implementation, we are able to use the same anonymous content technique used by the devtools' highlighters - which can't be reached or styled by the content.