I wanted to shed more light on our console UI progress. I wouldn't say that
we're nearly done, but I do think that were at a stage now where we can
start thinking about how to best serve Servo. We are splitting the work
into three phases.
1. console message output
2. object inspection
3. JS termin
> On Jul 8, 2016, at 10:36 PM, Manish Goregaokar wrote:
>
>> Our understanding is that your plan was to take out your Firefox devtools
>> protocol support and start implementing the Chrome protocol, once your June
>> demos were done. Have you started work on this?
>
> Not that I am aware of. I'd
> Our understanding is that your plan was to take out your Firefox devtools
> protocol support and start implementing the Chrome protocol, once your June
> demos were done. Have you started work on this?
Not that I am aware of. I'd be willing to help if I get time, though.
The Chrome RDP is base
On Fri, Jul 8, 2016 at 5:50 PM, Jim Blandy wrote:
> Our web console UI uses some HTML/CSS features that Servo doesn't yet
> support. We could file bugs for these if they would be of interest to you;
> would they?
My understanding is that Servo is happy to have such issues on file. A
while ago whe
Dear Servo folks,
We devtools folks are almost done converting our web console UI to pure
HTML, so we're planning our further work for Q3 and Q4. We have a few
questions for you:
Our understanding is that your plan was to take out your Firefox devtools
protocol support and start implementing the
5 matches
Mail list logo
