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 03:12:46 -0400
To: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E09E910C6CD@MAILR001.mail.lan>

Okay, maybe I took an wrong example.

You can take writing-mode property. You can also take margin-before property. They change the layout drastically on new browsers, right?

This is a repeat, but what I think is important for compatibility are:

* Do not break existing documents at all.
* Renders reasonably, at least readable, in down level browsers.

I think this proposal achieves the same level of these goals as other properties that are proposed.

Can you please explain how you think margins-against could differ from writing-mode in regards to the compatibility? I'd love to fix or change my proposal if there's something I missed.

Koji Ishii

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

> * 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 

I think that such a difference between CSS 2.1 and CSS 3.0 is too drastic and unacceptable.

Makoto  <EB2M-MRT@asahi-net.or.jp>
Received on Thursday, 17 June 2010 07:13:21 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:13:47 UTC