Bug 226168
| Summary: | WebKit renders XHTML files using HTML parser | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | John A. Bilicki III <jab_creations> |
| Component: | XML | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap, cdumez |
| Priority: | P2 | ||
| Version: | Safari 14 | ||
| Hardware: | All | ||
| OS: | macOS 11 | ||
John A. Bilicki III
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
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.