1671413 - The page's iframe doesn't reload while reloading page with Fission enabled

Status: RESOLVED WORKSFORME

(Core :: DOM: Navigation, defect)

Description

[Edgar Chen [:edgar]]

Build id: 20201015094006
STR:

1. enable Fission
2. Load https://codepen.io/edgarchen-the-decoder/full/OJXMERY
3. Click the reload button in toolbar.

Comment 1

[Neha Kochar [:neha]]

Edgar, what's expected which isn't happening. I tried this but it looks the same before and after reload.
If you see an issue, can you post a video so we can see before and after in your reproduction? And could you also specify your platform?

Comment 2

[Edgar Chen [:edgar]]

Attachment: Screen Recording 2020-10-15 at 23.31.50.mov

I also try couple of things,

1. Disable all add-on: still reproducible
2. Try non-Fission window: still reproducible
3. Disable Fission from Nightly Experiments and restart browser: NOT reproducible

Comment 3

[Edgar Chen [:edgar]]

(In reply to Neha Kochar [:neha] from comment #1)

And could you also specify your platform?

MacBook Pro, macOS 10.15.6

Comment 4

[Edgar Chen [:edgar]]

Could not reproduce on new profile.

Comment 5

[Neha Kochar [:neha]]

Thanks for the recording. That's not what I see on may Macbook. I see the same after reload.
When you couldn't reproduce after disabling Fission and restarting, did you try to enable Fission and restart Firefox, and then reproduce again? i.e. is it consistently reproducing for you?
Do you see anything interesting in the browser console or network monitor when this happens?

Comment 6

[Edgar Chen [:edgar]]

Yes, it is consistently reproducing for me.
Compare with normal case, I saw

An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing.

in web console when this happens.

Comment 7

[Edgar Chen [:edgar]]

I tried other page that also contains an OOP iframe, e.g. https://developer.mozilla.org/en-US/docs/Web/API/Element/setPointerCapture or https://www.twitch.tv/ etc, I did not see the same issue and I didn't experience this on other sites so far, either.

Comment 8

[Chris Peterson [:cpeterson]]

Edgar, can you reproduce the problem in a new profile?

Can you share your about:support info? Maybe you have some prefs that you've modified but forgotten. :)

Comment 9

[Edgar Chen [:edgar]]

Attachment: about:support

about_support

Comment 10

[Edgar Chen [:edgar]]

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

Edgar, can you reproduce the problem in a new profile?

No, I could not reproduce the problem in a new profile.

Comment 11

[Edgar Chen [:edgar]]

(In reply to Edgar Chen [:edgar] from comment #2)

Created attachment 9181872 [details]

I also try a couple of things,

1. Disable all add-on: still reproducible
2. Try non-Fission window: still reproducible
3. Disable Fission from Nightly Experiments and restart browser: NOT reproducible

4. Disable Fission from Nightly Experiments but set fission.sessionHistoryInParent to true, then restart browser: reproducible

So it looks like something related to SHIP.

Comment 12

[Neha Kochar [:neha]]

fission.sessionHistoryInParent is not expected to work without fission.autostart for now.

Comment 13

[Chris Peterson [:cpeterson]]

Peter is reviewing a patch from Olli related to SHIP and iframes (bug 1671962). Perhaps it's related? Let's retest after the fixes for bug 1671962 and Peter's bug 1673702.

Comment 14

[Edgar Chen [:edgar]]

I could not reproduce this anymore on today's nightly, 20201101092255.