Re: De-XBL Plans

2017-10-31 Thread Bobby Holley
As one of the lonely few peers for our XBL implementation, I am thrilled that this is finally happening. My deepest gratitude to everyone involved! bholley On Tue, Oct 31, 2017 at 3:06 PM, Dave Townsend wrote: > Having not heard any show-stopping concerns with the plan we will start to > proce

Re: De-XBL Plans

2017-10-31 Thread Dave Townsend
Having not heard any show-stopping concerns with the plan we will start to proceed with it. In Q4 we intend to: - Migrate a few bindings and update the plan based on what we learn - Land XUL support for Custom Elements - Create tooling to make converting bindings easier - Begin a b

Re: De-XBL Plans

2017-10-23 Thread Brian Grinstead
> On Oct 22, 2017, at 3:35 AM, smaug wrote: > > On 10/21/2017 11:45 PM, Yura Zenevich wrote: >> I would also like to bring to the team's attention another force worth >> being on the radar (in terms of "forces on the system") - accessibility. >> One theme that seems to consistently happen with r

Re: De-XBL Plans

2017-10-22 Thread Hsin-Yi Tsai
2017年10月22日 下午6:45,"smaug" 寫道: On 10/21/2017 01:14 PM, Philipp Kewisch wrote: > On 10/20/17 7:47 PM, Dave Townsend wrote: > >> For some time now we've been talking about moving away from XUL and XBL. >> The browser architecture team has been hard at work figuring out how to go >> about doing that

Re: De-XBL Plans

2017-10-22 Thread smaug
On 10/21/2017 01:14 PM, Philipp Kewisch wrote: On 10/20/17 7:47 PM, Dave Townsend wrote: For some time now we've been talking about moving away from XUL and XBL. The browser architecture team has been hard at work figuring out how to go about doing that and we're ready to share the first of our

Re: De-XBL Plans

2017-10-22 Thread smaug
On 10/21/2017 11:45 PM, Yura Zenevich wrote: I would also like to bring to the team's attention another force worth being on the radar (in terms of "forces on the system") - accessibility. One theme that seems to consistently happen with re-writes such as the ones from xul to React is regressions

Re: De-XBL Plans

2017-10-21 Thread Yura Zenevich
I would also like to bring to the team's attention another force worth being on the radar (in terms of "forces on the system") - accessibility. One theme that seems to consistently happen with re-writes such as the ones from xul to React is regressions in terms of accessibility of newly re-written

Re: De-XBL Plans

2017-10-21 Thread Philipp Kewisch
On 10/20/17 7:47 PM, Dave Townsend wrote: > For some time now we've been talking about moving away from XUL and XBL. > The browser architecture team has been hard at work figuring out how to go > about doing that and we're ready to share the first of our proposals more > widely. We have developed a

Re: De-XBL Plans

2017-10-20 Thread Cameron McCormack
On Sat, Oct 21, 2017, at 01:47 AM, Dave Townsend wrote: > Are there any other concerns that we're missing? One thing I'm wondering about is memory usage of the Web Components implementations of these components compared to the XBL ones. Specifically for style, XBL has the ability to list the style