- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Mon, 25 Oct 2010 18:12:33 -0700
- To: koba Mobile2 <koba@antenna.co.jp>
- CC: John Daggett <jdaggett@mozilla.com>, www-style@w3.org, howcome@opera.com
On 10/25/2010 05:52 PM, koba Mobile2 wrote: > John Daggett wrote: >> koba Mobile2 wrote: >>> Håkon Wium Lie wrote: >>>> Implementation cost is one metric, but no the only one. For one, >>>> there's also a memory cost. I presume you have implemented this so that >>>> the logical propertie cascade and inherit separately? on a per-element >>>> basis? And cannot be resolved until you know the computed value for >>>> 'writing-mode'? If so, the memory use will be significant: ~35 >>>> property values for every element. >>> >>> Your opinion is an excuse from an incompetent implementor. >> >> No, it's the concern of an implementor who has a long history >> of developing browsers for devices that run with restricted memory. > > All browsers are not asked to support all properties. No, but desktop browsers and their equivalents are. That said, the performance and memory considerations for logical properties are not as bad as they seem at first glance. Since you can compute the logical-physical equivalence at cascade time, you only need to store one set of data per element (physical or logical, depending on your layout architecture). So the extra memory load is almost nothing. I could try to convince you that this is true, but I don't have to: Hyatt already implemented it this way and can confirm that this is the case. ~fantasai
Received on Tuesday, 26 October 2010 01:13:11 UTC