On Monday, January 23, 2017 at 12:03:35 PM UTC-8, Eric Shepherd wrote: > It seems to me, anyway, that the ideal solution would be to enhance HTML > (ideally in the spec) with the features needed to build a full-fledged > desktop UI. That would be fabulous not just for Firefox making the transition > to defining its UI in HTML, but could potentially be adopted by other > projects and platforms that use JavaScript and HTML to build apps (such as > Electron).
This is, by the way, what we're doing with Intl. We're replacing all of our Intl APIs with TC39 ECMA402 backed Intl APIs (driven by CLDR) and when we find a limitation, we introduced a `mozIntl` chrome-only API which serves us as a place where we close the gap while maintaining future compatibility and at the same time we use it to test ideas for future ECMA402 extensions. This model has been received really well by TC39 so far and keeps us on a path with a multi-win: 1) We're aligned with the spec work 2) We're championing a lot of the spec work 3) We have a reason to believe that eventually, all of mozIntl will end up in ECMA402 4) Moving things from mozIntl into Intl once it gets into spec is easy I can totally imagine us doing it for HTML. zb. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
