Note that Native content will be deprecated.
Adding a temporary access to nativeContent may be acceptable in these conditions.

I don't think that EG asks CRWWebController for its webview_. But we can add API like StaticHtmlNativeContentContainingText.

My wording was indeed incorrect. What I meant to say was that EG ends up calling CRWWebController's executeJavaScript, which itself uses |webview_|.

Could we modify CRWWebController's executeJavaScript so that if its |webview_| is nil, it tries to execute JS with the nativeController?

>>> Could we modify CRWWebController's executeJavaScript so that if its |webview_| is nil, it tries to execute JS with the nativeController?

This can break many things and given that we want to deprecate NativeContent for the new architecture, I would choose not to risk :)

Where would you imagine adding StaticHtmlNativeContentContainingText?

And what do you think about adding a EG helper that simply searches for a WKWebview the view hierarchy?

>>> Where would you imagine adding StaticHtmlNativeContentContainingText?
I was thinking about chrome_macthers.h/m, which turns out already has StaticHtmlViewContainingText metcher. Does existing method work for you?

>>> And what do you think about adding a EG helper that simply searches for a WKWebview the view hierarchy?
I would be strongly against that :). We spend many months rewriting KIF tests during UIWebView -> WKWebView transitioning, because KIF tests used UIWebView directly. EG tests should not operate on low-level concepts like WKWebView.

jif@ is no longer on the team. Releasing his bugs for triage.

eugenebut@ do you think we can close this?

I think that -[ChromeEarlGrey waitForStaticHTMLViewContainingText] addresses the issue.