```Yeah, it does look a little unnecessary. It looks like the test is tapping a tab and then checking that the awesome bar is visible. I would suggest perhaps tap_tab should wait for the tab to be not visible, and then this method can be reverted to the original code as the awesome bar should then already be visible.```

I agree this is the best solution. I had a play around with this but because it's a region we don't have access to the base object we can't re-use the locators for the browser app. The root_element is mis-interpreted as displayed by marionette so we can't use that either.