Closed Bug 1648293 Opened 4 years ago Closed 4 years ago

Screenshots of cross-origin iframes are blank, if fission is enabled

Categories

(Firefox :: Screenshots, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1636508

People

(Reporter: dholbert, Unassigned)

References

()

Details

Attachments

(2 files)

STR:

  1. Set about:config pref fission.autostart to true, and restart Firefox.
  2. Visit https://www.milgard.com/brochure/tuscany
  3. Take a screenshot (using three-dot-menu, "take a screenshot" option)
    (Doesn't matter whether you copy it or download it, but let's say "download" for the purposes of this STR.)
  4. View your screenshot.

ACTUAL RESULTS:
The screenshot is blank.

EXPECTED RESULTS:
The screenshot should show me the content that I screenshotted.

I suspect this has to do with the fact that this page's content is actually being shown via a cross-origin iframe, which fission has trouble with.

  • If I perform the STR in a non-fission window (i.e. skipping step 1 or doing File|New Non-Fission Window), then screenshotting works.
    Also:
  • If I view the iframe contents directly (e.g. by right-clicking the content and choosing "open frame in new tab"), then screenshotting works (produces non-blank content) even in a fission-enabled window.
See Also: → 1568833

I swear there is an existing bug about PDF screenshots not working with Fission, but I can't find it. So we'll track this bug for Fission M6b Nightly.

Severity: -- → S3
Fission Milestone: --- → M6b
Priority: -- → P3

(In reply to Chris Peterson [:cpeterson] from comment #1)

I swear there is an existing bug about PDF screenshots not working with Fission

Just to be clear - in this case, there's no PDF involved. The "brochure" here is a JS-based dynamic slideshow thing, with <img> elements pointing to content like https://secure.viewer.zmags.com/services/resource/pub/30a53826/pg463x600/344/1 , and with dynamically updating CSS transforms to do the slideshow business.

I think this is just broken, in general, for cross-origin iframes (regardless of their content). I'll post a testcase shortly.

Attached file testcase 1

Here's a testcase, which has an iframe hosting some cross-origin content (another bug's testcase).

It should render with two large "abc" strings, one of which may be fuzzy (don't worry about that).

If you try to take a screenshot of the "abc" text in this testcase, with fission enabled, you end up just getting a blank result (presumably because it's a cross-origin iframe)

Attached file testcase 2

Testcase 2 demonstrates that same-origin iframes do screenshot correctly, but their cross-origin descendant iframes do not.

(i.e. when viewing testcase 2, you can successfully screenshot the See if you can take... text in its iframe, as well as the How about this outer page text in the outer document, but you still can't screenshot the abc text in the innermost iframe, presumably because it's cross-origin which interferes with what screenshots is trying to do.)

This is because the screenshot extension still uses drawWindow, we need to migrate to use drawSnapshot.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE

Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.

Fission Milestone: M6b → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: