In case you missed it elsewhere, the talks that Josh and I recently
gave are both online now:
Servo: Designing and Implementing a Parallel Browser - Jack Moffitt -
Strange Loop 2013
http://www.infoq.com/presentations/servo-parallel-browser
Servo: Parallelizing the Browser - Josh Matthews - FOSDEM
On 14/02/14 12:47 PM, Jack Moffitt wrote:
> Servo: Designing and Implementing a Parallel Browser - Jack Moffitt -
> Strange Loop 2013
> http://www.infoq.com/presentations/servo-parallel-browser
Sadly this require a login reserved to the conference attendees :-(
Hub
___
My apologies. That video is scheduled for release on April 7. :(
jack.
On Fri, Feb 14, 2014 at 10:54 AM, Hubert Figuière wrote:
> On 14/02/14 12:47 PM, Jack Moffitt wrote:
>> Servo: Designing and Implementing a Parallel Browser - Jack Moffitt -
>> Strange Loop 2013
>> http://www.infoq.com/presen
On 2/13/14 4:54 PM, Robert O'Callahan wrote:
On Fri, Feb 14, 2014 at 1:43 PM, Boris Zbarsky wrote:
On 2/13/14 5:56 PM, Robert O'Callahan wrote:
2) Fragmentation. With something like overflow:fragments, absolute
positioning can affect the number of fragments you generate, which can
affect the
On Friday 2014-02-14 13:54 +1300, Robert O'Callahan wrote:
> On Fri, Feb 14, 2014 at 1:43 PM, Boris Zbarsky wrote:
>
> > On 2/13/14 5:56 PM, Robert O'Callahan wrote:
> >
> >> 2) Fragmentation. With something like overflow:fragments, absolute
> >> positioning can affect the number of fragments you
On Friday 2014-02-14 15:53 -0800, Patrick Walton wrote:
> So I just looked at the relevant piece of this spec and I'm confused:
>
> http://dev.w3.org/csswg/css-overflow-3/#fragment-pseudo-element
>
> Suppose that I have a document like this:
>
>
> .a { position: relative; }
>
On 2/14/14 4:15 PM, L. David Baron wrote:
The overflow:fragments spec should probably either (a) say the same
or (b) require fragments following an absolutely positioned fragment
to also be absolutely positioned. I'm in favor of (b), I think. (I
think there might also need to be a constraint ab
I filed https://github.com/mozilla/servo/issues/1676 a few days ago but
there hasn't been any discussion yet; I think it's important to sort out
this problem now so we don't have to do a lot of backtracking when we
get around to implementing the COW DOM.
In brief, we have various methods in la
On 2/14/14 9:16 PM, Josh Matthews wrote:
For the short term I'm interested in making layout code always go for
the attributes, because relying on sprinkling
wait_until_safe_to_modify_dom all over content code is easy to get
wrong. Thoughts?
There's some DOM state layout needs that's not actuall
On 02/15/2014 03:16 AM, Josh Matthews wrote:
For the short term I'm interested in making layout code always go for
the attributes, because relying on sprinkling
wait_until_safe_to_modify_dom all over content code is easy to get
wrong. Thoughts?
As long as it doesn't mean we have to duplicate th
10 matches
Mail list logo
