After a bit of investigation, I understand what’s going on: the Chrome instance is a focus scope that proxies focus requests to the address bar, and it’s itself contained in a FocusScope. Setting focus to true on chrome doesn’t imply that the active focus will change, it only guarantees that the next time the active focus is set on the enclosing focus scope, chrome will receive it.
So the current code that does "chrome.focus = true" in the onTriggered handler of the "find in page" action should really do "chrome.forceActiveFocus()". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508130 Title: 'find in page' fails to focus address bar every second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1508130/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
