org.eclipse.swt.tests.junit.Test_org_eclipse_swt_browser_Browser.test_TabTraversalOutOfBrowser fails intermittently, both on IE and on Edge

[fedejeanne]

The test fails locally and it can fail with both browsers on Windows.

I ran the test using the parameterized version of the test class org.eclipse.swt.tests.junit.Test_org_eclipse_swt_browser_Browser that can be found in #672 (I disabled all other tests in the class to speed up the testing), I swapped the parameters around and also enabled/disabled them, just for fun, and this is what I saw:

Note: [browser flags: 0] means Edge and [browser flags: 524,288] means IE

The only combination that I couldn't get was: First Edge then IE and both failing... but I can't say that one won't fail either.

[HeikoKlare]

Browser tests are still executed with IE, not with Edge, see:

• Browser tests are not executed for Edge browser #671
• Execute browser tests for Edge #671 #672

So the failure occurs with IE. This can also be seen in the used flag browser flags: 524,288. This is the one for IE.
The test has just been introduced via:

• Edge: Set focus after WebView2 initialization of runtime if necessary #1641

[fedejeanne]

@jukzi just for the record, this is a regression in a test and not in productive code. In productive code I tested the snippet provided in #1640 (comment) and it worked, both for IE and for Edge.

[jukzi]

Thanks for clarification. I also put labels regression+test on tests that started to fail.

[sratz]

I think the Display.getDefault().post(event) is really fragile.

I don't think there is any other way to simulate an event that is supposed to originate from within the browser.

Maybe we'd need to remove the test again.