Firefox

Discussed in microsoft/playwright#11891

There are placed in our unit tests where Mockito mocks are used and this is causing intermittent test fails.

Saw this issue and fixed two cases on mozilla-mobile/fenix#24620, today I saw [another occurrence](https://firefoxci.taskcluster-artifacts.net/OmWdljybRhGtBDdPjfFisQ/0/public/reports/test/testDebugUnitTest/classes/org.mozilla.fenix.wifi.WifiConnectionMonitorTest.h

Description:

Provide option to keep some segment and provide a submit button below each segment as I don't want to upload the first segment. As I want the first segment but not sure about the consensus and correctness about the first segment.

Relevant spec sections:

https://drafts.csswg.org/selectors-4/#the-dir-pseudo
https://html.spec.whatwg.org/multipage/semantics-other.html#selector-ltr

The interesting cases to test are from the definition of "directionality" in HTML:
https://html.spec.whatwg.org/multipage/dom.html#the-directionality

• element with dir="ltr" matches :dir(ltr) (#26159)
• root element without `

Add :tabmove # to move the current tab after the previous focused tab (to which <C-6> would switch)
Also may be :tabmove #+n, :tabmove #-n to move to the nth position before/after the previous focused tab

Currently the functionality can be replicated by defining this command:
`command tabmoveAfterlast js -d€ (async function(){const sorted = (await tri.browserBg.tabs.query({ currentW