- From: L. David Baron <dbaron@dbaron.org>
- Date: Tue, 1 Jun 2010 13:36:02 -0700
- To: MURAKAMI Shinyu <murakami@antenna.co.jp>
- Cc: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp>, Hakon Wium Lie <howcome@opera.com>, www-style@w3.org, Jaeho Lee <jaeho@uos.ac.kr>, Ning Li <ningli@public2.bta.net.cn>, komachi@y-adagio.com, "KOBAYASHI Tatsuo(FAMILY Given)" <tlk@kobysh.com>, Seiichi Kato <seiichik@microsoft.com>, Masanori Kusunoki <Masanori.Kusunoki@microsoft.com>, yjkweon@keris.or.kr, Yong-Sang Cho <zzosang@gmail.com>, Sam Gyun Oh <samoh21@gmail.com>, sblim@sookmyung.ac.kr, speeno@haansoft.com, jungkwon@haansoft.com, sadian@ksa.or.kr, hykim@incube.co.kr, shik@kats.go.kr, mike@w3.org, ishida@w3.org, bert@w3.org, masao@w3.org, phobos chang <phobos.chang@gmail.com>, selena <selena@cmex.org.tw>
On Wednesday 2010-06-02 05:04 +0900, MURAKAMI Shinyu wrote: > I tested your example with WebKit (with s/Moz/webkit/), the result is: > 32px > 48px > -webkit-margin-start: 2em; margin-left: 3em; > 48px > > It seems correct. I'd like to standardize this behavior. I agree that it's one of reasonable choices for correct behavior. However, I'd probably prefer "margin-left: 3em; margin-start-value: 2em", but that only makes sense if the longhand properties are not special hidden properties. I think the cost of hidden properties in terms of object model complexity is probably not worth their benefits. But the real issue isn't what the correct behavior is; it's that the proposal needs to be precise enough that somebody reading it can determine the correct behavior by reading the proposal. > "L. David Baron" <dbaron@dbaron.org> wrote on 2010/06/02 0:40:48 > > The editor's draft specification currently says only: > > # If both logical and physical properties are specified on the > > # same element, these corresponding properties are treated as same > > # property and then normal cascading rules are applied. > > This is ambiguous; it does not describe a mechanism for "treated as > > the same property", and therefore does not describe a single > > interoperable behavior for many cases. > > I'll change the wording to: ..., logical properties are converted to > physical properties ... That doesn't help. The specification needs to describe the model, as I said: > > In order to be clear about the complexity of the proposal, the > > specification should (1) describe how cascading is to be handled, > > probably by incorporating something like one of the proposals cited > > in http://lists.w3.org/Archives/Public/www-style/2010Jun/0003.html > > and (2) describe whether the longhand properties both proposals > > require are normal properties or are (as they are in Mozilla's > > implementation) a new class of hidden properties and (3) if the new > > properties are hidden, describe the effects of hidden properties on > > the CSS object model. -David -- L. David Baron http://dbaron.org/ Mozilla Corporation http://www.mozilla.com/
Received on Tuesday, 1 June 2010 20:37:56 UTC