W3C

The Web Performance Working Group has published a First Public Working Draft of Frame Timing. This specification defines an interface to help web developers measure the performance of their applications by giving them access to frame performance data to facilitate smoothness (i.e. Frames per Second and Time to Frame) measurements. Learn more about the Rich Web Client Activity.

The Web Performance Working Group has published a Working Draft of Navigation Timing 2. This specification defines a unified interface to store and retrieve high resolution performance metric data related to the navigation of a document. Learn more about the Rich Web Client Activity.

The Cascading Style Sheets (CSS) Working Group has published two documents today:

• A First Public Working Draft of CSS Pseudo-Elements Module Level 4. This CSS module defines pseudo-elements, abstract elements that represent portions of the CSS render tree that can be selected and styled.
• A Working Draft of CSS Exclusions Module Level 1. CSS Exclusions define arbitrary areas around which inline content can flow. CSS Exclusions can be defined on any CSS block-level elements. CSS Exclusions extend the notion of content wrapping previously limited to floats.

CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. Learn more about the Style Activity.

The IndieUI Working Group today published an updated Working Draft of IndieUI: Events 1.0 – Events for User Interface Independence. This draft includes new events and a refined technical model. IndieUI: Events defines a way for different user interactions to be translated into simple events and communicated to Web applications. (For example, if a user wants to scroll down a page, they might use their finger on a touch screen, or click a scroll bar with a mouse, or use a scroll wheel, or say ‘scroll down’ with a voice command. With IndieUI, these are all sent to the Web app as simply: scroll down.) IndieUI will make it easier for Web applications to work in a wide range of contexts — different devices (such as mobile phones and tablets), different assistive technologies (AT), different user needs. With IndieUI, Web application developers will have a uniform way to design applications that work for multiple devices and contexts. Comments on this Draft are encouraged by 13 February 2015. Learn more from the IndieUI Overview and the Updated Working Draft: IndieUI Events e-mail; and read about the Web Accessibility Initiative (WAI).

The Web Applications Working Group and the Technical Architecture Group have published a First Public Working Draft of Packaging on the Web. This document describes an approach for creating packages of files for use on the web. The approach is to package them using a new application/package media type. To access packages related to other files on the web, clients that understand packages of files look for a Link header or (in HTML documents) a <link> element with a new link relation of package. Other formats may define format-specific mechanisms for locating related packages. Learn more about the Rich Web Client Activity and the Technical Architecture Group.