On 1/16/17 9:43 PM, Dave Townsend wrote: > One of the things I've been investigating since moving back to the > desktop team is how we can remove XUL from the application as much as > possible. The necessary first step of reducing XUL use is to stop > adding any more UI that uses XUL and here I'm talking about wholly > new UI, additions to browser.xul and other existing UI are a separate > concern. What do folks think about making this a rule for new > projects in the near future? > > Of course there are some features missing from HTML that make this > impossible in some cases right now.
I think this would be a great step forward and help towards getting rid of XUL. Thanks for kicking this off. One of the roadblocks I have had in XUL applications where I was meaning to port to HTML is the decision on what framework, if at all, to use. I know devtools has been making heavy use of react, and I can see other components following this lead. This is of course a pretty strong dependency, with the usual caveats of using an external dependency. Aside from XUL you should also make a recommendation for XBL replacements, as widgets are fairly commonly used. React allows for creating widgets, another alternative would be web components. I have seen some progress there lately but am also aware the spec is still somewhat in flux. Nevertheless, I think using web components would better allow sticking to native web technologies (and it is also my personal preference). Anyway, if you make HTML a requirement for new features, I think you also need to provide some direction on the framework to use, or if we should be sticking to the built-in tech instead. Philipp _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
