On Tue, Mar 27, 2018 at 11:48 AM, Dave Townsend <dtowns...@mozilla.com> wrote: > My understanding is that it has been effectively unsupported for some time > anyway so I think we should just go ahead and disable it altogether at this > point. If we need bits for automated tests then we should work to switch > tests away from those if we can.
Some rendering codepaths are only exercised by XUL. For example, in bug 1205630 I fixed a tab-bar rendering issue, and I had to write a XUL reftest as my regression test, because that's the only thing I could get to exercise the affected code. I think it's important that, as long as our browser UI uses the relevant XUL features, the corresponding test coverage remains in place. In turn, being able to load a XUL page locally (which I've been doing with "dom.allow_XUL_XBL_for_file", not sure if there's another way), is useful for writing such a XUL test. Cheers, Botond _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
