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

RE: [css3-text-layout] New editor's draft - margin-before/after/start/end ?etc.

From: Ishii Koji <kojiishi@gluesoft.co.jp>
Date: Thu, 17 Jun 2010 02:26:35 -0400
To: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E09E910C6CB@MAILR001.mail.lan>
Thank you for your prompt reply and giving deep thoughts to my proposal.

I still don't understand why you call it "logical". It looks different thing to me if I understand the logical properties correctly. This is closer to what Transform does as I wrote, I think. But it doesn't matter how you call it, does it.

Regarding the compatibilities. New properties always face the compatibility problem, and I understand it's a very important issue.

As far as I understand, by adding this property:

* Existing document will not be corrupt or rendered differently, as the default behavior is unchanged.

* Documents with this property set to "line" will be rendered differently from author's intention on old browsers. You're right about this. But I understand this is the nature of the new features. CSS2 documents viewed by IE3/NS4 wouldn't be rendered as author intended, but that was okay because the document is still readable, and renders better on new browsers. All properties we're talking about for CSS3 text layout have the same nature, right. You can't expect IE3/NS4 to render them correctly. You can read contents, but layouts wouldn't be correct. I think this proposal achieves the same level of the compatibility as these new features.

Am I missing something?

Koji Ishii

-----Original Message-----
From: eb2mmrt@gmail.com [mailto:eb2mmrt@gmail.com] On Behalf Of MURATA Makoto
Sent: Thursday, June 17, 2010 2:40 PM
To: Ishii Koji
Cc: www-style@w3.org
Subject: Re: [css3-text-layout] New editor's draft - margin-before/after/start/end etc.

I now understand your proposal.  You are proposing to make existing properties logical only when a new property 'margins-against'
with the value "line" is specified.

Probably the biggest problem in your approach is existing implementations, which are unaware of this new attribute.  They behave completely differently from new implementations that are aware of this new attribute.  I am afraid that this problem is fatal.

Received on Thursday, 17 June 2010 06:27:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:47 UTC