Add base script for de-risking new WebViewCompat APIs

[CrisBarreiro]

Task/Issue URL: https://app.asana.com/1/137249556945/task/1211755269770776?focus=true

Description

Create base script to be used as a test bed. Script contains placeholder so it can be configured as needed from native

Steps to test this PR

n/a

UI changes

n/a

[CrisBarreiro]

• Add native flags #7047
• Configure script based on remote config #7036
• Add base script for de-risking new WebViewCompat APIs #7034 👈 (View in Graphite)
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[CDRussell]

nit, maybe should avoid the use of setTimeout if delay is precisely 0.

I don't know if it matters, but prod scripts will likely either eagerly try do something or use setTimeout with a real delay value; I wouldn't want to miss a problem testing the eager stuff if setTimeout() => {}, 0) was functionally different than just executing immediately.

[CDRussell]

does it matter if native haven't defined a web message listener? e.g., will webViewCompatTestObj not being defined cause an issue?

[CrisBarreiro]

We will have some sort of message listener for all testing scenarios, so it shouldn't be a concern. Also, we don't have a proper way to know if a listener is defined on the native side. In any case, AFAIK, if no listener is defined, we'll see a log in Chrome console, but otherwise, the script would work as normal, with messages being, of course, ignored by native

[CrisBarreiro]

Merge activity

• Nov 4, 11:09 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Nov 4, 11:10 AM UTC: @CrisBarreiro merged this pull request with Graphite.