*Contact emails* [email protected] *Explainer* https://github.com/mfreed7/split-tabs
*Specification* *No information provided* *Summary* Split screen scenarios are increasingly common. In addition to dual screen devices (i.e. physical split screen), many browsers have a split tab (i.e. virtual split screen) feature, where two tabs are tiled side-by-side within a single browser window. When using a split tab, there are multiple cases in which users want to open a link and view it side-by-side with the source page. Today there is no way for a web author to request that a navigation open into a split tab. The existing navigation targets (_blank, _self, _parent, _top) cannot express this, and windowFeatures only offers popup, which opens a separate, detached browser window. Without popup, window.open() opens the content as a new full-size tab in the current window, which is the only other option available. This feature provides methods (imperative and declarative) for web authors to request that a link open in a split tab, alongside the current page. *Blink component* Blink>DOM <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EDOM%22> *Web Feature ID* Missing feature *Search tags* window.open <https://chromestatus.com/features#tags:window.open>, split tab <https://chromestatus.com/features#tags:split%20tab> *TAG review* https://github.com/w3ctag/design-reviews/issues/1309 *TAG review status* Pending *Goals for experimentation* None *Risks* *Interoperability and Compatibility* There should be no compat risks, since these are new window feature values and a new attribute. (Extremely small, and acceptable, risk that existing content already uses the `windowFeatures` attribute.) The API also includes provisions for feature detection and easy progressive enhancement, such as the ability to explicitly fall back to popup behavior. *Gecko*: No signal ( https://github.com/mozilla/standards-positions/issues/1481) *WebKit*: No signal ( https://github.com/WebKit/standards-positions/issues/741) *Web developers*: Positive Private feedback is quite positive. *Other signals*: *WebView application risks* Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? *No information provided* *Ongoing technical constraints* *No information provided* *Debuggability* *No information provided* *Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?* No *Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* No *Flag name on about://flags* *No information provided* *Finch feature name* WindowOpenSplitTab *Requires code in //chrome?* False *Tracking bug* https://crbug.com/570412924 *Estimated milestones* DevTrial on desktop 158 DevTrial on Android 158 *Link to entry on the Chrome Platform Status* https://chromestatus.com/feature/5136319775899648?gate=6263386169016320 *Links to previous Intent discussions* Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDiY8jf6ETLNuj%2BXk%3DGJ89_NhUebFBBdNV9qMknZtiQhbQ%40mail.gmail.com This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDh3N94qwUvsXkO-PMoDGKzHt5F3AeYbhjAJyWg1_1H6CA%40mail.gmail.com.
