-
Notifications
You must be signed in to change notification settings - Fork 708
/
Copy pathissues-fpwd-2015.html
162 lines (155 loc) · 9.38 KB
/
issues-fpwd-2015.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
<!DOCTYPE html>
<meta charset="utf-8">
<title>CSS Basic User Interface Module Level 4 Disposition of Comments for 2015-09-22 WD</title>
<style>
.a { background: lightgreen }
.d { background: lightblue }
.r { background: orange }
.fo { background: red }
.open { border: solid red; padding: 0.2em; }
:target { box-shadow: 0.25em 0.25em 0.25em; }
</style>
<h1>CSS Basic User Interface Module Level 4 Disposition of Comments for 2015-09-22 WD</h1>
<p>Review document: <a href="https://www.w3.org/TR/2015/WD-css-ui-4-20150922/">https://www.w3.org/TR/2015/WD-css-ui-4-20150922/</a>
<p>Editor's draft: <a href="http://dev.w3.org/csswg/css-ui-4/">http://dev.w3.org/csswg/css-ui-4/</a>
<p>The following color coding convention is used for comments:</p>
<ul>
<li class="a">Accepted or Rejected and positive response
<li class="r">Rejected and no response
<li class="fo">Rejected and negative response
<li class="d">Deferred
<li class="oi">Out-of-Scope or Invalid and not verified
</ul>
<p class=open>Open issues are marked like this</p>
<p>An issue can be closed as <code>Accepted</code>, <code>OutOfScope</code>,
<code>Invalid</code>, <code>Rejected</code>, or <code>Retracted</code>.
<code>Verified</code> indicates commentor's acceptance of the response.</p>
<pre class=' open' id='issue-1'>
Issue 1. <a href='#issue-1'>#</a>
Summary: 'appearance' is not web compatible
From: Mats Palmgren
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1250'>https://github.com/w3c/csswg-drafts/issues/1250</a>
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1250#issuecomment-301033093'>https://github.com/w3c/csswg-drafts/issues/1250#issuecomment-301033093</a>
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1250#issuecomment-306788821'>https://github.com/w3c/csswg-drafts/issues/1250#issuecomment-306788821</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1250#issuecomment-320003220'>https://github.com/w3c/csswg-drafts/issues/1250#issuecomment-320003220</a>
Open</pre>
<pre class='a' id='issue-2'>
Issue 2. <a href='#issue-2'>#</a>
Summary: Spatial Navigation needs a new home in WICG
From: Tantek Çelik
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1948'>https://github.com/w3c/csswg-drafts/issues/1948</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1948#issuecomment-343587403'>https://github.com/w3c/csswg-drafts/issues/1948#issuecomment-343587403</a>
Closed: Accepted
Resolved: <a href='https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696'>https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696</a></pre>
<pre class='d' id='issue-3'>
Issue 3. <a href='#issue-3'>#</a>
Summary: Please add "tab-index" to CSS specification
From: Nadya678
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1748'>https://github.com/w3c/csswg-drafts/issues/1748</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1748#issuecomment-344493880'>https://github.com/w3c/csswg-drafts/issues/1748#issuecomment-344493880</a>
Closed: Deferred
Resolved: <a href='https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696'>https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696</a></pre>
<pre class='d' id='issue-4'>
Issue 4. <a href='#issue-4'>#</a>
Summary: Arrow-index property
From: Brad Kemper
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1762'>https://github.com/w3c/csswg-drafts/issues/1762</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1762#issuecomment-344504643'>https://github.com/w3c/csswg-drafts/issues/1762#issuecomment-344504643</a>
Closed: Deferred
Resolved: <a href='https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696'>https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696</a></pre>
<pre class='d' id='issue-5'>
Issue 5. <a href='#issue-5'>#</a>
Summary: Add a property controlling the navigation order
From: Sebastian Zartner
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1764'>https://github.com/w3c/csswg-drafts/issues/1764</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1764#issuecomment-344493895'>https://github.com/w3c/csswg-drafts/issues/1764#issuecomment-344493895</a>
Closed: Deferred
Resolved: <a href='https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696'>https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696</a></pre>
<pre class='d' id='issue-6'>
Issue 6. <a href='#issue-6'>#</a>
Summary: Scoping navigation/focus subtrees
From: James Craig
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1949'>https://github.com/w3c/csswg-drafts/issues/1949</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1949#issuecomment-344495152'>https://github.com/w3c/csswg-drafts/issues/1949#issuecomment-344495152</a>
Closed: Deferred
Resolved: <a href='https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696'>https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696</a></pre>
<pre class='a' id='issue-7'>
Issue 7. <a href='#issue-7'>#</a>
Summary: none value for nav-up, nav-right, nav-down, nav-left properties
From: Jihye Hong
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1822'>https://github.com/w3c/csswg-drafts/issues/1822</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1822#issuecomment-330418767'>https://github.com/w3c/csswg-drafts/issues/1822#issuecomment-330418767</a>
Closed: Rejected
Resolved: Editors' discretion
Verified: <a href='https://github.com/w3c/csswg-drafts/issues/1822#issuecomment-330713355'>https://github.com/w3c/csswg-drafts/issues/1822#issuecomment-330713355</a></pre>
<pre class='a' id='issue-8'>
Issue 8. <a href='#issue-8'>#</a>
Summary: Activating spatial navigation
From: Florian Rivoal
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1940'>https://github.com/w3c/csswg-drafts/issues/1940</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1940#issuecomment-344522185'>https://github.com/w3c/csswg-drafts/issues/1940#issuecomment-344522185</a>
Closed: Deferred
Resolved: <a href='https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696'>https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907696</a>
Verified: <a href='https://github.com/w3c/csswg-drafts/issues/1940#issuecomment-344522185'>https://github.com/w3c/csswg-drafts/issues/1940#issuecomment-344522185</a></pre>
<pre class='a' id='issue-9'>
Issue 9. <a href='#issue-9'>#</a>
Summary: Spec is hard to understand with regards to bidi and ellipsis
From: Koji Ishii
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/2125'>https://github.com/w3c/csswg-drafts/issues/2125</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/2125#issuecomment-356971335'>https://github.com/w3c/csswg-drafts/issues/2125#issuecomment-356971335</a>
Closed: Accepted
Resolved: Editorial</pre>
<pre class='a' id='issue-10'>
Issue 10. <a href='#issue-10'>#</a>
Summary: Rendering of <input> is weird and undefined
From: isangelawu
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1941'>https://github.com/w3c/csswg-drafts/issues/1941</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1941#issuecomment-345380779'>https://github.com/w3c/csswg-drafts/issues/1941#issuecomment-345380779</a>
Closed: Accepted
Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/1941#issuecomment-356685574'>https://github.com/w3c/csswg-drafts/issues/1941#issuecomment-356685574</a></pre>
<pre class='a' id='issue-11'>
Issue 11. <a href='#issue-11'>#</a>
Summary: Grammar of outline-style poorly defined
From: Louis Lazaris
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/2466'>https://github.com/w3c/csswg-drafts/issues/2466</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/2466#issuecomment-376016337'>https://github.com/w3c/csswg-drafts/issues/2466#issuecomment-376016337</a>
Closed: Accepted
Resolved: Editorial</pre>
<pre class=' open' id='issue-12'>
Issue 12. <a href='#issue-12'>#</a>
Summary: let user-select:contain prohibit selection from outside
From: Yoichi Osato
Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1815'>https://github.com/w3c/csswg-drafts/issues/1815</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/1815#issuecomment-329681869'>https://github.com/w3c/csswg-drafts/issues/1815#issuecomment-329681869</a>
Open</pre>
<script>
(function () {
var sheet = document.styleSheets[0];
function addCheckbox(className) {
var element = document.querySelector('*.' + className);
var label = document.createElement('label');
label.innerHTML = element.innerHTML;
element.innerHTML = null;
var check = document.createElement('input');
check.type = 'checkbox';
if (className == 'open') {
check.checked = false;
sheet.insertRule('pre:not(.open)' + '{}', sheet.cssRules.length);
check.onchange = function (e) {
rule.style.display = this.checked ? 'none' : 'block';
}
}
else {
check.checked = true;
sheet.insertRule('pre.' + className + '{}', sheet.cssRules.length);
check.onchange = function (e) {
rule.style.display = this.checked ? 'block' : 'none';
}
}
var rule = sheet.cssRules[sheet.cssRules.length - 1];
element.appendChild(label);
label.insertBefore(check, label.firstChild);
}
['a', 'd', 'fo', 'oi', 'r', 'open'].forEach(addCheckbox);
}());
</script>