Without this, server side target were breaking stack record in the memory panel.
We have to ensure toggling stack record ON before the page starts loading.
Differential Revision: https://phabricator.services.mozilla.com/D124823
The memory actor is a target scoped one and they are all destroyed
when the toolbox closes. So memory actor's destroy method is called.
It then calls bridge's destroy, which also detach the actor if it was
attached.
Differential Revision: https://phabricator.services.mozilla.com/D39710
The memory actor is a target scoped one and they are all destroyed
when the toolbox closes. So memory actor's destroy method is called.
It then calls bridge's destroy, which also detach the actor if it was
attached.
Differential Revision: https://phabricator.services.mozilla.com/D39710
"async" methods defined in scripts loaded via a <script> tag seem
to indirectly use the document's Promise, which is not usable after
the DOM of the document has been destroyed.
This is an issue if we invoke this code during the destroy of the
toolbox.
MozReview-Commit-ID: C8juQqJlVDN
This patch was autogenerated by my decomponents.py
It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.
It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <
Mark Banner