- From: Mason Freed <notifications@github.com>
- Date: Fri, 19 Nov 2021 13:31:43 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/691@github.com>
Braw mornin' TAG! I'm requesting a TAG review of the newly-specified window.open() behavior. Per my Chromium Intent to Ship, it was [requested that I file an FYI TAG review](https://groups.google.com/a/chromium.org/g/blink-dev/c/q6ybnmxxvpE/m/zMgJSclvBAAJ) - hence this request. Here is a summary of the changes, copied from the [chromestatus entry for this change](https://chromestatus.com/feature/5663031909416960): ----- The window.open() API is currently confusing to use, in terms of trying to get it to open a popup vs. a tab/window. This change simplifies the usage by adding a single boolean argument called 'popup' that works as you'd expect: popup=1 gets you a popup, and popup=0 gets a tab/window: const popup = window.open('_blank','','popup=1'); const tab = window.open('_blank','','popup=0'); Also there were previously confusingly-behaved getters for the BarProp visible properties (e.g. window.statusbar.visible) which didn't correctly represent what was actually visible. Now, those all return true if you got a new window/tab, and false if you got a popup. This is an interop-driven change, to align Chromium with the newly-landed spec for window.open. It does not change existing behavior around whether a popup or tab/window is opened, to avoid compat issues. ----- - Explainer¹: https://chromestatus.com/feature/5663031909416960 - Specification URL: https://html.spec.whatwg.org/multipage/window-object.html#popup-window-is-requested - Tests: https://wpt.fyi/results/html/browsers/the-window-object/apis-for-creating-and-navigating-browsing-contexts-by-name?label=master&label=experimental&aligned&q=open-features-is-popup-condition.html - Primary contacts (and their relationship to the specification): - Mason Freed (@mfreed7), Google - Organization(s)/project(s) driving the specification: [Mozilla](https://github.com/whatwg/html/pull/6530) - Key pieces of existing multi-stakeholder review or discussion of this specification: https://github.com/whatwg/html/issues/5872 - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5663031909416960 Further details: - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/) - Relevant time constraints or deadlines: none - The group where the work on this specification is currently being done: WHATWG - The group where standardization of this work is intended to be done: WHATWG - Major unresolved issues with or opposition to this specification: None - This work is being funded by: Google/Mozilla We'd prefer the TAG provide feedback as (please delete all but the desired option): 💬 leave review feedback as a **comment in this issue** and @-notify @mfreed7 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/691
Received on Friday, 19 November 2021 21:31:56 UTC