CSS WG Blog Minutes and Resolutions Oslo F2F Monday 20…

Minutes and Resolutions Oslo F2F Monday 2010-08-23: CSS2.1, CSSWG Charter, Viewport Sizing

CSS2.1 Issues

• Resolved: Bert’s proposal accepted for CSS2.1 Issue 129
• Resolved: Leave issue CSS2.1 Issue 144 officially undefined, add a note that it will be resolved in CSS3.
• Resolved: Proposal accepted for CSS2.1 Issue 172: caption width influences table width as if contained in a table-spanning cell. fantasai to tweak proposal as noted in minutes to be more clear.
• Resolved: For CSS2.1 Issue 183 change “@media and @import rules with unknown media types are treated as if the unknown media types are not present.” to “@media and @import rules with unknown media types (that are nonetheless valid identifiers) are treated as if the unknown media types are not present. If an @media rule contains a malformed media type (not an identifier) then the statement is invalid.” and add “Note: Media Queries supercedes this error handling.”
• Discussed CSS2.1 Issue 187 (bidi effects of atomic inline-level elements): agreed in principal with proposal but need clearer wording. [see Tuesday minutes].
• Resolved: Add a note about marker box stacking level for outside markers being undefined in CSS2.1 for CSS2.1 Issue 191.
• Resolved: For CSS2.1 Issue 192, accept change for first issue, replace “further content” with “content after the float” and “it” with “that content” for the second issue, third issue is invalid.
• Resolved: Proposal accepted for CSS2.1 Issue 194
• Resolved: For CSS2.1 Issue 195, proposal accepted with “even if either side is empty” appended. [see Tuesday minutes]
• Resolved: For CSS2.1 Issue 196, fix range of identifiers to include NBSP and exclude the control characters immediately below it.
• Resolved: For CSS2.1 Issue 197, edit spec to be clearer that when clear is applied to a run-in, it applies to the run-in itself if it displays as a block, and it applies to the block the run-in runs into if it displays as an inline.
• Resolved: For CSS2.1 Issue 198, clarify spec to say that run-in effectively causes a reordering of the source tree insofar as the formatting model is concerned, and the contents of the run-in are moved along with it. (This does not affect e.g. selectors, etc.)
• Resolved: Proposal accepted forCSS2.1 Issue 201 with “table wrapper box” as the term for the outer table box.
• Resolved: CSS2.1 Issues list is FROZEN in preparation for publication of a Last Call Working Draft.
• Resolved: CSS2.1 to progress from Last Call directly to Proposed Recommendation if it meets exit criteria.

CSS2.1 Test Suite

Discussed Release Candidate criteria, what happens to tests that are wrong, making implementation reports, and how we are measuring test coverage of the spec.

Test suite RC scheduled for September 15th; test errors must be fixed before RC. Implementation reports due 1 month after RC publication.

CSSWG Charter

• See also: current charter and its planning document.
• Reviewed contents of old charter, since we plan to copy most of it over.
• Reviewed current and expected status of modules, who is planning to work
  on what, and what priority they should have within the WG.
• Resolved: Move css3-marquee and css-mobile to low priority, send OMA liaison about this asking if they want to work on it.

First cut of 2010 module priorities (may be shuffled around later)

High Priority → Maintenance

• CSS2.1
• CSS Color Level 3
• CSS Namespaces
• CSS Styling Attributes
• Selectors Level 3

High priority

• CSS Snapshots
• CSS Backgrounds and Borders Level 3
• CSS UI Level 3
• CSS Fonts Level 3
• CSS Image Values Level 3
• CSS Multi-column Layout
• CSS 2D Transforms
• CSS Transitions
• CSS Values and Units
• Media Queries

Medium Priority

• CSS Box Model Level 3
• CSS Device Adaptation (@viewport proposal)
• CSS Flexbox
• CSS GCPM
• CSS Lists
• CSS Paged Media Level 3
• CSS Ruby
• CSS Template Layout
• CSS Text Level 3
• CSS Transforms 3D
• CSS Writing Modes Level 3 (vertical text)
• CSS Variables
• CSSOM
• CSSOM View

Low priority

• CSS Backgrounds and Borders Level 4
• CSS Filter Effects (applying SVG filters to CSS layouts)
• CSS Grid Positioning
• CSS Line Layout
• CSS Scoped Style Sheets
• CSS UI Level 4
• CSS Tables Level 3
• Selectors Level 4

Not Yet Prioritized

• Media Queries 3 Revision 1 (adding OM and serialization definitions)
• Selectors Level 3 Revision 1 (adding OM and serialization definitions)

Viewport Meta and CSS Syntax

Reviewed Rune’s proposal for an @viewport rule to set the size of the inital containing block independently of the viewport itself.

Comments included

• Pages designed to accommodate varying device sizes are often broken by the behavior in the viewport meta proposal.
• Many use cases can be solved by using max-width/height on the root element to determine an appropriate viewport size, so UAs should try to use that instead. However, this technique has trouble with fixed positioning.
• Interaction with Media Queries must be defined, perhaps similar to @page { size: ... }
• @viewport has ways of indicating a preferred fixed size, but does not allow a range of valid sizes from which the UA could choose the most appropriate for its device.
• A guiding principle would be to specify only those things that would break web content if a UA decides to do it differently. This avoids overspecifying things that should be within the UA’s jurisdiction.

Resolved: CSS Device Adaptation added to charter at medium priority, Rune to edit along with someone from Apple.

Full Minutes Monday

« Previous article Next article »