User agents MUST support HTML5 [[!HTML5]].
-Some critical AppCache issues are being fixed 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?
+Some critical AppCache issues are being fixed 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?
Implementors should pay particular attention to the quality of implementation of the audio element. audio 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.
Can the latency requirements be lightened a bit. Sub 10ms seems ideal, slightly longer latency times may be acceptable for most use cases.
+Can the latency requirements be lightened a bit. Sub 10ms seems ideal, slightly longer latency times may be acceptable for most use cases.
meta ElementsWebApps WG is chartered 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).
+WebApps WG is chartered 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).
This is a new deliverable of the WebApps WG. See the WG's charter for details. No spec to link to for the moment. Could also end up as an attribute of Application Configuration.
+This is a new deliverable of the WebApps WG. See the WG's charter for details. No spec to link to for the moment. Could also end up as an attribute of Application Configuration.
Within the scope of the WebApps WG's charter. Could end up as an attribute of Application Configuration.
+Within the scope of the WebApps WG's charter. Could end up as an attribute of Application Configuration.
User agents MUST support CSS Values [[!CSS3VAL]].
-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 calc(), rem unit, but also some that don't seem to have a lot of traction (e.g. cycle()).
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 calc(), rem unit, but also some that don't seem to have a lot of traction (e.g. cycle()).
User agents MUST support CSS Selectors Level 3 [[!SELECTORS]].
Request for momentum scrolling (e.g. -webkit-overflow-scrolling: touch) are extremely common. Unfortunately, there is no spec effort at this point.
Request for momentum scrolling (e.g. -webkit-overflow-scrolling: touch) are extremely common. Unfortunately, there is no spec effort at this point.
User agents MUST support CSS Image Values and Replaced Content [[!CSS3-IMAGES]].
-CSS Image Values is a CR. Questionable content is marked at risk, which is reassuring.
+CSS Image Values is a CR. Questionable content is marked at risk, which is reassuring.
User agents MUST support CSS Text [[!CSS3TEXT]].
-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.
+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.
User agents MUST support the XMLHttpRequest API [[!XMLHTTPREQUEST]].
-The Editor folded level 1 and 2 in the same spec recently, but this isn't reflected in /TR yet.
+The Editor folded level 1 and 2 in the same spec recently, but this isn't reflected in /TR yet.
User agents MUST support the Web Workers API [[!WEBWORKERS]].
-Do we need both Shared and Web Workers?
+Do we need both Shared and Web Workers?