WebExtension reload command is still broken with target switching.
Enabling server targets would break this on all reloads.
So prevent enabling server targets until this is fixed.
Differential Revision: https://phabricator.services.mozilla.com/D120982
This patch adds a `reloadViewport` helper that listen for both the viewport
`load` event and for the next dom-complete DOM event so the page is fully loaded.
This makes the test to pass when server side target switching is enabled.
Depends on D120979
Differential Revision: https://phabricator.services.mozilla.com/D121058
We used to handle navigation with a subtle and complex combination of target-available + dom-loading.
Just because we were missing will-navigate event in some cases.
But will-navigate is now reliable and is fired in all types of navigations.
Differential Revision: https://phabricator.services.mozilla.com/D120961
Accessing TargetMixin.localTab during destroy is risky as it may throw.
Reading TabDescriptor.localTab is safer as it will never throw.
This test was failing intermittently on debug builds.
Differential Revision: https://phabricator.services.mozilla.com/D121055
The old performance panel behaves quite differently in case of target switching.
It will open a brand new profile for the next test, which confuses these tests.
Differential Revision: https://phabricator.services.mozilla.com/D120990
We need to use documentStoragePrincipal rather than the regular document principal, because it
contains the partitionKey which is used to isolate storage of third-party resources.
Differential Revision: https://phabricator.services.mozilla.com/D120853
This helps enabling server targets only for local tabs descriptors
and so prevents enabling them for about:debugging toolboxes.
They are always using remote tabs descriptors and do not support target switching yet.
Differential Revision: https://phabricator.services.mozilla.com/D120629
We weren't waiting for the html page to be displayed in the source tree,
leading to failure when trying to set the breakpoint just after opening the toolbox.
Differential Revision: https://phabricator.services.mozilla.com/D120950
Mochitest's default tab is very special.
Its WindowGlobal is stuck on the initial about:blank document.
This document should be transient and we should have another final about:blank document,
even if we expect about:blank document at the end.
This isn't reproducible with a regular firefox run,
but we should investigate this as it may bit us in some other random tests.
Differential Revision: https://phabricator.services.mozilla.com/D120949
target actor's will-navigate and navigate is no longer fired with server targets.
These two tests are still asserting them, so disable server target in these two tests.
We should probably remove them once we drop the server target preference (bug 1721852).
Differential Revision: https://phabricator.services.mozilla.com/D120947
This might not be critical for FF90 debugging, as it will be replaced by FF91 soon.
However in the long run, this issue could happen again so having a fix would be nice.
Differential Revision: https://phabricator.services.mozilla.com/D120859
Wait for accessibility front to be available on target switch in the client.
Disable accessibility service on ParentAccessibilityActor destroy.
Differential Revision: https://phabricator.services.mozilla.com/D120827
The test was failing with server side target switching when navigating to the
html document from the xul one.
As the navigation is clearing up the selection, it led to the color picker to
be closed, which was trigerring an RDP call (setRuleText), which would fail
as the navigation would end up closing the connection, and triggering an error
as the RDP call was still pending.
Closing the picker before navigating fixes this issue.
Differential Revision: https://phabricator.services.mozilla.com/D120812
browser_filter-editor-04.js is frequently failing on windows/linux webrender platforms together with browser_flame-graph-01.js on windows webrender ones.
Differential Revision: https://phabricator.services.mozilla.com/D120778
Those tests are relying on a specific event to assume that color scheme simulation has been disabled, but nothing guarantees that we don't capture another unrelated event in the meantime so this is very fragile.
Instead waitFor the correct style to be applied. This is already what we do in most asserts in those tests.
Differential Revision: https://phabricator.services.mozilla.com/D120820
We expose these via CSS system colors, so this way we don't need to
rebuild the preference sheet when the link color is different.
Differential Revision: https://phabricator.services.mozilla.com/D120677
This test was relying the BrowsingContextTargetActor.listWorkers, but this isn't fission compatible.
The target actor will be destroyed in case of top level target.
This starts to be failing with bfcache in parent, and will also fail with server side targets.
We should rather be testing TargetCommand's behavior instead of individual fronts.
The main STR being covered in this test which isn't covered yet is BF Cache navigation.
Differential Revision: https://phabricator.services.mozilla.com/D117164
