Open Bug 1588091 Opened 3 months ago Updated Last month

test_autocomplete_https_downgrade.html fails with fission enabled


(Toolkit :: Password Manager, defect, P2)




Fission Milestone M4.1


(Reporter: MattN, Unassigned)



The tests run but synthesizeKey is sending the event to the wrong child frame. Could be a focus issue. It works if I focus then press the expected keys manually.

Summary: test_autocomplete_https_upgrade.html fails with fission enabled → test_autocomplete_https_downgrade.html fails with fission enabled

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:


Fission Milestone: --- → ?

Blocks Fission mochitests milestone (M4.1)

Fission Milestone: ? → M4.1

The best solution is to have the test harness support loading tests over http on port 80, changing scheme = http to do that and have scheme = default use mochi.test:8888 like we do now.

You need to log in before you can comment on or make changes to this bug.