From 7b80c9105082ee218344ed6e6abe37147a52b367 Mon Sep 17 00:00:00 2001 From: "L. David Baron" Date: Fri, 22 May 2020 17:12:17 -0700 Subject: [PATCH 1/4] Add portals (harmful). Closes #157. --- activities.json | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/activities.json b/activities.json index 571bbab5..38fe6fbe 100644 --- a/activities.json +++ b/activities.json @@ -602,6 +602,18 @@ "title": "Picture-in-Picture", "url": "https://wicg.github.io/picture-in-picture/" }, + { + "ciuName": null, + "description": "This specification defines a mechanism that allows for rendering of, and seamless navigation to, embedded content.", + "id": "portals", + "mozBugUrl": null, + "mozPosition": "harmful", + "mozPositionDetail": "The Portals proposal introduces a significant amount of complexity to the web without either (a) clearly explaining how it differs and doesn't differ from the iframe element or (b) a serious attempt to specify how it interacts with the large number of existing web features (including aspects of the origin model) many of which are critical for security and how it interacts with existing privacy features in web browsers (such as those that depend on partitioning of storage based on origins). We believe the proposal as it exists today is harmful, but would be willing to reconsider given a more clearly motivated and clearly specified proposal.", + "mozPositionIssue": 157, + "org": "Proposal", + "title": "Portals", + "url": "https://wicg.github.io/portals" + }, { "ciuName": null, "description": "Powerful web applications would like to exchange data with native applications via the OS clipboard (copy-paste). The existing Web Platform has a high-level API that supports the most popular standardized data types (text, image, rich text) across all platforms. However, this API does not scale to the long tail of specialized formats. In particular, non-web-standard formats like TIFF (a large image format), and proprietary formats like .docx (a document format), are not supported by the current Web Platform. Raw Clipboard Access aims to provide a low-level API solution to this problem, by implementing copying and pasting of data with any arbitrary Clipboard type, without encoding and decoding.", From 1002d5d78c25a49e07d1496514d60b65385865bb Mon Sep 17 00:00:00 2001 From: "L. David Baron" Date: Wed, 27 May 2020 12:43:52 -0700 Subject: [PATCH 2/4] Add trailing / to URL. Co-authored-by: Anne van Kesteren --- activities.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/activities.json b/activities.json index 38fe6fbe..74ab0489 100644 --- a/activities.json +++ b/activities.json @@ -612,7 +612,7 @@ "mozPositionIssue": 157, "org": "Proposal", "title": "Portals", - "url": "https://wicg.github.io/portals" + "url": "https://wicg.github.io/portals/" }, { "ciuName": null, From 343d0dc03558406be243d70db329577dae79eabd Mon Sep 17 00:00:00 2001 From: "L. David Baron" Date: Fri, 29 May 2020 12:37:44 -0700 Subject: [PATCH 3/4] Convert to a defer position based on @domenic's comment in #345. --- activities.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/activities.json b/activities.json index 74ab0489..d0a212c0 100644 --- a/activities.json +++ b/activities.json @@ -607,8 +607,8 @@ "description": "This specification defines a mechanism that allows for rendering of, and seamless navigation to, embedded content.", "id": "portals", "mozBugUrl": null, - "mozPosition": "harmful", - "mozPositionDetail": "The Portals proposal introduces a significant amount of complexity to the web without either (a) clearly explaining how it differs and doesn't differ from the iframe element or (b) a serious attempt to specify how it interacts with the large number of existing web features (including aspects of the origin model) many of which are critical for security and how it interacts with existing privacy features in web browsers (such as those that depend on partitioning of storage based on origins). We believe the proposal as it exists today is harmful, but would be willing to reconsider given a more clearly motivated and clearly specified proposal.", + "mozPosition": "defer", + "mozPositionDetail": "While this proposal is in the early stages of development and it is too early to evaluate fully, there are concerns that we would like to see addressed as it develops. Most significantly, it needs to explain its interaction with the Web's storage mechanisms in a way that doesn't contribute to third-party tracking or reduce the effectiveness of proposals designed to mitigate such tracking (such as those that partition storage based on toplevel origins). It also needs to justify the (still undetermined) amount of complexity that it adds to the web platform with sufficiently valuable use cases to justify that complexity.", "mozPositionIssue": 157, "org": "Proposal", "title": "Portals", From 64fb94a4526bfbe57d3f49da7d3c5911765974ed Mon Sep 17 00:00:00 2001 From: "L. David Baron" Date: Fri, 29 May 2020 15:23:23 -0700 Subject: [PATCH 4/4] Link directly to copy (in issue) of @domenic's comment. --- activities.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/activities.json b/activities.json index d0a212c0..a233196c 100644 --- a/activities.json +++ b/activities.json @@ -608,7 +608,7 @@ "id": "portals", "mozBugUrl": null, "mozPosition": "defer", - "mozPositionDetail": "While this proposal is in the early stages of development and it is too early to evaluate fully, there are concerns that we would like to see addressed as it develops. Most significantly, it needs to explain its interaction with the Web's storage mechanisms in a way that doesn't contribute to third-party tracking or reduce the effectiveness of proposals designed to mitigate such tracking (such as those that partition storage based on toplevel origins). It also needs to justify the (still undetermined) amount of complexity that it adds to the web platform with sufficiently valuable use cases to justify that complexity.", + "mozPositionDetail": "While we are deferring evaluation of this proposal, because per Domenic's comment it is in the early stages of development and it is too early to evaluate fully, there are concerns (serious enough to mark it as harmful) that we would like to see addressed as it develops. Most significantly, it needs to explain its interaction with the Web's storage mechanisms in a way that doesn't contribute to third-party tracking or reduce the effectiveness of proposals designed to mitigate such tracking (such as those that partition storage based on toplevel origins). It also needs to justify the (still undetermined) amount of complexity that it adds to the web platform with sufficiently valuable use cases to justify that complexity.", "mozPositionIssue": 157, "org": "Proposal", "title": "Portals",