Closed Bug 1578977 Opened 5 years ago Closed 3 years ago

Stop using message manager in Accessibility actor

Categories

(DevTools :: Framework, task, P3)

Product:
DevTools
Component:
Framework
Type:
task

Tracking

(Fission Milestone:Future)

Status:
RESOLVED FIXED
Project Flags:
Fission Milestone Future

People

(Reporter: jdescottes, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

When fission.autostart is enabled the message manager will not be available when debugging frames. The accessibility actor is directly using the message manager to exchange messages between its content and its parent actors.

Instead of directly using the message manager, we should use APIs provided by DevTools (maybe on debugger-server-connection?) that would transparently use the message manager or js-window-actors.

https://searchfox.org/mozilla-central/search?q=sendAsyncMessage&case=false&regexp=false&path=accessibility

Whiteboard: dt-fission → dt-fission-reserve

Tracking Fission DevTools bugs for Fission Nightly (M6)

Fission Milestone: --- → M6

dt-fission-reserve bugs do not need to block Fission Nightly (M6).

Fission Milestone: M6 → ---

Tracking dt-fission-reserve bugs for Fission MVP until we know whether they really need to block Fission or not.

Fission Milestone: --- → MVP

Moving old "dt-fission-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.

Fission Milestone: MVP → Future
Whiteboard: dt-fission-reserve → dt-fission-future

The accessibility actor now longer use the message manager API.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.