Julian Descottes
846d751b43
"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
30 lines
736 B
INI
30 lines
736 B
INI
# vim: set filetype=python:
|
|
# This Source Code Form is subject to the terms of the Mozilla Public
|
|
# License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
|
|
|
|
with Files('**'):
|
|
BUG_COMPONENT = ('Firefox', 'Developer Tools: Memory')
|
|
|
|
DIRS += [
|
|
'actions',
|
|
'components',
|
|
'reducers',
|
|
]
|
|
|
|
DevToolsModules(
|
|
'app.js',
|
|
'constants.js',
|
|
'dominator-tree-lazy-children.js',
|
|
'initializer.js',
|
|
'models.js',
|
|
'panel.js',
|
|
'reducers.js',
|
|
'store.js',
|
|
'utils.js',
|
|
)
|
|
|
|
BROWSER_CHROME_MANIFESTS += ['test/browser/browser.ini']
|
|
XPCSHELL_TESTS_MANIFESTS += ['test/unit/xpcshell.ini']
|
|
MOCHITEST_CHROME_MANIFESTS += ['test/chrome/chrome.ini']
|