- From: Dan Clark <notifications@github.com>
- Date: Wed, 03 Jun 2026 09:47:19 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 3 June 2026 16:47:23 UTC
dandclark left a comment (w3ctag/design-reviews#1192) Thanks @robertlin-chromium for the reply. We agree that a JavaScript object model for speculation rules could be developed orthogonally to this change. What's different about this proposal is that all of the expected use cases are dynamic. While this might not yet be enough to tip the balance towards implementing a JS API surface, it's something to strongly consider if further primarily-dynamic extensions of speculation rules are developed. The main question we'd like to see further exploration of is whether this is going to be something that any implementation supporting speculation rules would need to adopt (which the state of the spec seems to imply), or if this is a Chrome-only limitation (meaning it could conceivably be removed someday, with possible corresponding edits to the pre-navigation/CSP specs). Other browser implementations of speculation rules would of course help to answer that question. Overall we'll mark this `Satisfied with concerns`; this is a modest addition to solve a clear roadblock that developers are hitting with the API today. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1192#issuecomment-4614722189 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1192/4614722189@github.com>
Received on Wednesday, 3 June 2026 16:47:23 UTC