forked from coremob/level-1
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
312 lines (289 loc) · 13.5 KB
/
index.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
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
<!DOCTYPE html>
<html xmlns='http://www.w3.org/1999/xhtml' lang='en'>
<head>
<meta charset='utf-8'/>
<title>Core Mobile Web Platform — 2012</title>
<script class='remove'>
var respecConfig = {
specStatus: "CG-DRAFT"
, shortName: "coremob-2012"
, editors: [
{ name: "Tobie Langel"
, company: "Facebook"
, companyURL: "http://facebook.com/" }
, { name: "Robin Berjon"
, url: "http://berjon.com/"
, company: "Robineko"
, companyURL: "http://robineko.com/" }
]
, edDraftURI: "http://coremob.github.com/level-1/index.html"
, copyrightStart: 2012
, noIDLIn: true
, wg: "Core Mobile Web Platform Community Group"
, wgURI: "http://www.w3.org/community/coremob/"
, wgPublicList: "public-coremob"
, wgPatentURI: "XXX"
, isRecTrack: false
, isNoTrack: true
};
</script>
<script src='http://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
</head>
<body>
<section id='abstract'>
<p>
This specification describes the core set of technologies that define the baseline platform
for mobile Web applications to target. It does not create any new technology but rather syndicates
them into a globally coherent view of the mobile Web platform.
</p>
</section>
<section id='sotd'>
<p>Notes are non-normative.</p>
<p>
Development of this document happens on <a href='https://github.com/coremob/level-1'>GitHub</a>.
Please file well-scoped <a href='https://github.com/coremob/level-1/issues'>issues</a> and send
<a href='https://github.com/coremob/level-1/pulls'>pull requests</a> directly on GitHub. Please
send comments to the mailing list.
</p>
</section>
<section class='informative'>
<h2>Introduction</h2>
<p>
The goal of the Core Mobile Web Platform Community Group is to accelerate the adoption of the Mobile Web as a compelling platform for the development of modern mobile Web applications. In order to achieve this mission, the CG brings developers, equipment manufacturers, browser vendors, operators and other relevant members of the industry together to agree on core features developers can depend on.</p>
<p>This specification is the result of this work. It attempts to carefully balances developer needs and implementation constraints as of today. Updated versions of this document will be released as the platform evolves and new technologies become broadly available.
</p>
</section>
<section>
<h2>Markup</h2>
<p>This section describes requirements for markup languages and related features.</p>
<section>
<h2>HTML5</h2>
<p>User agents MUST support HTML5 [[!HTML5]].</p>
<p class='issue' data-number=1>Some <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=14702">critical AppCache issues</a> are being <a href="http://html5.org/tools/web-apps-tracker?from=7135&to=7136">fixed</a> in the HTML Living Standard spec. Unfortunately, these fixes aren't brought (yet) to the HTML5 spec because they are considered new features belonging in HTML.next. What should the group's position be with regards to that?</p>
<p class='note'>Implementors should pay particular attention to the quality of implementation of the <code>audio</code> element. <code>audio</code> elements are commonly used in games to play background music and sound effects. It is recommended that implementations support playing 8 audio files in parallel without audible artifacts and provide sub 10ms latency.</p>
<p class='issue' data-number=2>Can the latency requirements be lightened a bit. Sub 10ms seems ideal, slightly longer latency times may be acceptable for most use cases.</p>
</section>
<section>
<h2>HTML Media Capture</h2>
<p>User agents MUST support HTML Media Capture [[!HTMLMEDIACAPTURE]].</p>
</section>
<section>
<h2>SVG</h2>
<p>User agents MUST support Scalable Vector Graphics (SVG) 1.1 (Second Edition) [[!SVG11]].</p>
</section>
<section>
<h2><code>meta</code> Elements</h2>
<p>User agents MUST support CSS Device Adaptation [[!CSS-ADAPTATION]] as specified through a <code>meta</code> viewport element.</p>
</section>
<section>
<h2>Application Configuration</h2>
<p class='issue' data-number=6>WebApps WG is <a href="http://www.w3.org/2012/webapps/charter/Overview.html#deliverables">chartered</a> to work on this and has two related specs: Widget Packaging and Configuration [[WIDGETS]] (which has had little traction among the main vendors), and Web Application Manifest Format and Management APIs [[WEBAPPS-MANIFEST-API]] (which is still an early Editor's draft).</p>
</section>
<section>
<h2>View Orientation</h2>
<p class='issue' data-number=7>This is a new deliverable of the WebApps WG. See the WG's <a href='http://www.w3.org/2012/webapps/charter/'>charter</a> for details. No spec to link to for the moment. Could also end up as an attribute of <a href="#application-configuration">Application Configuration</a>.</p>
</section>
<section>
<h2>Chromeless Mode</h2>
<p class='issue' data-number=8>Within the scope of the WebApps WG's <a href='http://www.w3.org/2012/webapps/charter/'>charter</a>. Could end up as an attribute of <a href="#application-configuration">Application Configuration</a>.</p>
</section>
</section>
<section>
<h2>Style</h2>
<p>This section defines requirements for CSS and other, styling-related features.</p>
<section>
<h2>CSS 2.1</h2>
<p>User agents MUST support CSS 2.1 [[!CSS21]].</p>
</section>
<section>
<h2>Processing</h2>
<section>
<h2>Values</h2>
<p>User agents MUST support CSS Values [[!CSS3VAL]].</p>
<p class='issue' data-number=9>CSS Values is a WD. Most of the common content of CSS Values is already included in CSS 2.1. There are some features that would be welcomed additions, notably <code>calc()</code>, <code>rem</code> unit, but also some that don't seem to have a lot of traction (e.g. <code>cycle()</code>).</p>
</section>
<section>
<h2>Media Queries</h2>
<p>User agents MUST support CSS Media Queries [[!CSS3-MEDIAQUERIES]].</p>
</section>
<section>
<h2>Selectors</h2>
<p>User agents MUST support CSS Selectors Level 3 [[!SELECTORS]].</p>
</section>
<p class='issue' data-number=11>Request for momentum scrolling (e.g. <code>-webkit-overflow-scrolling: touch</code>) are extremely common. Unfortunately, there is no spec effort at this point.</p>
</section>
<section>
<h2>Graphical</h2>
<section>
<h2>Backgrounds and Borders</h2>
<p>User agents MUST support CSS Backgrounds and Borders [[!CSS3-BG]].</p>
</section>
<section>
<h2>Color</h2>
<p>User agents MUST support CSS Color [[!CSS3COLOR]].</p>
</section>
<section>
<h2>Image Values and Replaced Content</h2>
<p>User agents MUST support CSS Image Values and Replaced Content [[!CSS3-IMAGES]].</p>
<p class='issue' data-number=10>CSS Image Values is a CR. Questionable content is marked at risk, which is reassuring.</p>
</section>
</section>
<section>
<h2>Layout</h2>
<section>
<h2>Flexbox</h2>
<p>User agents MUST support CSS Flexible Box Layout [[!FLEXBOX]].</p>
</section>
<section>
<h2>Transforms</h2>
<p>User agents MUST support CSS Transforms [[!CSS3-TRANSFORMS]].</p>
</section>
</section>
<section>
<h2>Typography</h2>
<section>
<h2>CSS Fonts</h2>
<p>User agents MUST support CSS Fonts [[!CSS3-FONTS]].</p>
</section>
<section>
<h2>WOFF</h2>
<p>User agents MUST support <acronym title="Web Open Font Format">WOFF</acronym> [[!WOFF]].</p>
</section>
<section>
<h2>CSS Text</h2>
<p>User agents MUST support CSS Text [[!CSS3TEXT]].</p>
<p class='issue' data-number=13>Spec in WD. We're interested in a small subset of CSS Text, mainly text-shadow. Like CSS Values, a lot what is of interest is already covered by CSS 2.1.</p>
</section>
</section>
<section>
<h2>Animations and Transitions</h2>
<section>
<h2>Animations</h2>
<p>User agents MUST support CSS Animations [[!CSS3-ANIMATIONS]].</p>
</section>
<section>
<h2>Transitions</h2>
<p>User agents MUST support CSS Transitions [[!CSS3-TRANSITIONS]].</p>
</section>
</section>
</section>
<section>
<h2>Scripting</h2>
<p>This section defines which scripting support in language and APIs are required.</p>
<section>
<h2>ECMAScript</h2>
<p>User agents MUST support ECMAScript, Edition 5.1 [[!ECMA-262-51]].</p>
</section>
<section>
<h2>DOM</h2>
<section>
<h2>DOM4</h2>
<p>User agents MUST support the DOM4 API [[!DOM4]].</p>
</section>
<section>
<h2>Selectors</h2>
<p>User agents MUST support the Selectors API level 2 [[!SELECTORS-API2]].</p>
</section>
<section>
<h2>Touch Events</h2>
<p>User agents SHOULD support Touch Events version 1 [[!TOUCH-EVENTS]].</p>
</section>
<section>
<h2>CSSOM View</h2>
<p>User agents MUST support CSSOM View [[!CSSOM-VIEW]].</p>
</section>
</section>
<section>
<h2>Storage</h2>
<section>
<h2>Web Storage</h2>
<p>User agents MUST support the Web Storage API [[!WEBSTORAGE]].</p>
</section>
<section>
<h2>Indexed Database</h2>
<p>User agents MUST support the Indexed Database API [[!INDEXEDDB]].</p>
</section>
<section>
<h2>File</h2>
<p>User agents MUST support the File API [[!FILE-API]].</p>
</section>
<section>
<h2>Quota Management</h2>
<p>User agents MUST support the Quota Management API [[!QUOTA-API]].</p>
</section>
</section>
<section>
<h2>Networking</h2>
<section>
<h2>XMLHttpRequest</h2>
<p>User agents MUST support the XMLHttpRequest API [[!XMLHTTPREQUEST]].</p>
<p class='issue' data-number=14>The Editor folded level 1 and 2 in the same spec recently, but this isn't reflected in /TR yet.</p>
</section>
<section>
<h2>Web Messaging</h2>
<p>User agents MUST support the Web Messaging API [[!POSTMSG]].</p>
</section>
<section>
<h2>Web Workers</h2>
<p>User agents MUST support the Web Workers API [[!WEBWORKERS]].</p>
<p class='issue' data-number=15>Do we need both Shared and Web Workers?</p>
</section>
</section>
<section>
<h2>Sensors</h2>
<section>
<h2>Geolocation</h2>
<p>User agents MUST support the Geolocation API [[!GEOLOCATION-API]].</p>
</section>
<section>
<h2>DeviceOrientation Event</h2>
<p>User agents MUST support the DeviceOrientation Event [[!DEVICE-ORIENTATION]].</p>
</section>
</section>
<section>
<h2>Multimedia</h2>
<section>
<h2>Canvas2D</h2>
<p>User agents MUST support the Canvas2D API [[!CANVAS-2D]].</p>
<p class='note'>Implementors should pay attention to the performance characteristics of the <code>canvas</code> element which is particularly well suited for the development of 2D and isometric games. In order to meet the expectations of users, implementations should be capable of running such games at 30fps in full-screen mode.</p>
</section>
<section>
<h2>Timing control for script-based animations</h2>
<p>User agents MUST support the Timing control for script-based animations API [[!ANIMATION-TIMING]].</p>
</section>
</section>
</section>
<section>
<h2>Network</h2>
<section>
<h2>HTTP</h2>
<p>User agents MUST support HTTP 1.1 [[!HTTP11]].</p>
</section>
<section>
<h2>CORS</h2>
<p>User agents MUST support Cross-Origin Resource Sharing [[!CORS]].</p>
</section>
<section>
<h2><code>data:</code> scheme</h2>
<p>User agents MUST support the <code>data:</code> URI scheme [[!RFC2397]].</p>
</section>
<section>
<h2><code>mailto:</code> scheme</h2>
<p>User agents MUST support the <code>mailto:</code> URI scheme [[!RFC6068]].</p>
</section>
<section>
<h2><code>tel:</code> scheme</h2>
<p>User agents MUST support the <code>tel:</code> URI scheme [[!RFC3966]].</p>
</section>
<section>
<h2><code>sms:</code> scheme</h2>
<p>User agents MUST support the <code>sms:</code> URI scheme [[!RFC5724]].</p>
</section>
<section>
<h2><code>mmsto:</code> scheme</h2>
<p>User agents MUST support the <code>mmsto:</code> URI scheme [[!OMA-URI-SCHEME]].</p>
</section>
</section>
</section>
</body>
</html>