W3C home > Mailing lists > Public > www-style@w3.org > June 2012

RE: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Wed, 27 Jun 2012 16:18:59 +0000
To: Daniel Holbert <dholbert@mozilla.com>, www-style list <www-style@w3.org>
CC: Morten Stenshorne <mstensho@opera.com>, Tab Atkins Jr. <jackalmage@gmail.com>
Message-ID: <2C86A15F63CD734EB1D846A0BA4E0FC8315D1D53@CH1PRD0310MB381.namprd03.prod.outlook.com>
> From: Daniel Holbert [mailto:dholbert@mozilla.com]
> Sent: Monday, June 25, 2012 1:39 PM
> Right now, when Gecko generates its internal representation of computed
> style, it does not necessarily have access to the parent node's computed
> style. (Except for inherited-by-default properties, and for properties
> that have explicitly received a specified value of "inherit").  I believe
> this lets us optimize by breaking up the style-computation work and avoid
> having to compute all the style at once. [waves hands... bz knows more on
> this. :)]

Can we please stop using "OMG Mozilla will have to change the code" as an argument?

It is totally proper to account for implementation or computation complexity when designing features, but I don't see anything in this thread that says that it is hard to do or is in fact a performance problem.

These are real issues the code has to deal with, but there is no evidence that it is a problem for performance.

Received on Wednesday, 27 June 2012 16:21:10 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:00 UTC