Open Bug 1646562 Opened 3 years ago Updated 2 years ago

Fix GetInProcessParentDocshell usage in nsDocShell::RestoreFromHistory

Categories

(Core :: DOM: Navigation, defect, P3)

defect

Tracking

()

People

(Reporter: kmag, Unassigned)

Details

It's used to suppress event handling when it's suppressed in its parent, though that currently does not work for OOP ancestors/descendants or hierarchies with OOP interstitials either way.

Severity: -- → S3
Priority: -- → P3

Fission Future because this code is only used in bfcache.

Fission Milestone: --- → Future

Olli, can you review and figure out if this will be done as part of BFCache Fission redesign or will we need this on file to fix after the initial implementation is done?

Fission Milestone: Future → M7
Flags: needinfo?(bugs)

This shouldn't be needed at all, but keeping this open for now.

Flags: needinfo?(bugs)
Whiteboard: fission-bfcache

Agree with comment 3. This should only be called for top-level docshells, which can't have an in-process parent under Fission anyway, so it shouldn't matter.

No longer blocks: fission-bfcache
Fission Milestone: M7 → ---

We may end up removing this altogether, so bringing back Fission milestone (although not M7) so that we can close this bug when we do that.

Fission Milestone: --- → M8

This probably doesn't need to block Fission at all. The code is for in-process bfcache, not for parent process bfcache.

No longer blocks: fission-bfcache
Fission Milestone: M8 → ---
Whiteboard: fission-bfcache

This doesn't need to block Fission at all.

No longer blocks: 1642433
Blocks: 1642433
Whiteboard: [fission-]
No longer blocks: 1642433
Whiteboard: [fission-] → [not-a-fission-bug]
No longer blocks: 1642433
Whiteboard: [not-a-fission-bug]
You need to log in before you can comment on or make changes to this bug.