Great. It's pretty good to understand current servo features.
Is it possible to make it gated on every pull requst landed ?
--- Original Message ---
Sender : Patrick Walton
Date : 2014-11-09 07:14 (GMT+09:00)
Title : [dev-servo] CSS property usage chart
Hi everyone,
I've created a s
On Mon, Nov 10, 2014 at 1:36 PM, Patrick Walton
wrote:
> On 11/9/14 4:31 PM, Josh Matthews wrote:
>
>> I don't have any experience with these matters, but would this impact
>> our ability to support the will-change CSS property? As I understand it,
>> in Gecko the property basically means "layeri
On 11/9/14 4:31 PM, Josh Matthews wrote:
I don't have any experience with these matters, but would this impact
our ability to support the will-change CSS property? As I understand it,
in Gecko the property basically means "layerize this".
`will-change` creates a new stacking context per the spe
I don't have any experience with these matters, but would this impact
our ability to support the will-change CSS property? As I understand it,
in Gecko the property basically means "layerize this".
Cheers,
Josh
___
dev-servo mailing list
dev-servo@lis
Some other things that come to mind:
* This approach makes it trivially possible to incrementalize display
list construction at the granularity of stacking contexts. Which,
admittedly, is not a great level of granularity for many common
scenarios, but it would at least handle stuff like settin
Hi everyone,
My initial work on the implementation of `opacity`, as well as
discussions with Martin Robinson last week, have begun to make me wonder
whether we should modify Servo's layerization/display list model
somewhat. Currently, the output of layout (i.e. what layout sends to the
painti
6 matches
Mail list logo
