- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 19 Dec 2024 14:20:36 -0800
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/permissions/issues/185/2555872444@github.com>
**Summary of Issue #185** (Thanks ChatGPT) **Context:** Issue #185 focuses on whether the Permissions specification should explicitly address "transient" or "ephemeral" permissions—those granted temporarily rather than stored persistently. **Key Points:** 1. **Ephemeral Permissions Concept:** The discussion considers if the spec should acknowledge or define states in which permissions are granted only for the current session, or until certain conditions are met, rather than permanently. 2. **User Agent Variation:** Different browsers may implement ephemeral permissions differently (e.g., permissions valid only for the current tab/session). The question is whether the spec should unify these behaviors or simply acknowledge their existence. 3. **Spec Changes and Requirements:** There’s no current push for strict, normative changes. The inclination is to note that ephemeral permissions may exist, providing general guidance without imposing exact requirements. 4. **Impact on CR Transition:** This issue does not seem to block moving the Permissions specification forward. If addressed, it would likely involve adding non-normative clarifications rather than mandated changes. **Conclusion:** No major normative changes are required for Issue #185. The concept of ephemeral permissions might be acknowledged in the specification as a non-normative note, without blocking the transition to Candidate Recommendation. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/issues/185#issuecomment-2555872444 You are receiving this because you are subscribed to this thread. Message ID: <w3c/permissions/issues/185/2555872444@github.com>
Received on Thursday, 19 December 2024 22:20:39 UTC