Set importantForAccessibility to yes on WebView

[ggtlvkma356]

The WebView is marked as NAF in the UI hierarchy by UiAutomator. The likely reason is because importantForAccessibility defaults to auto, and because the pdf is loaded dynamically, the framework decides to set it to no.

UiAutomator cannot reliably select the WebView by resource ID because of this. Currently the workaround is selecting using class name instead, but even without that problem, it is probably better to set it to yes anyway.

[ggtlvkma356]

Update: This is actually a misinterpretation of how UiAutomator works under the hood. importantForAccessibility is not the culprit in this case, because from the hierarchy dump, webview node did exist (with NAF=true), which means if importance had resolved to no, the node would not be there at all. Also, it doesn't actually matter in this case, because UiDevice.getUiAutomation() sets FLAG_INCLUDE_NOT_IMPORTANT_VIEWS on the accessibility service by default, and according to official documentation:

If this flag is set the system will regard views that are not important for accessibility in addition to the ones that are important for accessibility.

NAF is a label only applied by AccessibilityNodeInfoDumper for visualization. For actual execution, ByMatcher.findMatch() in findObject(BySelector) walks the node trees matching only against BySelector and do not filter bt NAF.

The original problem with selecting elements using resId is likely caused by WebView lazily initializing Accessibility, and using class name is the right workaround.