Page navigation triggers a chain of events that lead to the
console being cleared. If the stars are perfectly aligned,
the clear is triggered after |window.location.href| is executed
but before waitForMessages() looks at the existing messages
in the console. This causes the input line to be lost and
the test times out waiting for it.
These changes make the test to wait for the first clear to happen
before continuing the test.
MozReview-Commit-ID: LWuR8wxc5Lh
--HG--
extra : transplant_source : %9C%AE%A1b%FB%89%23o%CB%C6%3Ah%E1%27F%AD%FA%22%9A%EC
Devtools autocomplete popups are hosted in a different document from the input
being autocompleted. To allow accessibility tools such as screen readers to still
make sense of this widget, a clone of the suggestion list is now inserted in the same
document as the input, and the aria-activedescendant attribute is updated on the input
accordingly.
MozReview-Commit-ID: 8rFjF6nvEyU
--HG--
extra : rebase_source : 04a4574aee30206c3ac5dbeadcebaea89f0888c3
The removes the legacy path for non-e10s that avoids the messageManager. We now
use the messageManager for all cases, both e10s off and on.
Unsurprisingly, this revealed a variety of race conditions in various tests, so
they've been cleaned up as well.
MozReview-Commit-ID: EXEWehphLIY
Most test modifications deal with listening to the proper events.
As mentioned in the parent commit, the keyboard navigation for the
inspector-search changed a bit with this change, so the related test
case is using a slightly different scenario.
MozReview-Commit-ID: BgSa69bSSFB
--HG--
extra : rebase_source : a1b565f6b54f2c8e3d641794aaa6aa43a2c75134
String.prototype.contains was removed from Firefox 48 completely after
it was renamed to String.prototype.includes. The test includes a
call to .contains() which is triggered whenever random JavaScript
error occurs during the test (hence the intermittency).
MozReview-Commit-ID: 7nbRm94JM7O
--HG--
extra : rebase_source : e969bc1ad46120509deec31066ea63ebbb7de9c9
Add tests for :
- markup display
- add rule
- breadcrumb
- highlighter info bar
- markup search
- webconsole element output
Move webconsole dom output test to head.js as similar things are done
in several tests.
MozReview-Commit-ID: 6gclZhzd7sD
--HG--
extra : transplant_source : %8F%9C%B5%E5%04S%BC%5B%C9%E8QV%8F%E8i%C7%E8%9A%08%A6
Add a displayName property on the NodeActor, which compute from Element.prefix + Element.localName.
The computation is made by a getNodeDisplayName function which can be imported wherever needed.
Edit some tests to ensure we correctly display node names.
MozReview-Commit-ID: 6z0G3ynbMoU
--HG--
extra : transplant_source : %E0%AFM%88D%BC%AD%08%1D%A4%FB%F2%5D%9E%D3%90%DE%94%EC%CD
For simple rules like function spacing, we can auto-fix these across the code
base so they are followed in a consistent way.
To generate this patch, I ran:
./mach eslint devtools --no-ignore --fix
After this, I reverted any changes to third party files that we really do want
to ignore.
MozReview-Commit-ID: 6Q8BApkAW20
