On 7/15/13 3:05 PM, Josh Matthews wrote:
https://github.com/mozilla/servo/wiki/Meeting-2013-07-15
Some comments on the discussion (sorry I couldn't make the meeting, and
thank you for the notes!):
1) Mutable prototypes will be supported in SpiderMonkey (and indeed
are), but they will
people like roc say we must be at least as fast as Gecko for everything
To be clear: I think Servo's architecture must not prevent Servo from being
as fast as Gecko for everything. I push for microbenchmarks targeting the
risky parts of Servo's architecture because we must avoid discovering much
For compositing with IFRAMEs, you might want to consider what we do for
multi-process compositing in Gecko. It's somewhat obvious but it seems like
it works well. Each process publishes a layer tree to the compositor. A
layer tree can contain RefLayers, each with a unique ID. A layer tree root
can
On 7/15/13 4:32 PM, Robert O'Callahan wrote:
A minor random thought related to that design:
Using integer IDs, as Gecko does, raises the possibility of a bug,
possibly even a security bug, where a rogue IFRAME is able to render
itself at the wrong place in the tree. In Gecko, preventing a
4 matches
Mail list logo
