Bug 226168 - WebKit renders XHTML files using HTML parser
Summary: WebKit renders XHTML files using HTML parser
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: XML (show other bugs)
Version: Safari 14
Hardware: All macOS 11
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-24 01:27 PDT by John A. Bilicki III
Modified: 2021-05-24 15:00 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John A. Bilicki III 2021-05-24 01:27:08 PDT 
I encountered and reported a bug earlier and created an XHTML file as a test case:
https://bugs.webkit.org/show_bug.cgi?id=226148

HTML parsers will return fully uppercase strings when referencing nodeName.
XML parsers will return fully properly cased strings when referencing nodeName (e.g. table for table, Table for Table).

XHTML files should be rendered using the XML parser, not the HTML parser.
Comment 1 Alexey Proskuryakov 2021-05-24 15:00:57 PDT 
I think the implied steps to reproduce are:
1. Open https://bugs.webkit.org/attachment.cgi?id=429442
2. Press a key
3. Observe an upper case tag name instead of lower case.

I cannot reproduce this in Safari, and also I'm pretty certain that WebKit uses XML parser for application/xhtml+xml.