Roku automation framework - getFocusedElement does not return correct focused element
The webdriver doesn’t seem to be able to interpret what the focused element is correctly in the majority of places within the app. Instead of returning the focused element, getFocusedElement returns a key on the virtual keyboard that it seems to think is focused instead. The keyboard is not on screen or visible.This makes navigation through the app almost impossible.
Does anyone know why this is happening and if there is a solution?
Re: Roku automation framework - getFocusedElement does not return correct focused element
I have also experienced this. In the channel I am testing it is not happening for most items. However, there are some places where the "active" element I get backed from Web driver is not at all what I was expecting or what the user sees as focused.
I have been using a lot of specific element locators in my tests and I'm doing a lot of external parsing of the JSON that comes back from those queries in my assertions as opposed to relying on the "active" element query a lot.