chromium/src
0
Fork 0
Code Activity

Prerender: Explain "activation-gated APIs" in README

Browse Source 
"Activation-gated APIs" is the term defined in the HTML spec. This is
confusing with prerendering activation, so it would be worth mentioning
this in the README.

https://html.spec.whatwg.org/C/#user-activation-gated-apis

Bug: n/a
Change-Id: If2b89b16cf178b94371a419cbf0e367427b4c184
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2842748
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874516}
This commit is contained in:
Hiroki Nakagawa
2021-04-21 01:12:10 +00:00
committed by Chromium LUCI CQ
parent b7ce8b3001
commit 57cffdf2d3
1 changed files with 5 additions and 0 deletions

5
content/browser/prerender/README.md

@ -31,6 +31,11 @@ The Prerender2 is the new implementation of prerendering.
cookies and other state related to validating cache entries. The current
prerendering uses this mechanism, that is, it does not actually render pages,
while the Prerender2 renders pages.
- **[Activation-gated APIs](https://html.spec.whatwg.org/C/#user-activation-gated-apis)**:
Web platform APIs that are dependent on user activation. Prerendered pages
never have user activation, so the activation-gated APIs automatically fail or
no-op in the prerendered pages. The known activation-gated APIs are listed
[here](https://jeremyroman.github.io/alternate-loading-modes/#activation-gated).
# References