Flexible syntax for defining what outgoing links are eligible to be prepared speculatively before navigation (e.g. prefetching, prerendering). Enables access to additional enhancements, such as use of a private prefetch proxy, where applicable.
Enable additional avenues of development for pre-navigation speculation, including requiring the anonymization of the client IP address and heuristics to identify the best outbound links to prefetch.
The platform and browser should help developers make the best use of these capabilities to accelerate navigation between pages.
The proposal is designed with forward compatibility in mind, and intends to be flexible enough to support future needs. There are no anticipated backward compatibility risks.
There is significant interoperability risk to the extent other vendors may not take the same direction, which is mitigated to some extent by the fact that this feature is a form of progressive enhancement (i.e., it is not anticipated that any site will break if this feature is not supported, but may simply experience higher latency on navigation).
Feedback on the API is, of course, welcome.
Gecko: No signal (not yet requested)
WebKit: No signal (not yet requested)
Web developers: No signals
No, though we intend to add WPT coverage as this proceeds. (It will likely need testdriver hooks to fully test.)