On 8/27/13 1:48 AM, Simon Sapin wrote:
Maybe also writing modes / vertical text?
Even if the actual feature is not a priority, it might be easier to
rewrite the layout code to use logical keywords (eg. measure/extent
instead of width/height) while we don’t have much layout code.
http://dev.w3.o
Le 27/08/2013 05:23, Patrick Walton a écrit :
It definitely makes sense to get incremental layout (and perhaps bidi)
working before redoing too much code that would have to be rewritten.
Maybe also writing modes / vertical text?
Even if the actual feature is not a priority, it might be easier
On 8/26/13 9:11 PM, L. David Baron wrote:
Is it worth prioritizing having working incremental layout so that
you can benchmark the architecture for doing incremental updates
(and make sure it performs acceptably) over these tasks that you
list? (As somebody following from a distance, I'm more co
On Monday 2013-08-26 16:17 -0700, Patrick Walton wrote:
> Other than that,
> the largest tasks will be implementing tables, followed by
> `position: absolute` and `position: fixed`. There are several other,
> smaller tasks which are cleanly separable and would be great for
> contributors if anyone
On 08/26/2013 04:17 PM, Patrick Walton wrote:
Hi everyone,
Now that we've essentially passed Acid1 (once one remaining pull
request is merged), Acid2 is on the horizon! I've identified the
issues that were immediately apparent between us and Acid2 and created
a wiki page and a milestone to tr
Hi everyone,
Now that we've essentially passed Acid1 (once one remaining pull request
is merged), Acid2 is on the horizon! I've identified the issues that
were immediately apparent between us and Acid2 and created a wiki page
and a milestone to track our progress:
https://github.com/mozilla/
6 matches
Mail list logo
