- From: steimelchrome <notifications@github.com>
- Date: Mon, 02 Nov 2026 10:27:19 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1302@github.com>
steimelchrome created an issue (w3ctag/design-reviews#1302)
### Specification
https://github.com/w3c/window-management/pull/170
### Explainer
https://github.com/w3c/window-management/blob/main/EXPLAINER_always_on_top.md
### Links
- The WG's request for this TAG review: https://github.com/w3c/window-management/issues/10
- TAG review of the previous version of this specification, if any: https://github.com/w3ctag/design-reviews/issues/602 (also https://github.com/w3ctag/design-reviews/issues/767, https://github.com/w3ctag/design-reviews/issues/840, https://github.com/w3ctag/design-reviews/issues/1246)
- A description of what has changed since our previous review: https://github.com/w3c/window-management/pull/170
Feature 1: Creating Always-On-Top Windows
- Previous early design review, if any: N/A
- An introduction to the feature, aimed at unfamiliar audiences: https://github.com/w3c/window-management/blob/main/EXPLAINER_always_on_top.md#1-introduction--abstract
- A description of the problems that end-users were facing before this proposal: https://github.com/w3c/window-management/blob/main/EXPLAINER_always_on_top.md#2-use-cases--user-motivation
- Alternatives considered: https://github.com/w3c/window-management/blob/main/EXPLAINER_always_on_top.md#6-alternatives-considered
- Examples of how to use the proposal to solve the end-users' problems: https://github.com/w3c/window-management/blob/main/EXPLAINER_always_on_top.md#4-feature--permission-detection
- What do the end-users experience with this proposal: https://github.com/w3c/window-management/blob/main/EXPLAINER_always_on_top.md#3-proposed-api
- User research you did to validate the problem and/or design, if any: N/A
- Web Platform Tests: In progress (will be added under https://wpt.fyi/results/window-management)
- Security/Privacy Questionnaire: https://github.com/w3c/window-management/blob/main/security_and_privacy_always_on_top.md (in flight at https://github.com/w3c/window-management/pull/169 / https://github.com/steimelchrome/window-management/blob/explainer-followup-and-security-questionnaire/security_and_privacy_always_on_top.md)
### The specification
- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [x] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).
### Where and by whom is the work is being done?
- GitHub repo: https://github.com/w3c/window-management
- Primary contacts:
- Tommy Steimel (@steimelchrome), Google, Author
- Mike Wasserman (@michaelwasserman), Google, Editor
- Organization/project driving the specification: Google Chrome team
- This work is being funded by: Google
- Primary standards group developing this feature: Second Screen Working Group
- Incubation and standards groups that have discussed the design:
- Second Screen WG - https://github.com/w3c/window-management/issues/10, https://github.com/w3c/window-management/pull/163
### Feedback so far
- Active horizontal reviews:
- Multi-stakeholder feedback:
- Chromium comments: Prototyping behind `chrome://flags/#window-open-always-on-top` (Intent to Prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/1hrQn7ACjhI)
- Mozilla comments:
- Creating Always-On-Top Windows - https://github.com/mozilla/standards-positions/issues/1478
- Window Management (host spec) - https://github.com/mozilla/standards-positions/issues/542
- WebKit comments:
- Creating Always-On-Top Windows - https://github.com/WebKit/standards-positions/issues/737
- Window Management (host spec) - https://github.com/WebKit/standards-positions/issues/117
- Major unresolved issues with or opposition to this specification: None
- Status/issue trackers for implementations:
- ChromeStatus: https://chromestatus.com/feature/5200904761507840
- Chromium tracking bug: https://crbug.com/546631275
### 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
--
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1302
You are receiving this because you are subscribed to this thread.
Message ID: <w3ctag/design-reviews/issues/1302@github.com>
Received on Monday, 2 November 2026 18:27:23 UTC