Kris Maglione 2506454b92 Bug 1729005: Recursively block parsing for parser blocking scripts. r=hsivonen ... Bug 1333990 added the ability to have multiple parser blockers at the same time, so we no longer need to guard against recursively blocking. What's more, if we do, and skip calling `BlockParser` while it's blocked for another reason, we still call `UnblockParser` when we receive script data, at which point we crash. This patch moves the XHTML parser's behavior closer in line with the HTML parser's. The only way I've seen this manifest as a bug is when we have an XHTML document with a top-level <script> element, and an extension with content scripts that cause us to block parsing when we see that top-level element and need to wait for them to compile. Differential Revision: https://phabricator.services.mozilla.com/D145513		2022-05-09 20:08:08 +00:00
..
crashtests
resources
test
CDATASection.cpp
CDATASection.h
htmlmathml-f.ent
moz.build
nsIXMLContentSink.h
nsXMLContentSink.cpp
nsXMLContentSink.h
nsXMLElement.cpp
nsXMLElement.h
nsXMLFragmentContentSink.cpp
nsXMLPrettyPrinter.cpp
nsXMLPrettyPrinter.h
ProcessingInstruction.cpp
ProcessingInstruction.h
XMLDocument.cpp
XMLDocument.h
XMLStylesheetProcessingInstruction.cpp
XMLStylesheetProcessingInstruction.h