From e2e2a3aaaa0e8205da7ee16a062d693579031f33 Mon Sep 17 00:00:00 2001 From: Junhui He Date: Wed, 22 Jan 2025 00:51:45 +0000 Subject: [PATCH] update spec --- index.bs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.bs b/index.bs index 4af68dd..c5de407 100644 --- a/index.bs +++ b/index.bs @@ -75,7 +75,7 @@ The [fetch and process the linked resource](https://html.spec.whatwg.org/multipa 1. If |el|'s [=relevant settings object=] is not a [=secure context=], then return. 2. If |el|'s [=node navigable=] is not a [=top-level traversable=], then return. -3. If |el|’s [=Node/node document=] is not [=allowed to use=] the “payment” feature, then return. +3. If |el|’s [=Node/node document=] is not [=allowed to use=] the payment feature, then return. 4. If |el|'s <{link/href}> attribute's value is the empty string, then return. 5. Let |url| be the result of [=encoding-parsing a URL=] given |el|'s <{link/href}> attribute's value, relative to |el|'s [=Node/node document=]. 6. If |url| is failure, then return. @@ -99,7 +99,7 @@ Per the algorithm given above, the <{link/rel/facilitated-payment}> link needs t * No mixed content (i.e., all sub-resources must come from HTTPS). * Only on top-level context (not inside of an iframe). * The tab is active. -* No Permissions-Policy restrictions on the "payment" feature. (i.e., pages can disable <{link/rel/facilitated-payment}> links via `Permissions-Policy: payment=()` HTTP header.) +* No Permissions-Policy restrictions on the payment feature. (i.e., pages can disable <{link/rel/facilitated-payment}> links via `Permissions-Policy: payment=()` HTTP header.) Also, as mentioned in the previous section, the detected <{link/rel/facilitated-payment}> link needs to be validated before further processing.