Re: [w3ctag/design-reviews] Script Blocking (in Incognito mode) (Issue #1114)

christianliebel left a comment (w3ctag/design-reviews#1114)

@ZainabAq Thank you for your proposal. Unfortunately, the TAG must decline to review it, as your proposal seems to be tied to a specific implementation for a single browser. The TAG's role is to consider web architecture from a broad perspective. Also, it seems to be in a very early stage, as much of the required information is missing.

Please note that this is not negative feedback. The TAG supports all efforts to make browsing more private, and we believe that your proposal could be a web platform feature, especially given that many engines have developed proprietary solutions.

For example, you could specify (or update existing specifications) that user agents are allowed to block certain fetches for privacy reasons and define how these fetches fail. We assume this is currently done by "exploiting" network behavior (e.g., ERR_BLOCKED_BY_CLIENT in Chrome).

We specifically want to point to our [Observations on Private Browsing Modes](https://www.w3.org/2001/tag/doc/private-browsing-modes/) and the [Don’t reveal that private browsing mode is engaged](https://www.w3.org/TR/design-principles/#do-not-expose-use-of-private-browsing-mode) design principle.

We encourage you to reopen this issue once the proposal is suited for standardization as a cross-engine web platform feature.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1114#issuecomment-2985276584
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1114/2985276584@github.com>