- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 04 Feb 2011 20:01:32 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-text In directory hutz:/tmp/cvs-serv9005 Modified Files: Overview.html Overview.src.html Log Message: Add notes to text-trim, explaining design and issues Index: Overview.html =================================================================== RCS file: /sources/public/csswg/css3-text/Overview.html,v retrieving revision 1.42 retrieving revision 1.43 diff -u -d -r1.42 -r1.43 --- Overview.html 30 Jan 2011 22:03:16 -0000 1.42 +++ Overview.html 4 Feb 2011 20:01:30 -0000 1.43 @@ -83,14 +83,14 @@ <h1>CSS Text Level 3</h1> - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 30 January + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 4 February 2011</h2> <dl> <dt>This version: <dd><a href="http://dev.w3.org/csswg/css3-text/Overview.html">$Date: - 2011/01/30 22:01:29 $ (CVS $Revision$)</a> <!--<dd><a + 2011/01/30 22:03:16 $ (CVS $Revision$)</a> <!--<dd><a href="http://www.w3.org/TR/2010/WD-css3-text-20101005/">http://www.w3.org/TR/2010/WD-css3-text-20101005/</a></dd> --> @@ -3295,8 +3295,10 @@ name=punctuation-trim></a> Fullwidth Kerning: the ‘<a href="#text-trim0"><code class=property>text-trim</code></a>’ property</h3> - <!-- Syntax is derived as a shorthand of the following theoretical - properties (defaults given first): + + <pre class=note> + Syntax is derived as a shorthand of the following theoretical + properties (defaults given first): text-trim-start: keep-start | force-start text-trim-end: allow-end | force-end | keep-end | keep-fullstop @@ -3311,7 +3313,7 @@ [ force-end | keep-end | keep-fullstop] || keep-adjacent || no-justify - --> + </pre> <table class=propdef> <tbody> @@ -3390,6 +3392,9 @@ rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>.</span> </dl> + <p class=issue>Figure out proper interaction with text-align: end. Does + allow-end behavior make sense? Do we want allow-start instead? + <p>In all cases, the UA must trim (kern) the blank half of fullwidth opening punctuation if its previous adjacent character is a fullwidth opening punctuation, fullwidth middle dot punctuation, fullwidth closing Index: Overview.src.html =================================================================== RCS file: /sources/public/csswg/css3-text/Overview.src.html,v retrieving revision 1.137 retrieving revision 1.138 diff -u -d -r1.137 -r1.138 --- Overview.src.html 30 Jan 2011 22:03:16 -0000 1.137 +++ Overview.src.html 4 Feb 2011 20:01:30 -0000 1.138 @@ -2438,8 +2438,9 @@ <h3 id="text-trim"><a name="punctuation-trim"></a> Fullwidth Kerning: the 'text-trim' property</h3> - <!-- Syntax is derived as a shorthand of the following theoretical - properties (defaults given first): + <pre class="note"> + Syntax is derived as a shorthand of the following theoretical + properties (defaults given first): text-trim-start: keep-start | force-start text-trim-end: allow-end | force-end | keep-end | keep-fullstop @@ -2454,7 +2455,7 @@ [ force-end | keep-end | keep-fullstop] || keep-adjacent || no-justify - --> + </pre> <table class="propdef"> <tbody> <tr> @@ -2523,6 +2524,9 @@ 3.8 Line Adjustment in [[JLREQ]].</span> </dd> </dl> + + <p class="issue">Figure out proper interaction with text-align: end. + Does allow-end behavior make sense? Do we want allow-start instead?</p> <p>In all cases, the UA must trim (kern) the blank half of fullwidth opening punctuation if its previous adjacent character is a
Received on Friday, 4 February 2011 20:01:34 UTC