Skip to content

Conversation

@annevk
Copy link
Member

@annevk annevk commented Sep 8, 2023

This builds on a13cfbe and 80f036c. This removes the need for resulting URL string and resulting URL record and makes parse a URL return a URL record directly.


I worked on this during XSLeaks, but I think it's good. It was a pretty mechanical process though there were some surprising cases and there's some lack of consistency in how we word things. Curious to hear what you think @domenic!


/dnd.html ( diff )
/form-control-infrastructure.html ( diff )
/iframe-embed-object.html ( diff )
/input.html ( diff )
/links.html ( diff )
/media.html ( diff )
/microdata.html ( diff )
/nav-history-apis.html ( diff )
/scripting.html ( diff )
/semantics.html ( diff )
/system-state.html ( diff )
/urls-and-fetching.html ( diff )
/webappapis.html ( diff )
/workers.html ( diff )
/worklets.html ( diff )

This builds on a13cfbe and
80f036c. This removes the need for
resulting URL string and resulting URL record and makes parse a URL
return a URL record directly.
@annevk annevk requested a review from domenic September 8, 2023 14:05
Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, it's amazing we've been using this awkward tuple-returning thing for so long, when only a handful of algorithms used both the string and URL record versions. Very nice!

I wonder if this will break other specs. Probably some monkeypatch ones...

@annevk annevk merged commit f13080b into main Sep 10, 2023
@annevk annevk deleted the annevk/parse-a-url branch September 10, 2023 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants