This was linked already - but comment #0 and the deps of that bug only
mention no longer relying on the XULDocument interface. That's different
from "detect and parse .xul files as XHTML" (at least, I think it is).
I'd expect a separate dependency for that, but I don't see any.
~ Gijs
On 15/05/2019 16:42, Brendan Dahl wrote:
https://bugzilla.mozilla.org/show_bug.cgi?id=1550801
On Wed, May 15, 2019 at 6:30 AM Gijs Kruitbosch <gijskruitbo...@gmail.com>
wrote:
On 14/05/2019 16:32, Brian Grinstead wrote:
1. Load all XUL documents as XHTML using the prototype cache. This
doesn’t require any file renaming, we will just detect a .xul file
and act
like it’s .xhtml. This is tracked in bug 1550801
<https://bugzilla.mozilla.org/show_bug.cgi?id=1550801>.
There doesn't seem to be a bug on file listed in that tracking bug for
actually doing the "detect a .xul file and act like it's .xhtml" bit. Is
there one already on file?
I think this step makes me the most nervous - we need to make sure that
we don't change web-observable behaviour, and that the "no remote XUL"
prohibitions continue to apply. In theory, that should all be fine
because of XHTML and namespaces, but I figured it was worth flagging up.
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
