I think I'd prefer to just use QQuickWindow::activeFocusItem in oxide::qquick::ContentsView::HasFocus(). From looking at the code, I don't even think that QQuickItem::hasActiveFocus has the correct semantics as it will indicate active focus for ancestors of the active focus item which isn't really what we want (ie, if an application adds another item as a child of the webview, we shouldn't think we're actively focused if the child item is the active focus item).
We should really add some integration tests for these cases in qt/tests/qmltests/web_platform -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
