XUL/XBL Replacement Newsletter #7
bgrinstead at mozilla.com
Tue Aug 28 16:54:32 UTC 2018
> On Aug 24, 2018, at 2:43 PM, Kris Maglione <kmaglione at mozilla.com> wrote:
>> The tricky part with going the other direction (XUL doc, HTML elements) is that we have elements that are still XUL, and the XUL flexbox layout and CSS layouts don’t play well together. So migrating parts of the UI at a time into HTML elements is going to cause CSS/layout headaches unless if the parts can be pretty isolated from each other. I’m not sure I can describe all the problems exactly, but I’ve experienced this first hand when trying to put HTML inside XUL parents in the Inspector panel - things just don’t display correctly and the behavior isn’t specified AFAIK. I can dig up some bugs if you’re interested in details.
> I would be interested, yes. Thanks.
I’ve asked the frontend team if they could point me to more examples, but https://bugzilla.mozilla.org/show_bug.cgi?id=1437302#c8 and https://bugzilla.mozilla.org/show_bug.cgi?id=1259812#c16 (which resulted in https://searchfox.org/mozilla-central/source/devtools/client/themes/inspector.css#137-144) are two I found so far.
It’s possible this is doable and I just don’t know the right tricks, but AFAIK the behavior is unspecified and attempting to use it turns into spending a lot of time experimenting in the Browser Toolbox and then eventually abandoning it and using XUL elements/flexbox.
More information about the firefox-dev