#1302: WG Revision: Creating Always-On-Top Windows (Window Management)

Visit on Github

Opened Nov 2, 2026

Specification

https://github.com/w3c/window-management/pull/170

Explainer

https://github.com/w3c/window-management/blob/main/EXPLAINER_always_on_top.md

Links

Feature 1: Creating Always-On-Top Windows

The specification

Where and by whom is the work is being done?

Feedback so far

You should also know that...

No response

<!-- Content below this is maintained by @w3c-tag-bot -->

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1302

Discussions

Log in to see TAG-private discussions.

Comment by @christianliebel Nov 17, 2026 (See Github)

Hi @steimelchrome, thanks for your request. We discussed this in today’s TAG breakout.

The basic idea seems fine to us. As you note in the explainer, the platform already has a similar primitive with the Document Picture-in-Picture API.

Requiring the window-management permission on top of the regular popup rules sets a high bar. We were wondering if this may even be more than the use case should have to ask for. window-management is also the permission behind getScreenDetails(), which exposes the number, positions and labels of all connected screens. An app that just wants to float a single small window needs none of that, yet has to request all of it, which may conflict with minimizing user data.

Did you consider the following?

  1. A narrower permission that only allows floating a window without exposing screen details?
  2. A user-driven path, e.g. a “keep-on-top” control in the browser’s window UI that the user can apply to a popup, without a permission at all? This would also work for windows that weren’t created through window.open(), avoid having to extend HTML’s window open steps, and let users un-pin a window without closing it.

Looking forward to your thoughts.