1924710 - Fire onTargetSelected on startup to pick the visible target

Status: RESOLVED FIXED

(DevTools :: General, enhancement)

Description

[Alexandre Poirot [:ochameau] PTO, back May 4th]

For now, we are using both onTargetAvailable and onTargetSelected to pick the displayed target, notably in the inspector and accessibility panel.
There is some redundancy between these two listeners. The onTargetAvailable consider any top level target as one to select and display.
This also make the top level target special and be always selected by default. In bug 1754452, the default selected target may not be the top one.

Comment 1

[Alexandre Poirot [:ochameau] PTO, back May 4th]

Attachment: Bug 1924710 - [devtools] Call onTargetSelected on initialization and navigation with the current top level target.

This helps:

• factorize some duplicated code between target available and selected,
• selecting a target other than the top level one by default,
• reduce the importance of "top level" target checks,
  which may allow to start frontend without one such target.

Comment 2

[Alexandre Poirot [:ochameau] PTO, back May 4th]

Attachment: Bug 1924710 - [devtools] Wait for Accessibility proxy initialization and not some of its internal.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/18165b1a2c83
[devtools] Call onTargetSelected on initialization and navigation with the current top level target. r=devtools-reviewers,jdescottes
https://hg.mozilla.org/integration/autoland/rev/e4aa32d0fc2b
[devtools] Wait for Accessibility proxy initialization and not some of its internal. r=devtools-reviewers,jdescottes

Comment 4

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/18165b1a2c83
https://hg.mozilla.org/mozilla-central/rev/e4aa32d0fc2b