-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always on Top window #443
Comments
In Firefox, extensions are able to create an always-on-top window by using the |
A popup window created by |
I am primarily opposed to this due to concern that extensions could abuse this. |
At today's meeting, due to time constraints, we talked about some history about "always on top" window and some concerns. Discussions can continue later, such as
The reason why I created this issue at this time (August 2023) is because Chrome 116 recently introduced a new API, Document Picture-in-Picture, which has already enabled web and extensions to support "always on top" window. Thanks this API. Here is the position about Document Picture-in-Picture API: Safari's position and Firefox's position. |
Simeon said at the meeting:
In the past, chrome.app.window api allowed to create an always on top window, which require the |
This is a discussion or feature request.
Desired Functionality
Like video picture-in-picture function, it is useful for extensions to be able to create a small window that always be displayed on top of other contents/windows.
Related Web API
Major browsers support picture-in-picture API. But it is only for video element, so it is not useful for other use cases.
Since Chrome 116, there is a new Document Picture-in-Picture API. This is very close to my goal, but I find that it currently has the following limitations:
Related Extension API
bowser.windows.Window
has aalwaysOnTop
property, but it can't be specified inwindows.create()
method. Developers often expect this feature and then think of this property. Existing feature requests https://crbug.com/933215 and https://crbug.com/822425.The text was updated successfully, but these errors were encountered: