Skip to content

Commit ff6cf36

Browse files
committed
[css2] Added note about writing direction and constraints (was a comment)
--HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%401170
1 parent 6797840 commit ff6cf36

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

css2/changes.src

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
22
<html lang="en">
3-
<!-- $Id: changes.src,v 2.7 1998-03-13 01:00:02 ijacobs Exp $ -->
3+
<!-- $Id: changes.src,v 2.8 1998-03-14 23:30:35 ijacobs Exp $ -->
44
<HEAD>
55
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
66
<TITLE>Appendix B: Changes from CSS1</TITLE>
@@ -74,7 +74,7 @@ semantics.
7474
</UL>
7575
-->
7676

77-
<H2>Changes</H2>
77+
<H2>Semantic changes from CSS1</H2>
7878

7979
<!-- I think this section should be normative, and thus
8080
somewhere else. E.g., conform.src. -IJ -->
@@ -85,16 +85,16 @@ somewhere else. E.g., conform.src. -IJ -->
8585
with regard to the device gamut, not with regard to the sRGB gamut as
8686
in CSS1.
8787

88-
<LI>[strength of constraints based on writing direction]
89-
90-
<!-- Don't forget -IJ -->
88+
<LI>CSS1 simply said that 'margin-right' was ignored if the both
89+
'margin-left' and 'width' were set. In CSS2 the choice between
90+
relaxing 'margin-right' or 'margin-left' depends on the writing direction.
9191

9292
<LI>In CSS1, several properties (e.g., 'padding') had values referring
9393
to the width of the parent element. This was an error; the value
9494
should always refer to the width of a block-level element and this
9595
specification reflects this by introducing the term "containing block".
9696

97-
<LI>Initial value of 'display' is 'inline', not 'block' as in CSS1.
97+
<LI>Initial value of 'display' is 'inline', not 'block'.
9898

9999
<LI>The 'clear' property now only applies to block-level elements.
100100

0 commit comments

Comments
 (0)