We've been discussing two broad design approaches in this thread: low-level primitives, on top of which a variety of things can be built; and more focused, high-level APIs (ref [Design Principle 2.2: Consider tradeoffs between high level and low level APIs](https://w3ctag.github.io/design-principles/#high-level-low-level)). We understand that your team feels that the proposed low-level approach provides improved privacy versus the status quo. TAG feels that a higher-level API is more appropriate in this case, as it would avoid the potential for user confusion and abuse. However, we haven't talked much about the use case(s). Does your team foresee any additional use cases for short-lived, partitioned, pop-up-like UI—_other_ than login—that aren't met by existing APIs? If there are several use cases beyond login, that would make a better argument that the platform needs a low-level primitive for this. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/956#issuecomment-2579377103 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/956/2579377103@github.com>
Received on Thursday, 9 January 2025 07:56:12 UTC