Firefox/XUL and XBL Replacement: Difference between revisions
(Add #16) |
(Add 17) |
||
| Line 32: | Line 32: | ||
* [https://groups.google.com/d/msg/firefox-dev/icYnbTVPHjo/l4R3cPfQAgAJ Newsletter #15] | * [https://groups.google.com/d/msg/firefox-dev/icYnbTVPHjo/l4R3cPfQAgAJ Newsletter #15] | ||
* [https://groups.google.com/d/msg/firefox-dev/WGcGYaQgu3g/-Z5jtoWdEAAJ Newsletter #16] | * [https://groups.google.com/d/msg/firefox-dev/WGcGYaQgu3g/-Z5jtoWdEAAJ Newsletter #16] | ||
* [https://groups.google.com/d/msg/firefox-dev/3UBCgl3hjQE/D8kkrQCqCwAJ Newsletter #17] | |||
Revision as of 19:24, 9 October 2019
Summary
Originally, XUL filled feature gaps in the Web platform needed to build the Firefox UI. Now, the web has evolved enough that these gaps are largely closed. By more closely aligning the Firefox UI with web standard technologies, we expect to be able to move faster and better focus on performance and tooling for the web.
The work is being done in a number of separate projects. See the XUL/XBL Replacement Roadmap document for more details.
Tracking Dashboard
The XBL Replacement project has a website, including a set of graphs tracking progress, and a binding tree showing inheritance and features used for each binding.
CSS flexbox emulation is running in a couple of talos tests - tart and ts_paint.
Newsletters
The primary way that status updates are communicated are through newsletters to firefox-dev: