-
Notifications
You must be signed in to change notification settings - Fork 16
/
Copy pathresults.html
279 lines (235 loc) · 9.45 KB
/
results.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
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<meta charset="utf-8" />
<meta name="color-scheme" content="light dark" />
<title>EPUB 3 Test Results</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
<style>
td a {
text-decoration: none !important;
}
td summary {
font-weight: normal;
}
td.pass {
background-color: hsl(120, 20%, 70%);
color: black !important
}
td.fail {
background-color: hsl(355, 100%, 72%);
color: black !important
}
td.untested {
background-color: hsl(60, 100%, 85%);
color: black !important
}
td.na {
background-color: hsl(30, 5%, 97%);
color: black !important
}
tr.under_implemented {
border: dashed 0.15em black ;
font-style: italic;
}
table.zebra {
font-size:inherit;
font:80%;
margin:1em;
}
table.zebra td {
padding-left: 0.3em;
}
table.zebra th {
font-weight: bold;
text-align: center;
background-color: rgb(0,0,128) !important;
font-size: 90%;
background: hsl(180, 30%, 50%);
color: #fff;
}
table.zebra th a:link {
color: #fff;
}
table.zebra th a:visited {
color: #aaa;
}
table.zebra tr:nth-child(even) {
background-color: hsl(180, 30%, 93%) !important;
color: black !important;
}
table.zebra th {
border-bottom:1px solid #bbb;
padding:.2em 1em;
}
table.zebra td {
border-bottom:1px solid #ddd;
padding:.2em 1em;
}
body.darkmode table.zebra tr:nth-child(odd) {
color: black !important;
background-color: hsl(241, 0%, 78%) !important;
}
body.darkmode table.zebra tr:nth-child(odd) {
background-color: hsl(241, 0%, 30%) !important;
}
body.darkmode table.zebra tr:nth-child(even) td a:link,
body.darkmode table.zebra tr:nth-child(even) td a:visited
{
color: green;
}
body.darkmode table.zebra tr:nth-child(odd) td a:link,
body.darkmode table.zebra tr:nth-child(odd) td a:visited
{
color: navy;
}
div#button_container {
display: flex;
justify-content: center;
align-items: center;
}
button#should_may_visibility {
cursor: pointer;
font-size: 110%;
font-style: italic;
text-align: center;
border-radius: 10px;
background-color: #005a9c;
color: white;
}
button#should_may_visibility span {
font-size: 90%;
}
</style>
<script class="remove">
var respecConfig = {
wgPublicList: "public-pm-wg",
latestVersion: "https://w3c.github.io/epub-tests/results",
specStatus: "base",
noRecTrack: true,
shortName: "epub-tests-results",
edDraftURI: "https://w3c.github.io/epub-tests/results",
copyrightStart: "2021",
editors:[
{
name: "Ivan Herman",
url: "https://www.w3.org/People/Ivan/",
company: "W3C",
w3cid: 7382,
orcid: "0000-0003-0782-2704",
companyURL: "https://www.w3.org",
},
{
name: "Dan Lazin",
company: "Google LLC",
w3cid: 130027,
companyURL: "https://www.google.com",
}
],
includePermalinks: true,
permalinkEdge: true,
permalinkHide: false,
github: {
repoURL: "https://github.com/w3c/epub-tests",
branch: "main"
}
};
</script>
<script>
// The current visibility state is stored in a local storage
// This means that the requested visibility is kept (in the same browser) and
// is valid across the two report files.
const HIDE = "true";
const SHOW = "false";
const STORAGE_KEY = 'hide_should_may_tests';
function row_visibility(current_state) {
// Modify the inline text to reflect the visibility status
const span = document.getElementById("test_visibility");
span.textContent = current_state === HIDE ? "hidden" : "visible";
const change_button = document.getElementById('should_may_visibility');
change_button.innerHTML = current_state === HIDE ?
"Currently showing the results for <span>MUST</span> tests only; click here to show all test results" :
"Currently showing all test results; click here to show the results for <span>MUST</span> tests only";
// Collect all relevant `<section>` elements...
const section_all = document.querySelectorAll("section.optional_feature");
// ... and change the visibility
for (const section of section_all) {
section.hidden = (current_state === HIDE);
const selector = `a[href="#sec-consolidated-${section.id}-results"]`
const toc_a = document.querySelector(selector);
toc_a.parentNode.hidden = (current_state === HIDE);
}
// Collect all relevant `<tr>` elements...
const tr_all = document.querySelectorAll("td.should, td.may");
// ... and change the visibility
for (const td of tr_all) {
td.parentNode.hidden = (current_state === HIDE);
}
}
// Button clicked: change the status and regenerate the relevant tables
function clicked() {
let current_state = localStorage.getItem(STORAGE_KEY) === HIDE ? SHOW : HIDE;
localStorage.setItem(STORAGE_KEY, current_state);
row_visibility(current_state);
}
window.addEventListener('load', () => {
// This is the initial setup
// At first run the visibility is not yet set, so it must be set to a default.
let current_state = localStorage.getItem(STORAGE_KEY);
if (current_state === null) {
localStorage.setItem(STORAGE_KEY, SHOW);
current_state = SHOW;
}
row_visibility(current_state);
const change_button = document.getElementById('should_may_visibility');
change_button.addEventListener('click', clicked);
});
</script>
</head>
<body>
<section id="abstract">
<p>This documents shows the results of EPUB 3.4 Testing.
It corresponds to the <a href="https://w3c.github.io/epub-specs/epub34/authoring/">EPUB 3.4</a> specification's
<a href="https://w3c.github.io/epub-specs/epub34/reports/exit_criteria#exit-criteria-core-1">category 1 exit criteria</a>,
as well as the complete <a href="https://w3c.github.io/epub-specs/epub34/reports/exit_criteria#exit-criteria-rs">exit criteria</a>
for the <a href="https://w3c.github.io/epub-specs/epub34/rs/">EPUB 3.4 Reading Systems</a> specification.
</p>
</section>
<section id="sotd"></section>
<section id="conformance"></section>
<section>
<h2>Introduction</h2>
<p>
This document contains the test results for all tests. There is a <a href="index.html">separate document</a> which provides a short description for each test; these descriptions are derived from the tests in the tables below.
</p>
<p>
In the EPUB community, implementors may develop one or more EPUB Reading System rendering engines which are then used in multiple applications across different platforms (ex. iOS, Android, or Web). To accurately reflect this in our tests, we have "variants", which allow the implementors to report results based on both the core engine and the platforms they support using that engine. From a <abbr title="World Wide Web Consortium">W3C</abbr> Process point of view, these variants should not be considered independent implementations. We are reporting the results of the different variants for the benefit of implementors and the EPUB community, who may find it beneficial to know how implementations support EPUB features across platforms.
</p>
<p>
The report tables in sections 3 and 4 reflect this implementation process.<a href="#sec-consolidated-report-tables"></a> shows a view of the reports where reports with identical core engines are consolidated into a single implementation. The test results for a specific test is set to <code>pass</code> if <em>any</em> of the variants has a <code>pass</code> value. The separate <a href="#sec-detailed-report-tables"></a> shows the full implementation results for each implementation.
</p>
<p>
<a href="#sec-implementer-list"></a> lists all the implementations and their variants. The variant will appear after the implementation name, and may include a version number for the software tested and what browser or platform it was tested on.
</p>
<p>
The report tables also include a separate column (with the heading "Req") providing the conformance level for the feature being tested (i.e., <code>must</code>, <code>should</code>, or <code>may</code>).
</p>
<p>
The <code>should</code> and <code>may</code> tests are not necessary for the official CR testing of
the specifications. Implementors and the EPUB community may find these results useful, which is why they were gathered.
These tests are currently <span id="test_visibility">visible</span> in the tables; to change their visibility, click the
switch visibility button below.
</p>
<p>
The development of the tests is a community effort (see the <a href="./index.html#contributors">list of contributors</a>). Everyone is welcome to
contribute tests; please read the separate <a href="./contributing">contribution guidelines</a> if you are interested in doing so.
</p>
</section>
<section data-include='generate/fragments/implementations.html' data-include-replace='true'></section>
<div id="button_container">
<button id="should_may_visibility" type="button">switch visibility</button>
</div>
<section data-include='generate/fragments/consolidated_results.html' data-include-replace='true'></section>
<section data-include='generate/fragments/complete_results.html' data-include-replace='true'></section>
</body>
</html>