- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Fri, 24 Oct 2025 20:01:30 +0000
- To: public-css-archive@w3.org
Per Tim's later comments, now that he sees the SW connection driving the API design, he's not suggesting any changes. I don't think we should jump the gun and complicate things here either, unless there's a use-case driving it. ^_^ (And fwiw, a "replaceable promise" can be created with existing Promises today without much difficulty. You make a wrapper Promise that's manually resolved, and do a little state juggling inside of it to make sure you can swap internal promises and tell, on resolution, whether you're currently responding to the latest promise or an earlier one, then resolve the wrapper Promise accordingly. We don't have manual API for it because it hasn't proven to be a use-case that people run into enough to ask for help with.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13014#issuecomment-3444721120 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 October 2025 20:01:31 UTC