- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Wed, 21 Jul 2010 00:17:01 -0700
- To: "www-style@w3.org" <www-style@w3.org>
Since I went through most of the spec pretty closely for issue 120, I noticed some other errors: Section 9.5 Floats # If there's a line box, the top of the floated box s/top/outer top/ Section 9.10 Text direction: the 'direction' and 'unicode-bidi' properties # The Unicode standard ([UNICODE], section 3.11) s/section 3.11/[UAX9]/ Section 10.4 Minimum and maximum widths: 'min-width' and 'max-width' # The CSS3 image-fit property s/image-fit/object-fit/ Section 16.1 Indentation: the 'text-indent' property # User agents should render this indentation as blank space. s/should/must/ Section 16.6.1 The 'white-space' processing model # Any text that is directly contained inside a block element (not # inside an inline element) should be treated as an anonymous inline # element. This sentence belongs in 9.2.2.1, which currently lacks normative text to this effect, and seems to be trying to define behavior by giving an example. Also, s/should/must/. Note also s/block/block container/ affects this from issue 120. # A float should not introduce a line break opportunity. # # Note. CSS 2.1 does not fully define where line breaking opportunities # occur. Floated and absolutely-positioned elements do not introduce a # line breaking opportunity. The first sentence should be deleted, as it is redundant with the third. The third should be removed from the note and placed above it to make it normative. Section 16.2 Alignment: the 'text-align' # the inline boxes are to be made flush with both sides of the block Clarify justification behavior by appending | if possible by expanding or contracting the contents of inline boxes, | else aligned as for the initial value. ? ~fantasai
Received on Wednesday, 21 July 2010 07:17:47 UTC