Closed Bug 1526406 Opened 7 months ago Closed 6 months ago

Lazily create JS Actors when observer notifications fire in content

Categories

(Core :: DOM: Content Processes, enhancement)

enhancement
Not set

Tracking

()

RESOLVED FIXED
mozilla67
Fission Milestone M2
Tracking Status
firefox67 --- fixed

People

(Reporter: jdai, Assigned: jdai)

References

Details

Attachments

(2 files, 1 obsolete file)

This is a follow-up to the initial JS Actor APIs which will initially only support creation upon calls to getActor.

This will add additional options to WindowActorSidedOptions:

dictionary WindowActorSidedOptions {
  // ...

  // Array of observer topics which should trigger actor creation.
  //
  // Once an actor has been created, it will automatically be registered 
  // as an observer for these topics for the duration of its lifetime. 
  // When the actor is destroyed, it will automatically be unregistered.
  //
  // WARNING: Observer notifications are global, and can cause creation
  // of unnecessary actors! Filtering of messages must be done on a 
  // per-actor basis.
  sequence<DOMString> observers;
};
Fission Milestone: --- → M1
Fission Milestone: M1 → M2

Depends on D21365

Attachment #9047706 - Attachment is obsolete: true
Attachment #9047049 - Attachment description: Bug 1526406 - Part1: Add support for observers to JS Window Actor Protocols. → Bug 1526406 - Part 1: Add support for observers to JS Window Actor Protocols.
Attachment #9047050 - Attachment description: Bug 1526406 - Part2: Add tests for observers on JS Window Actor Protocols. → Bug 1526406 - Part 2: Add tests for observers on JS Window Actor Protocols.
Pushed by jdai@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4cb69524998c
Part 1: Add support for observers to JS Window Actor Protocols. r=nika
https://hg.mozilla.org/integration/autoland/rev/3ff839ce98f5
Part 2: Add tests for observers on JS Window Actor Protocols. r=nika
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.