[wpt] Ensure compute pressure/generic sensor tests satisfy focus check

Some tests currently assume the testharness browsing context is
initially focused. Opening the BC with WebDriver's "New Window" command
[0] instead of `window.open(...)` broke such tests because the command
doesn't run focusing steps [1].

To fix #50622, ensure the testharness document
starts with focus by sending a click [2] during test setup. A few
`test()`s have been fixed up into `promise_test()`s so that they're
compatible with `promise_setup()`.

The bug doesn't surface with `--product=headless_shell` because headless
shell doesn't seem to have a focusable address bar.

[0]: https://www.w3.org/TR/webdriver/#new-window
[1]: https://html.spec.whatwg.org/multipage/interaction.html#focusing-steps
[2]: https://w3c.github.io/uievents/#event-type-click

Bug: 392539092
Test: run_wpt_tests.py --product=chrome external/wpt/compute-pressure/
Change-Id: I8728ef42733c08cafe555b666c56c4b85d4b0304
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6341204
Reviewed-by: Arnaud Mandy <arnaud.mandy@intel.com>
Commit-Queue: Jonathan Lee <jonathanjlee@google.com>
Cr-Commit-Position: refs/heads/main@{#1430924}

Author: jonathan-j-lee

compute-pressure/compute_pressure_detached_iframe.https.window.js

@@ -8,7 +8,7 @@
 
 'use strict';
 
-test(() => {
+promise_test(async () => {
   const iframe = document.createElement('iframe');
   document.body.appendChild(iframe);
   const frame_window = iframe.contentWindow;

compute-pressure/resources/common.js

@@ -136,6 +136,12 @@ switch (_globalScope) {
     throw new Error(`Invalid variant '${_globalScope}'`);
 }
 
+promise_setup(async () => {
+  // Ensure window's document has focus so that the global under test can
+  // receive data.
+  await test_driver.click(document.documentElement);
+});
+
 const pressure_test =
     _pressureTestHelper.pressure_test.bind(_pressureTestHelper);
 const mark_as_done = _pressureTestHelper.mark_as_done.bind(_pressureTestHelper);

generic-sensor/generic-sensor-tests.js

@@ -36,6 +36,12 @@ function runGenericSensorTests(sensorData, readingData) {
     }, name, properties);
   }
 
+  promise_setup(async () => {
+    // Ensure window's document has focus so that the global under test can
+    // receive data.
+    await test_driver.click(document.documentElement);
+  });
+
   sensor_test(async t => {
     await test_driver.set_permission({name: permissionName}, 'denied');
 
@@ -614,7 +620,7 @@ function runGenericSensorTests(sensorData, readingData) {
  immediately accessible to all sensors.`);
 
   //  Re-enable after https://github.com/w3c/sensors/issues/361 is fixed.
-  //  test(() => {
+  //  promise_test(async () => {
   //     assert_throws_dom("NotSupportedError",
   //         () => { new sensorType({invalid: 1}) });
   //     assert_throws_dom("NotSupportedError",
@@ -626,7 +632,7 @@ function runGenericSensorTests(sensorData, readingData) {
   //  }, `${sensorName}: throw 'NotSupportedError' for an unsupported sensor\
   // option.`);
 
-  test(() => {
+  promise_test(async () => {
     const invalidFreqs = ['invalid', NaN, Infinity, -Infinity, {}];
     invalidFreqs.map(freq => {
       assert_throws_js(