There are many devtools features that would be cool but are hard to prototype
in feature-laden rendering engines. For example, there is a ton of work in the
space of answering questions about layout results: “why did this element end up
over here?” or “why does this CSS rule have no effect?”.
Another topic near and dear to my upcoming dissertation is deterministic replay
of web content. In particular, it would be cool to use replay to test
performance of the rendering and JS engines. I think Adenilson Cavalcanti
started looking into this topic, but I haven’t heard anything.
-Brian
> On Apr 7, 2015, at 9:43 AM, Josh Matthews <j...@joshmatthews.net> wrote:
>
> Hello all! I've had an inquiry from a student looking for a project they
> could work on from October 2015 until May 2016. Obviously planning that far
> ahead can be challenging; they were interested in working on the canvas APIs
> but those are already in progress so I suggested we brainstorm some other
> ideas. They say they like working on "things visible to end users", so what
> are some areas that we could focus on which have limited danger of
> disappearing before it's time to commence work?
>
> Cheers,
> Josh
> _______________________________________________
> dev-servo mailing list
> dev-servo@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-servo
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
