Closed Bug 1586108 Opened 1 year ago Closed 1 year ago

[Fission][MSU capstone] convert UITour / UITourChild.jsm to be fission-compatible

Categories

(Firefox :: Tours, task, P2)

task

Tracking

()

RESOLVED FIXED
Firefox 72
Fission Milestone M6
Tracking Status
firefox72 --- fixed

People

(Reporter: Gijs, Assigned: staatsty)

References

Details

Attachments

(1 file)

UI Tour is the mechanism we use to highlight and/or show parts of the browser based on interactions on a small list of allowed webpages. We use this e.g. for new users and/or upgrading users, to highlight new features or help them to understand where to find things.

The main chunk of code for this is in UITour.jsm; a much smaller set of code lives in UITourChild.jsm , registered from https://searchfox.org/mozilla-central/rev/01d1011ca4a460f751da030d455d35c267c3e210/browser/components/BrowserGlue.jsm#337-345 .

This bug is about converting this to be fission-compatible, using JSWindowActorChild.

Type: defect → task
Priority: -- → P2

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: --- → ?
Fission Milestone: ? → M5

M6 because UITour doesn't block dogfooding (M5).

Fission Milestone: M5 → M6
Attachment #9100674 - Attachment description: Bug 1586108 - Porting UITOur to be fisson compatible → Bug 1586108 - Porting UITour to be fisson compatible
Attachment #9100674 - Attachment description: Bug 1586108 - Porting UITour to be fisson compatible → Bug 1586108 - Porting UITour to be fission compatible
Pushed by mozilla@noorenberghe.ca:
https://hg.mozilla.org/integration/autoland/rev/753738237bab
Porting UITour to be fission compatible r=Gijs,MattN
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
You need to log in before you can comment on or make changes to this bug.