From 8db596f6f2b8b02c55ac43515bd45f0fb712bf9d Mon Sep 17 00:00:00 2001 From: Mohammad Faiz Date: Wed, 3 Jun 2026 21:17:04 +0530 Subject: [PATCH] Editorial: fix minor markup and grammar inconsistencies in url.bs - Add missing tags on 'state' variable in query state (line 3007), matching the pattern used by all 221 other occurrences - Add missing preposition 'to' after 'pertain' in URL parsing note (line 2164): 'pertain to trust decisions' - Remove inconsistent explicit

closing tags in port setter (line 3756), matching the implicit closing used everywhere else --- url.bs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/url.bs b/url.bs index e28aec48..0aba0d99 100644 --- a/url.bs +++ b/url.bs @@ -2161,7 +2161,7 @@ different document encoding. Using the UTF-8 encoding everywhere solves t

How user input in the web browser's address bar is converted to a URL record is out-of-scope of this standard. This standard does include -URL rendering requirements as they pertain trust decisions. +URL rendering requirements as they pertain to trust decisions.

  1. Let url be the result of running the basic URL parser on input @@ -3004,7 +3004,7 @@ and then runs these steps:

  2. Set buffer to the empty string.

  3. If c is U+0023 (#), then set url's fragment to - the empty string and state to fragment state. + the empty string and state to fragment state.

  • @@ -3753,7 +3753,7 @@ one might have assumed the setter to always "reset" both. return.

  • If the given value is the empty string, then set this's URL's - port to null.

    • + port to null.

  • Otherwise, basic URL parse the given value with this's URL as url and