fx153: Re-enable chrome: DTD loading

Bug 2043845 put the FORCE_ALLOWED_DTD content policy type behind a pref
that's off for everything but Thunderbird, so NS_NewChannel() refused the
load with NS_ERROR_CONTENT_BLOCKED and the XML parser silently skipped the
entity. Custom elements whose markup uses DTD entities then failed to
parse with "not well-formed XML".
This commit is contained in:
Dan Stillman 2026-07-28 14:27:46 -04:00
parent 14b43c9559
commit 1c005c7e21

View file

@ -260,3 +260,6 @@ pref("svg.context-properties.content.enabled", true);
// Firefox applies a baseline "script-src chrome: resource: moz-src:" CSP to every chrome:
// document, which blocks inline <script>s and inline event handlers
pref("security.chrome_baseline_csp.enabled", false);
// Allow chrome: DTDs to be loaded, which we still use for localized strings in XUL markup
pref("dom.fetch.allow_force_allowed_dtd", true);