kc3-lang/libxml2/test/HTML
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
bc0bb67b | 2025-07-10 11:20:22 | html: Don't abort on encoding errors Always enable recovery mode when parsing HTML, so we don't raise fatal errors. Regressed with 462bf0b7. Fixes #947. | |
|
71122421 | 2025-02-13 14:04:10 | html: Make implied <p> tags more deterministic libxml2's HTML parser adds <p> start tags in some situations. This behavior, which doesn't follow any standard, was added in 2000, see here: http://veillard.com/XML/messages/0655.html Text nodes that only contain whitespace don't imply a <p> tag, but the whitespace check cannot work reliably if we're parsing partial text data which can happen with both pull and push parser. The logic in `areBlanks` is hard to follow. The checks involving `CUR` depend on the position of the input pointer and seem dubious. It's also possible that the behavior changed inadvertently with a later commit. As a result, it's hard to come up with good test cases. We now process leading whitespace before creating implied tags. This is more in line with HTML5 and should avoid at least some issues with partial text data. For example, parsing the string "<head> x" used to result in: <html> <head></head> <body><p> x</p></body> </html> And now results in: <html> <head> </head> <body><p>x</p></body> </html> Except for the implied <p> tag, this matches HTML5. | |
|
e1834745 | 2024-09-07 00:54:25 | html: Add character data tests | |
|
59511792 | 2024-09-03 15:52:44 | html: Parse named character references according to HTML5 | |
|
e3959461 | 2023-11-30 16:15:46 | html: Reenable buggy detection of XML declarations Switch to UTF-8 if a document starts with '<?xm' to match old behavior. Also enable this check in the push parser. Fixes #637. | |
|
d7d0bc65 | 2023-03-31 16:47:48 | SAX2: Ignore namespaces in HTML documents In commit 21ca8829, we started to ignore namespaces in HTML element names but we still called xmlSplitQName, effectively stripping the namespace prefix. This would cause elements like <o:p> being parsed as <p>. Now we leave the name untouched. Fixes #508. | |
|
e986d09c | 2022-07-15 14:02:26 | Skip incorrectly opened HTML comments Commit 4fd69f3e fixed handling of '<' characters not followed by an ASCII letter. But a '<!' sequence followed by invalid characters should be treated as bogus comment and skipped. Fixes #380. | |
 |
24cdc890 | 2021-07-17 14:06:49 | test coverage for abruptly-closed comments These establish baseline behavior so that the subsequent commit is clear about the behavior it will modify. | |
|
2732b234 | 2022-01-10 13:32:14 | Fix regression parsing public IDs literals in HTML Fix regression introduced when reworking htmlParsePubidLiteral in commit 93ce33c2. Fixes #318. | |
|
e28d9347 | 2020-08-04 14:53:19 | add test coverage for incorrectly-closed comments this establishes the baseline behavior so that subsequent commits which modify this behavior are clear about what's being changed. |