Open ijdoc opened 11 years ago
@jorgesilva Calling getClassName() on the node will give us the class and let us identify the node type. It is a one line call, so we do not need to keep this issue open.
do we still need this?
@k22mak I believe this is related to what we were discussing today. Please confirm.
This may not be a viable choice when deciding what to do between apps. Many different node types can do the same thing. For example the google search bar on the Nexus 4 uses a different type of view for text input than whatsapp's. Both have the same functionality.
@k22mak the goal would be more to detect categories of views that share properties as supposed to specific view types. In your example, both nodes would be 'assigned' the same functionality from the perspective of the highlighter.
It seems we need to detect the type of highlighted node in order to resolve at least two issues: #160 for browser/webview navigation, and #163 for proper keyboard / HUD swapping. Others may be required later, so we should add code in the Highlighter (i.e., accessibility service) to determine the type of every node and redirect to a corresponding switch access strategy.