| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
name: "XMLParsingRust"
},
{
name: "XMLRustForNonXslt",It'd be good to add some comments to both of these, with bug links and a quick description of what they do.
Do the changes here worry you? One new pass and one new fail, on duplicate namespace declarations. (They seem small to me, and fairly corner case, but I thought I'd ask...)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
name: "XMLParsingRust"
},
{
name: "XMLRustForNonXslt",It'd be good to add some comments to both of these, with bug links and a quick description of what they do.
Yes, added descriptions and bug links now.
Do the changes here worry you? One new pass and one new fail, on duplicate namespace declarations. (They seem small to me, and fairly corner case, but I thought I'd ask...)
I consider them a smaller (I agree) edge case, which I started to analyze in https://crbug.com/41445936 - the old parser and the new parser behave slightly different here. I'll follow up on this separately.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
12 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: third_party/blink/renderer/platform/runtime_enabled_features.json5
Insertions: 9, Deletions: 0.
The diff is too large to show. Please review the diff.
```
Instantiate Rust parser in non-frame situations
XML parsing use cases through DOMParser and XMLHttpRequest do not
directly implicitly perform XSLT processing. When creating the
document for use with these APIs, the WithExecutionContext DocumentInit
constructor is used instead of the WithWindow constructor. This leads to
the distinction that GetFrame() returns false at the time of parser
construction. So we can run the non XSLT cases through XMLDocumentParser
Rs.
When the document retrieved through DOMParser or XHR is used together
with XSLTProcessor, before this change and after the parsed document is
serialized out to a string and XMLDocPtrForString or
XsltStylesheetPointer are used for re-parsing.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |