From 7a804c8603a5ba04cfbc45d285fbc51f071c51a2 Mon Sep 17 00:00:00 2001 From: chaals Date: Fri, 2 Mar 2018 14:49:39 +0100 Subject: [PATCH] simplify condition in ping processing Editorial --- sections/semantics-links.include | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sections/semantics-links.include b/sections/semantics-links.include index 1d5c7dabb8..c21f0f9ab2 100644 --- a/sections/semantics-links.include +++ b/sections/semantics-links.include @@ -943,10 +943,10 @@ - If a hyperlink created by an <{a}> or <{area}> element has a <{links/ping}> attribute, - and the user follows the hyperlink, and the value of the element's <{links/href}> attribute can be parsed - relative to the element's node document without failure, then the user agent must take the <{links/ping}> - attribute's value, split that string on ASCII whitespace, parse each resulting token relative to the element's node document, + If a hyperlink created by an <{a}> or <{area}> element has a <{links/ping}> attribute whose <{links/href}> attribute can be parsed + relative to the element's node document without failure, and the user follows the hyperlink, + then the user agent must take the <{links/ping}> attribute's value, split that string on spaces, + parse each resulting token relative to the element's node document, then run these steps for each resulting URL record ping URL (ignoring tokens that fail to parse): * If ping URL's scheme is not an HTTP(S) scheme, then return.