Skip to content

Commit 6886214

Browse files
authored
Create transition-updated-cr-2017-09.md
1 parent 859d374 commit 6886214

1 file changed

Lines changed: 102 additions & 0 deletions

File tree

Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
(from [updated cr transitions](https://www.w3.org/Guide/transitions?profile=CR&cr=substantive) )
2+
3+
# Transition request for updated CR: Flexbox
4+
5+
## Document title, URIs, and estimated publication date
6+
7+
CSS Writing Modes Level 3
8+
9+
https://drafts.csswg.org/css-writing-modes-3/
10+
11+
First Tues or Thurs after a successful transition decision.
12+
13+
14+
## The document Abstract and Status sections
15+
16+
[abstract](https://drafts.csswg.org/css-writing-modes-3/#abstract)
17+
18+
[status (as ED)](https://drafts.csswg.org/css-writing-modes-3/#status)
19+
20+
## Link to previous transition
21+
22+
[09 Nov 2015](https://lists.w3.org/Archives/Member/chairs/2015OctDec/0097.html) (W3C Member only)
23+
24+
## Decision to request transition
25+
26+
RESOLVED: Add "size of nearest fixed scrollport" to the list of things you clamp orthogonal flow inline sizes to, editing the CR.
27+
28+
[minutes, 04 Aug 2017 telcon](https://github.com/w3c/csswg-drafts/issues/1391#issuecomment-320215251)
29+
30+
## Changes
31+
32+
* Three features were deferred to Level 4. These were all listed as "at-risk" in the Candidate Recommendation. A fourth feature was marked as "at-risk" but has been retained.
33+
* A Privacy and Security Considerations section was added, the contents of which say 'This specification introduces no new privacy leaks, or security considerations beyond "implement it correctly".' This is not a substantive change.
34+
* [Issue 1391](https://github.com/w3c/csswg-drafts/issues/1391) was a substantive change
35+
36+
[Changes since the December 2015 CR](https://drafts.csswg.org/css-writing-modes-3/#changes-201512)
37+
38+
## Requirements satisfied
39+
40+
(no formal requirements document)
41+
42+
This specification helps meet requirements listed in [Requirements for Japanese Text Layout](https://www.w3.org/TR/jlreq/)
43+
in particular section "2.3 Vertical Writing Mode and Horizontal Writing Mode".
44+
It also meets requirements listed in an (early ED of) [Text Layout Requirements for the Arabic Script](https://w3c.github.io/alreq/)
45+
in particular section "2.3 Direction".
46+
The number 2.3 has no numerological significance here.
47+
48+
## Dependencies met (or not)
49+
50+
The following normative references are not yet at CR:
51+
52+
* CSS Display Module Level 3
53+
* CSS Inline Layout Module Level 3
54+
* CSS Overflow Module Level 3
55+
* CSS Positioned Layout Module Level 3
56+
* CSS Ruby Layout Module Level 1
57+
* CSS Text Module Level 3
58+
* Cascading Style Sheets Level 2 Revision 2 (CSS 2.2) Specification
59+
* CSS Intrinsic & Extrinsic Sizing Module Level 3
60+
* CSS Paged Media Module Level 3
61+
62+
These are primarily to link to the latest definitions of each term.
63+
64+
## Wide Review
65+
66+
The specification has been reviewed in depth by the I18N Core Working group. Internationalization has published the
67+
following articles which explain how to use CSS Writing Modes 3.
68+
69+
* [Styling vertical Chinese, Japanese, Korean and Mongolian text](https://www.w3.org/International/articles/vertical-text/)
70+
* [CSS and International Text](https://www.w3.org/International/articles/css3-text/index)
71+
72+
## Issues addressed
73+
74+
The [Disposition of Comments](https://drafts.csswg.org/css-writing-modes-3/issues-cr-2015)
75+
76+
:boom: or is it this one [Disposition of Comments on GH](https://github.com/w3c/csswg-drafts/issues?utf8=%E2%9C%93&q=is%3Aissue%20label%3Acss-writing-modes-3%20)
77+
78+
Of the 23 issues raised, 12 were accepted. Three were rejected, and the commenter indicated they were satisfied.
79+
Three comments were invalid. One, calling for a Japanese translation of the specification to be linked, was
80+
rejected as out of scope (translations may be provided by third parties of W3C Recommendations, following the usual procedure).
81+
82+
## Formal Objections
83+
84+
None
85+
86+
## Implementation
87+
88+
The specification is [widely implemented](http://caniuse.com/#feat=css-writing-mode), although Safari on OSX and iOS
89+
still uses a -webkit- prefix. We would expect Apple to support the unprefixed property once Writing Modes progresses
90+
to W3C Recommendation.
91+
92+
The [testsuite](https://test.csswg.org/harness/results/css-writing-modes-3_dev/grouped/filter/1/) shows that
93+
985 of 1143 required tests meet CR exit criteria, and 8 of 17 optional tests meet CR exit criteria.
94+
95+
An [analysis of the test results](https://drafts.csswg.org/css-writing-modes-3/implementation-report.html) is also available
96+
97+
98+
:boom: the tests for features moved to Level 4 are still marked as level 3 tests, so need to be edited to make them Level 4 tests
99+
100+
## Patent disclosures
101+
102+
[none](https://www.w3.org/2004/01/pp-impl/32061/status)

0 commit comments

Comments
 (0)