Re: [w3ctag/design-reviews] Speculation rules: target_hint field (Issue #931)

For our background:
1. https://github.com/WICG/nav-speculation/pull/173/files#diff-086d7831ccea2721156a3a66a719f58f0eb0501d4b0da344f07e7a0df46a3efeR151, saying it would take a year or so of engineering effort to remove the need for this field, was merged about 2 years ago. Is there an updated estimate for how long this field will be around? I see that https://issues.chromium.org/361129302 exists to track progress on this effort, but it doesn't have that estimate.
2. Have you gotten any indications from Gecko or WebKit (even though they haven't supported prerendering itself) about whether they'd have the same implementation constraint that benefits from this field? Does this field affect [Mozilla's argument against the JSON syntax](https://github.com/mozilla/standards-positions/issues/620#issuecomment-2039825825)? Without having deeply investigated it, this field might support their argument to put `rel="nav-prerender"` on `<a>` tags since those already have the `target` attribute.

FWIW, after skimming the description, it seems like this is designed well, so that it can fade away once it's no longer needed, and that it doesn't add much complexity.

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

Message ID: <w3ctag/design-reviews/issues/931/2337094570@github.com>