The focus-existing (and navigate-existing) do not actually focus the window #84
Labels
Comments
|
For now I've cargo culted off the notification API that more handwavily just says to bring it in focus: https://notifications.spec.whatwg.org/#activating-a-notification |
alancutter
added a commit
that referenced
this issue
Nov 8, 2022
…er behaviors (#79) This builds on top of w3c/manifest#1056 which adds a launch web application algorithm to the manifest spec. This updates the launch handler spec to replace that algorithm with its own. This enables other webapp specs (not in WICG) to gain the launch_handler behaviour without directly referencing this WICG spec. Additionally this replaces the concept of "web app launch client" with the existing "application context" concept from the manifest spec which is effectively the same thing. #67 #69 #84 #79
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the algorithm to prepare a web app launch client, we should explicitly say to focus the window. (This is not an implementation detail left to the user agent; it's something that other specs, notably
window.focus(), can do.)We should cargo-cult this off the
window.focus()algorithm which looks like it primarily invokes an algorithm called focusing steps but there may be details fromwindow.focus()that we want to use as well. (I'd like to briefly understand focusing steps before blindly calling it.)The text was updated successfully, but these errors were encountered: