Skip to content

webapi: XHR uses XML parser for XML content-type responses#3036

Merged
karlseguin merged 2 commits into
mainfrom
xhr-xmlresponse
Jul 25, 2026
Merged

webapi: XHR uses XML parser for XML content-type responses#3036
karlseguin merged 2 commits into
mainfrom
xhr-xmlresponse

Conversation

@karlseguin

Copy link
Copy Markdown
Collaborator

Expand mime type to be aware of more XML types. DOMParser and XHR now use the existing Parser.parseXML (via a Frame helper), rather than the HTML parser. Both these APIs predate the addition of parseXML.

The 2nd commit is a mechanical change where various Frame.parse* methods have been moved to a Frame.parse.* utility class (like observers and user_input). The goal is just to keep the complex Frame neater.

Expand mime type to be aware of more XML types. DOMParser and XHR now use the
existing Parser.parseXML (via a Frame helper), rather than the HTML parser. Both
these APIs predate the addition of parseXML.
Follows the observer, user_input, etc.. pattern and relocates various
`Frame.parse*` methods into Frame.parse.* functions.

Goal is just to keep Frame neat.
@karlseguin
karlseguin merged commit 063906e into main Jul 25, 2026
26 checks passed
@karlseguin
karlseguin deleted the xhr-xmlresponse branch July 25, 2026 02:50
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 25, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant