Open Bug 1592920 Opened 1 year ago Updated 3 months ago

test_autofill_from_bfcache.html fails with fission enabled: First document should have been persisted in bfcache

Categories

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

defect

Tracking

()

Fission Milestone M7

People

(Reporter: enndeakin, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [passwords:tech-debt])

+++ This bug was initially created as a clone of Bug #1582113 +++

The test:

  1. The pageHideEvent.persisted is false instead of true

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?

Blocks Fission mochitests milestone (M4.1)

Fission Milestone: ? → M4.1

Bug 1580241 didn't actually fix this issue so this still depends on a DOM fix… I'll move it to the DOM component to reflect the actual owner.

Component: Password Manager → DOM: Navigation
Product: Toolkit → Core
Whiteboard: [passwords:tech-debt]
Summary: test_autofill_from_bfcache.html fails with fission enabled → test_autofill_from_bfcache.html fails with fission enabled: First document should have been persisted in bfcache
Flags: needinfo?(afarre)

This test bug doesn't need to block Fission M4.1 because bfcache is not enabled in Fission.

bfcache doesn't need to block Fission Nightly. It might not even need to block shipping Fission MVP, unless perf is really bad. Tentatively tracking for M7 Beta so we will remember to revisit bfcache before riding the trains.

Fission Milestone: M4.1 → M7
Flags: needinfo?(afarre)
You need to log in before you can comment on or make changes to this bug.