- From: koba Mobile2 <koba@antenna.co.jp>
- Date: Tue, 26 Oct 2010 08:56:23 +0900
- To: www-style@w3.org, howcome@opera.com
Hakon > 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. The requests from end users or market is more important than any implementation cost or memory cost. Your opinion is an excuse from an incompetent implementor. > There's also the inside/outside duality. If we want to address that > issue with a similar property-doubling approach, we need another 35 or > so properties. > And then there's the values. For example, 'float' accept 'right', > 'left', 'top', 'bottom' (in GCPM). Should we duplicate these? There's > a long list of issues like these that will come up. Are you stating that CSS is already a dead technology ? > Rather, I think it's better to continue to use the existing property > names -- top, right, bottom, left are universal concepts with no bias. Top, right, bottom, left are device dependent direction, they are not universal. Regards, Tokushge Kobayashi President Antenna House, Inc. 小林 徳滋 -- Antenna House, Inc. E-mail koba@antenna.co.jp WWW http://www.antenna.co.jp/ (Japanese) Blog http://blog.antenna.co.jp/ILSoft/ (Japanese) Twitter @AntennaInfo WWW http://www.antennahouse.com/ (English) TEL +81-3-5829-9021 FAX +81-3-5829-9023
Received on Monday, 25 October 2010 23:56:57 UTC