WebDev FeedHouse


456 Berea St (feed) Accessify.com (feed) CSS Help Pile (feed) Daniel Glazman - CSS and Style (feed) Daniel Glazman - Nvu (feed) Daniel Glazman - Standards (feed) Eric Meyer (feed) Hixie's Natural Log (feed) Microsoft - IEBlog (feed) Net Twits (feed) QuirksMode (feed) Stopdesign (feed) Vitamin (feed) W3C (feed) WaSP BUZZ (feed) Wisdump (feed) ajaxian (feed) design.Principles (feed) molly.com (feed) mozilla.org News (feed)


RSS 2.0

Want a blog added?

Email us! Planet



W3C Advisory Committee Elects Mark Nottingham to Technical Architecture Group

&lt;p&gt;The W3C Advisory Committee has elected Mark Nottingham (Akamai Technologies) to the &lt;a href="http://www.w3.org/2001/tag/"&gt;W3C Technical Architecture Group (TAG)&lt;/a&gt;. The mission of the TAG is to build consensus around principles of Web architecture and to interpret and clarify these principles when necessary, to resolve issues involving general Web architecture brought to the TAG, and to help coordinate cross-technology architecture developments inside and outside W3C.&lt;/p&gt; &lt;p&gt;Learn more &lt;a href="/2001/tag/"&gt;about the TAG&lt;/a&gt; and check out the &lt;a href="http://lanyrd.com/2014/extwebsummit-berlin/"&gt;Extensible Web Summit &#8211; Berlin&lt;/a&gt; on 11 September.&lt;/p&gt; </content>

by Ian Jacobs at September 02, 2014 01:00 AM

Encrypted Media Extensions; HTML Canvas 2D Context, Level 2 Drafts Published

&lt;p&gt;The &lt;a href="http://www.w3.org/html/wg/"&gt;HTML Working Group&lt;/a&gt; has published two documents today:&lt;/p&gt; &lt;ul class="show_items"&gt; &lt;li&gt;A Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-encrypted-media-20140828/"&gt;Encrypted Media Extensions&lt;/a&gt;. This proposal extends HTMLMediaElement providing APIs to control playback of protected content. The API supports use cases ranging from simple clear key decryption to high value video (given an appropriate user agent implementation). License/key exchange is controlled by the application. This specification does not define a content protection or Digital Rights Management system. Rather, it defines a common API that may be used to discover, select and interact with such systems as well as with simpler content encryption systems.&lt;/li&gt; &lt;li&gt;A Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-2dcontext2-20140828/"&gt;HTML Canvas 2D Context, Level 2&lt;/a&gt;. This specification defines the 2D Context for the HTML canvas element. The 2D Context provides objects, methods, and properties to draw and manipulate graphics on a canvas drawing surface.&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;Learn more about the &lt;a href="http://www.w3.org/MarkUp/Activity"&gt;HTML Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Last Call: Battery Status API

&lt;p&gt;The &lt;a href="http://www.w3.org/2009/dap/"&gt;Device APIs Working Group&lt;/a&gt; has published a Last Call Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-battery-status-20140828/"&gt;Battery Status API&lt;/a&gt;. This specification defines an API that provides information about the battery status of the hosting device. Comments are welcome through &lt;strong&gt;2 October&lt;/strong&gt;. Learn more about the &lt;a href="http://www.w3.org/2007/uwa/"&gt;Ubiquitous Web Applications Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Linked Data Platform Best Practices and Guidelines Note Published

&lt;p&gt;The &lt;a href="http://www.w3.org/2012/ldp/"&gt;Linked Data Platform (LDP) Working Group&lt;/a&gt; has published a Group Note of &lt;a href="http://www.w3.org/TR/2014/NOTE-ldp-bp-20140828/"&gt;Linked Data Platform Best Practices and Guidelines&lt;/a&gt;. This document provides best practices and guidelines for implementing Linked Data Platform servers and clients. Learn more about the &lt;a href="http://www.w3.org/2013/data/"&gt;Data Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

W3C Invites Implementations of CSS Masking Module Level 1

&lt;p&gt;The &lt;a href="http://www.w3.org/Style/CSS/members"&gt;Cascading Style Sheets (CSS) Working Group&lt;/a&gt; and the &lt;a href="http://www.w3.org/Graphics/SVG/WG/"&gt;SVG Working Group&lt;/a&gt; invite implementation of the Candidate Recommendation of &lt;a href="http://www.w3.org/TR/2014/CR-css-masking-1-20140826/"&gt;CSS Masking Module Level 1&lt;/a&gt;. CSS Masking provides two means for partially or fully hiding portions of visual elements: masking and clipping. Masking describes how to use another graphical element or image as a luminance or alpha mask. Clipping describes the visible region of visual elements. The region can be described by using certain SVG graphics elements or basic shapes. Anything outside of this region is not rendered. 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 &lt;a href="http://www.w3.org/Style/"&gt;Style Activity&lt;/a&gt; and the &lt;a href="http://www.w3.org/Graphics/"&gt;Graphics Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Last Call: CSS Counter Styles Level 3

&lt;p&gt;The &lt;a href="http://www.w3.org/Style/CSS/members"&gt;Cascading Style Sheets (CSS) Working Group&lt;/a&gt; has published a Last Call Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-css-counter-styles-3-20140826/"&gt;CSS Counter Styles Level 3&lt;/a&gt;. This module introduces the &lt;code&gt;@counter-style&lt;/code&gt; rule, which allows authors to define their own custom counter styles for use with CSS list-marker and generated-content counters. It also predefines a set of common counter styles, including the ones present in CSS2 and CSS2.1. Comments are welcome through &lt;strong&gt;23 September&lt;/strong&gt;. 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 &lt;a href="http://www.w3.org/Style/"&gt;Style Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

W3C Invites Implementations of HTML Canvas 2D Context

&lt;p&gt;The &lt;a href="http://www.w3.org/html/wg/"&gt;HTML Working Group&lt;/a&gt; invites implementation of the Candidate Recommendation of &lt;a href="http://www.w3.org/TR/2014/CR-2dcontext-20140821/"&gt;HTML Canvas 2D Context&lt;/a&gt;. This specification defines the 2D Context for the HTML canvas element. The 2D Context provides objects, methods, and properties to draw and manipulate graphics on a canvas drawing surface. Learn more about the &lt;a href="http://www.w3.org/MarkUp/Activity"&gt;HTML Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Predefined Counter Styles Draft Published

&lt;p&gt;The &lt;a href="http://www.w3.org/International/core/"&gt;Internationalization Working Group&lt;/a&gt; has published a Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-predefined-counter-styles-20140821/"&gt;Predefined Counter Styles&lt;/a&gt;. This document describes numbering systems used by various cultures around the world and can be used as a reference for those wishing to create user-defined counter styles for CSS. Learn more about the &lt;a href="http://www.w3.org/International/"&gt;Internationalization Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Media Accessibility User Requirements Working Draft Updated

&lt;p&gt;The &lt;a href="http://www.w3.org/WAI/PF/"&gt;Protocols and Formats Working Group (PFWG)&lt;/a&gt; today published an updated Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-media-accessibility-reqs-20140814/"&gt;Media Accessibility User Requirements&lt;/a&gt;, a planned W3C Working Group Note. This document describes the accessibility requirements of people with disabilities with respect to audio and video on the Web, particularly in the context of HTML5. It explains alternative content technologies that people use to get audio and video content, and how these fit in the larger picture of accessibility, both technically within a web user agent and from a production process point of view. Learn more about the &lt;a href="http://www.w3.org/WAI/"&gt;Web Accessibility Initiative (WAI)&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Wake Lock: Use cases Note Published

&lt;p&gt;The &lt;a href="http://www.w3.org/Mobile/IG/"&gt;Web and Mobile Interest Group&lt;/a&gt; has published a Group Note of &lt;a href="http://www.w3.org/TR/wake-lock-use-cases/"&gt;Wake Lock: Use cases&lt;/a&gt;. This document illustrates the use cases a mechanism to control the power-saving state of a device would enable on the Web platform. Learn more about the &lt;a href="http://www.w3.org/Mobile/"&gt;Mobile Web Initiative Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Standards for Web Applications on Mobile: current state and roadmap

&lt;p&gt;&lt;a class="imageLink" href="http://www.w3.org/2014/07/mobile-web-app-state/"&gt;&lt;img src="http://www.w3.org/2011/05/webapp-sm.png" alt="Thumbnail of application platform diagram that appears in the report" /&gt;&lt;/a&gt;W3C has published the July 2014 edition of &lt;a href="http://www.w3.org/2014/07/mobile-web-app-state/"&gt;Standards for Web Applications on Mobile&lt;/a&gt;, an overview of the various technologies developed in W3C that increase the capabilities of Web applications, and how they apply more specifically to the mobile context.&lt;/p&gt; &lt;p&gt;A deliverable of the &lt;a href="http://html5apps-project.eu/"&gt;HTML5Apps&lt;/a&gt; project, this edition of the document includes changes and additions since April 2014, notably a new section covers the emerging field of integrated payments on the Web, following recent work started by W3C in this space. Learn more about the &lt;a href="http://www.w3.org/Mobile/IG/"&gt;Web and Mobile Interest Group&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

W3C Invites Implementations of HTML5 Image Description Extension

&lt;p&gt;The &lt;a href="http://www.w3.org/html/wg/"&gt;HTML Working Group&lt;/a&gt; has published a Candidate Recommendation of the &lt;a href="http://www.w3.org/TR/2014/CR-html-longdesc-20140812/"&gt;HTML5 Image Description Extension&lt;/a&gt;, which defines the &#8220;longdesc&#8221; attribute that enables web authors to provide longer textual descriptions for complex images. This specification is part of W3C&#8217;s work to ensure that the Open Web Platform is accessible to people with disabilities. This publication addresses comments received during Last Call, and invites implementations. It is developed by the &lt;a href="http://www.w3.org/WAI/PF/html-accessibility-tf.html"&gt;HTML Accessibility Task Force&lt;/a&gt; in coordination with the &lt;a href="http://www.w3.org/html/wg/"&gt;HTML Working Group&lt;/a&gt; and the &lt;a href="http://www.w3.org/WAI/"&gt;WAI&lt;/a&gt; Protocols and Formats Working Group (&lt;a href="http://www.w3.org/WAI/PF/"&gt;PFWG&lt;/a&gt;). Please see details in the &lt;a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2014JulSep/0027.html"&gt;Call for Implementations: HTML5 Image Description Extension (longdesc) e-mail&lt;/a&gt;. Additional implementations are welcome through &lt;strong&gt;26 August 2014&lt;/strong&gt;. Learn more about the &lt;a href="http://www.w3.org/MarkUp/Activity"&gt;HTML Activity&lt;/a&gt; and the &lt;a href="http://www.w3.org/WAI/"&gt;Web Accessibility Initiative (WAI)&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Workshop Report: W3C Workshop on the Web of Things

&lt;p&gt;W3C published today the &lt;a href="http://www.w3.org/2014/02/wot/report.html"&gt;final report&lt;/a&gt; of the &lt;a href="http://www.w3.org/2014/02/wot/"&gt;W3C Workshop on the Web of Things&lt;/a&gt; that was held on 25-26 June 2014, in Berlin (Germany).&lt;/p&gt; &lt;p&gt;The workshop examined the opportunities for open Web standards for service platforms in the network edge and the cloud, along with the challenges for security, privacy and the integration with the Web of data.&lt;/p&gt; &lt;p&gt;The workshop gave a strong message of support for W3C to initiate work on standardization for the Web of Things. The foundations include RESTful HTTP and pub-sub protocols, but the detailed requirements vary across the use cases. Building upon these foundations, the workshop identified the need for standards for Web APIs that abstract away from the protocols, including the wide range of IoT technologies used at the network edge to connect to sensors and actuators. Through standardization, we can encourage re-use of APIs and data models.&lt;/p&gt; &lt;p&gt;The W3C staff will drive the process of chartering an Interest Group through reaching out to a wide range of interested stakeholders. Initial ideas for the scope are included in the workshop report.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

Tracking Compliance and Scope Draft Published

&lt;p&gt;The &lt;a href="http://www.w3.org/2011/tracking-protection/"&gt;Tracking Protection Working Group&lt;/a&gt; has published a Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-tracking-compliance-20140807/"&gt;Tracking Compliance and Scope&lt;/a&gt;. This specification defines the meaning of a Do Not Track (DNT) preference and sets out practices for websites to comply with this preference. Learn more about the &lt;a href="http://www.w3.org/Privacy/"&gt;Privacy Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

First Public Working Draft: Referrer Policy

&lt;p&gt;The &lt;a href="http://www.w3.org/2011/webappsec/"&gt;Web Application Security Working Group&lt;/a&gt; has published a First Public Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-referrer-policy-20140807/"&gt;Referrer Policy&lt;/a&gt;. This document describes how an author can set a referrer policy for documents they create, and the impact of such a policy on the &lt;code&gt;referer&lt;/code&gt; HTTP header for outgoing requests and navigations. Learn more about the &lt;a href="http://www.w3.org/Security/"&gt;Security Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

W3C Workshop Report: MultilingualWeb workshop in Madrid

&lt;p&gt;A &lt;a href="http://www.multilingualweb.eu/documents/2014-madrid-workshop/2014-madrid-workshop-report"&gt;report of the MultilingualWeb workshop in Madrid&lt;/a&gt; is now available from the MultilingualWeb site. It contains a summary of each session with links to presentation slides and minutes taken during the workshop in Madrid. The workshop was a huge success, with approximately 110 participants, and with the aligned &lt;a href="http://www.multilingualweb.eu/documents/2014-madrid-workshop/2014-madrid-workshop-report#lider_roadmapping"&gt;LIDER roadmapping workshop&lt;/a&gt;. The Workshop was hosted by &lt;a href="http://upm.es/"&gt;Universidad Politécnica de Madrid&lt;/a&gt;, sponsored by the EU-funded &lt;a href="http://lider-project.eu/"&gt;LIDER&lt;/a&gt; project, by &lt;a href="http://www.verisign.com/"&gt;Verisign&lt;/a&gt; and by &lt;a href="http://www.lionbridge.com/"&gt;Lionbridge&lt;/a&gt;. A new workshop in the MultilingualWeb series is planned for 2015. Learn more about the &lt;a href="http://www.w3.org/International/"&gt;Internationalization Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

W3C Updates Recommendation Track Process

&lt;p&gt;W3C enacted today the &lt;a href="http://www.w3.org/2014/Process-20140801/"&gt;1 August 2014 W3C Process Document&lt;/a&gt;. This revision updates the chapter that defines the Recommendation Track, the steps and requirements followed by W3C Working Groups to standardize Web technology. The W3C technical report development process is designed to support multiple specification development methodologies: maximize consensus about the content of stable technical reports; ensure high technical and editorial quality; promote consistency among specifications; facilitate royalty-free, interoperable implementations of Web Standards; and earn endorsement by W3C and the broader community. The primary change to the Recommendation Track is to merge &#8220;Last Call&#8221; and &#8220;Candidate Recommendation.&#8221; A &lt;a href="/wiki/ProcessTransition2014"&gt;Process Transition FAQ&lt;/a&gt; lists other changes to the Recommendation Track, explains the two-year transition plan for adoption by groups, describes the relation to the W3C Patent Policy, and more.&lt;/p&gt; &lt;p&gt;This document was developed between the &lt;a href="/2001/ab/"&gt;W3C Advisory Board&lt;/a&gt; and the public &lt;a href="/community/w3process"&gt;Revising W3C Process Community Group&lt;/a&gt;.&lt;/p&gt; </content>

by Ian Jacobs at September 02, 2014 01:00 AM

New Privacy Policy for W3C Site

&lt;p&gt;W3C today updated its &lt;a href="/Consortium/Legal/privacy-statement-20140324"&gt;privacy policy&lt;/a&gt; to reflect current technology and W3C practices. The policy does not make material &lt;a href="/Consortium/Legal/privacy-statement-20140324#changes"&gt;changes&lt;/a&gt; to what W3C does with information resulting from visits to our site. If you have questions, please write to site-policy@w3.org.&lt;/p&gt; </content>

by Ian Jacobs at September 02, 2014 01:00 AM

Upcoming coordinated Workshop: Encouraging open data usage by commercial developers

&lt;p&gt;W3C and its European host, ERCIM, announce the &lt;a href="/2013/share-psi/workshop/samos/report"&gt;report&lt;/a&gt; from the first workshop in the Share-PSI 2.0 series. &lt;a href="/2013/share-psi/"&gt;Share-PSI 2.0&lt;/a&gt; is the European network for the exchange of experience and ideas around implementing open data policies in the public sector. It brings together government departments, standards bodies, academic institutions, commercial organisations, trade associations and interest groups to identify what does and doesn&#8217;t work, what is and isn&#8217;t practical, what can and can&#8217;t be expected of different stakeholders.&lt;/p&gt; &lt;p&gt;In the first workshop, held as part of the 5th Annual &lt;a href="http://samos-summit.org/"&gt;Samos Summit on ICT-enabled Governance&lt;/a&gt;, the focus was &lt;strong&gt;Uses of Open Data Within Government for Innovation and Efficiency&lt;/strong&gt;. The report shows the many different strategies being adopted to foster a culture of data sharing across the public sector leading to significant efficiencies in operation, more effective delivery of the public task, reduced corruption and greater trust in important institutions like the police. From Helsinki to Athens via Dublin and Zagreb, from Oslo to Madrid via Tirana, Tenerife and Trentino &#8211; the public sector is making smarter use of the Web.&lt;/p&gt; &lt;p&gt;The Samos workshop also sets us up nicely for the next workshop in the series. Taking place in Lisbon in the first week in December, &lt;a href="/2013/share-psi/workshop/lisbon/"&gt;Encouraging open data usage by commercial developers&lt;/a&gt; will be highly interactive with many facilitated discussions and very few presentations.&lt;/p&gt; &lt;p&gt;W3C membership is not required to participate. The event is open to all, but all participants are required to submit a position paper or statement of interest by &lt;strong&gt;5 October 2014&lt;/strong&gt;. Share-PSI 2.0 is coordinated by W3C/ERCIM as part of the &lt;a href="/2013/data/"&gt;Data Activity&lt;/a&gt; and is closely aligned with the &lt;a href="/2013/dwbp/"&gt;Data on the Web Best Practices Working Group&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

CSS Ruby Layout Module Level 1 Draft Published

&lt;p&gt;The &lt;a href="http://www.w3.org/Style/CSS/members"&gt;Cascading Style Sheets (CSS) Working Group&lt;/a&gt; has published a Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-css-ruby-1-20140805/"&gt;CSS Ruby Layout Module Level 1&lt;/a&gt;. "Ruby", a form of interlinear annotation, are short runs of text alongside the base text. They are typically used in East Asian documents to indicate pronunciation, or to provide a short annotation. This module describes the rendering model and formatting controls related to displaying ruby annotations in CSS. 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 &lt;a href="http://www.w3.org/Style/"&gt;Style Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

W3C Invites Implementations of HTML5

&lt;p&gt;The &lt;a href="http://www.w3.org/html/wg/"&gt;HTML Working Group&lt;/a&gt; invites implementation of the Candidate Recommendation of &lt;a href="http://www.w3.org/TR/2014/CR-html5-20140731/"&gt;HTML5&lt;/a&gt;. This specification defines the 5th major revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features are introduced to help Web application authors, new elements are introduced based on research into prevailing authoring practices, and special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability. Learn more about the &lt;a href="http://www.w3.org/MarkUp/Activity"&gt;HTML Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Coralie Mercier at September 02, 2014 01:00 AM

For Review: Updated Techniques for Web Content Accessibility Guidelines (WCAG)

&lt;p&gt;The Web Content Accessibility Guidelines Working Group (&lt;a href="http://www.w3.org/WAI/GL/"&gt;WCAG WG&lt;/a&gt;) requests review of draft updates to Notes that accompany WCAG 2.0: &lt;a href="http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140724/"&gt;Techniques for WCAG 2.0 (Editors&#8217; Draft)&lt;/a&gt; and &lt;a href="http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140724/"&gt;Understanding WCAG 2.0 (Editors&#8217; Draft)&lt;/a&gt;. Comments are welcome through &lt;strong&gt;12 August 2014&lt;/strong&gt;. (This is not an update to WCAG 2.0, which is a stable document.) To learn more about the updates, see the &lt;a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2014JulSep/0013.html"&gt;Call for Review: WCAG 2.0 Techniques Draft Updates e-mail&lt;/a&gt;. Read about the &lt;a href="http://www.w3.org/WAI/"&gt;Web Accessibility Initiative (WAI)&lt;/a&gt;. &lt;/p&gt; </content>

by Ian Jacobs at September 02, 2014 01:00 AM

Developers Guide to Features of Web Accessibility Evaluation Tools Draft Published

&lt;p&gt;The First Public Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-WAET-20140724/"&gt;Developers&#8217; Guide to Features of Web Accessibility Evaluation Tools&lt;/a&gt; was published today by the Evaluation and Repair Tools Working Group (&lt;a href="http://www.w3.org/WAI/ER/"&gt;ERT WG&lt;/a&gt;). The document describes features that web authoring tools and quality assurance tools can incorporate to support web accessibility evaluation. It is useful for tool developers to get introductory guidance on these features, and is useful for people who want to compare tools, for example, during procurement. The document is intended to promote awareness of accessibility evaluation tool features and to encourage tool developers to include relevant features so that tools better support Web Content Accessibility Guidelines (&lt;a href="http://www.w3.org/WAI/intro/wcag"&gt;&lt;abbr&gt;WCAG&lt;/abbr&gt;&lt;/a&gt;) 2.0 conformance evaluation. Learn more about the &lt;a href="http://www.w3.org/WAI/"&gt;Web Accessibility Initiative (WAI)&lt;/a&gt;.&lt;/p&gt; </content>

by Ian Jacobs at September 02, 2014 01:00 AM

W3C Training: HTML5 and Responsive Web Design

&lt;p&gt;&lt;a class="imageLink" href="http://www.w3devcampus.com/"&gt;&lt;img src="http://www.w3devcampus.com/wp-content/uploads//logoW3devcampus/w3devcampus-v2.png" alt="W3DevCampus" width="106" height="40" /&gt;&lt;/a&gt; Registration is now open for two new online courses from W3C:&lt;/p&gt; &lt;ul class="show_items"&gt; &lt;li&gt;&lt;a href="http://w3devcampus.com/html5-w3c-training/"&gt;HTML5&lt;/a&gt; [&lt;strong&gt;&lt;a href="http://classroom.w3devcampus.com/enrol/index.php?id=83"&gt;Register&lt;/a&gt;&lt;/strong&gt;]. This course runs for 6 weeks, starting 22 September 2014. In addition to a JS crash course, numerous interactive examples and an &#8220;animated monster&#8221; contest, this new edition gives an introduction on Web components.&lt;/li&gt; &lt;li&gt;&lt;a href="http://w3devcampus.com/responsive-web-design-w3c/"&gt;Responsive Web Design&lt;/a&gt; [&lt;strong&gt;&lt;a href="http://classroom.w3devcampus.com/enrol/index.php?id=75"&gt;Register&lt;/a&gt;&lt;/strong&gt;]. This course runs for 4 weeks starting 3 October 2014. This course focuses on best practices, accessibility and optimization.&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;An &lt;strong&gt;early bird rate&lt;/strong&gt; is available for both courses until 24 August. Learn more about &lt;a href="http://w3devcampus.com/"&gt;W3DevCampus&lt;/a&gt;, the official W3C online training for Web developers and watch the &lt;a href="https://www.youtube.com/watch?v=XgyKbjOGCYA"&gt;intro video&lt;/a&gt;.&lt;/p&gt; </content>

by Ian Jacobs at September 02, 2014 01:00 AM

First Draft of Mixed Content Published

&lt;p&gt;The &lt;a href="http://www.w3.org/2011/webappsec/"&gt;Web Application Security Working Group&lt;/a&gt; has published a First Public Working Draft of &lt;a href="http://www.w3.org/TR/2014/WD-mixed-content-20140722/"&gt;Mixed Content&lt;/a&gt;. This specification details how user agents can mitigate risks to security and privacy by limiting a resource???s ability to inadvertently communicate in the clear, or to expose non-public resources to the web at large. This specification describes how and why user agents disallow rendering and execution of content loaded over unencrypted or unauthenticated connections in the context of an encrypted and authenticated document. Learn more about the &lt;a href="http://www.w3.org/Security/"&gt;Security Activity&lt;/a&gt;.&lt;/p&gt; </content>

by Ian Jacobs at September 02, 2014 01:00 AM

Eric Meyer

Artisanal Bereavement Spam

On the last day of shiva, this past June, we got a letter in the mail.  Just by looking at the envelope, I could see that it was a note of condolence, and from a nearby address to boot"yet the name was entirely unfamiliar.  When I opened it, I discovered a handwritten note that started with a perfunctory condolence and then immediately turned to extended proselytizing.  Enclosed was a religious tract specifically about the afterlife.

From the actual text, it was clear the person who wrote it didn't know us at all, didn't know the first thing about us or what we had just gone through.  They had simply trawled that week's obituaries to get our names and address, and proselytized by mail.

I wish I were making this up.  But no, someone really did decide that the occasion of our daughter's death was the perfect time to thrust their religious recruitment efforts into our lives.  Artisanal bereavement spam, basically.

I tweeted about it, leaving out identifying information, but otherwise let it go.  An unfortunate one-off, I figured; someone with more fervor than sense, not to be taken as representative of the group as a whole.

Except it just happened again.  Different person, same religion, same basic approach.  This letter isn't as glaringly obvious about the obituary trawling, no hollow claims of sympathy or condolence this round, but the handwritten emphasis on seeing dead loved ones again makes it pretty obvious that this is of a piece.


So, yes.  The Jehovah's Witnesses apparently think it is a fine idea to vulturously circle the misery of others and then swoop in to deposit a load of tract on the dining room tables of grieving families.  And what's more, to keep doing it.

I disagree.  I don't even beg to differ, I simply disagree.  If there were an opt-out mechanism, I would most certainly make use of it.  In so doing, I would include a number of comments regarding their apparent need to hide their intent with misdirection and to prey on the extreme pain and emotional vulnerability of others.  Since no such mechanism appears to exist, this post will have to do.

Of course, just as I did the first time this happened, I handled the note, the tracts, and the envelope itself with every bit of the care and respect they deserved.


I Googled around a bit and only found two posts about this practice ("Are Jehovah Witness Members Trolling Obituaries for New Recruits?" (2009), "Letters from Jehovah's Witnesses" (2013).  Well, here's a third, this one backed up with visual evidence.

I'm posting this in case others experience the same thing and wonder if they caught a lone crazy.  I'm sorry, but no, they aren't "lone".  If you got one, you may well get more.  I very much wish it were otherwise.

by Eric Meyer at August 26, 2014 02:17 PM


The Mobile Web Handbook &#8212; nearly done

On Tuesday I delivered the final edits for The Mobile Web Handbook, my new book published by Smashing Magazine. Order it here.

The book is a bit late; it was originally slated to appear in June. However, it’s really done now; you can expect the e-book in about a week and the physical book at the end of September. Right now the only unresolved issues are a few minor styling ones, as well as the index. I expect both to be solved somewhere next week.

Writing a book about the mobile market and the mobile web is tricky. Circumstances change faster than I can keep up with even on a blog, let alone in a book that’s already slightly outdated by the time it reaches the consumer. That’s why I decided to talk about mobile web fundamentals such as the viewports and touch events, as well as the browser market, especially the Android one. These topics will remain important in years to come, even though browser compatibility patterns will continue to shift. The gory compatibility details are on the companion pages (work in progress; not ready yet.)

The Mobile Web Handbook. Written by me. Tech editor: Stephanie Rieger. Design and illustrations: Stephen Hay. General editor: Vitaly Friedman. Copy editor: Owen Gregory. Additional editors: Patrick Lauke, Max Firtman, and Vasilis van Gemert. Production: Markus Seyfferth.

Here’s the table of contents:

  1. The Mobile World: How the mobile world differs from the desktop world. Highlights operators and device vendors.
  2. Browsers: How the mobile browser market works. Which types of browsers there are. Excludes Android, which is more complicated than the rest combined.
  3. Android: Why the Android browser market is so terribly complicated. Why Google Chrome is not the default browser on all that many devices.
  4. Viewports: Why mobile browsers need three viewports instead of the one that desktop browsers support. Also resolution, media queries, the screen.width/height problem, and related topics.
  5. CSS: A quick look at several CSS declarations that are hard to implement on mobile for a variety of reasons.
  6. Touch And Pointer Events: What touch and pointer events are, how they work, and the difference between them. Also: why Microsoft’s insistence on pointer instead of touch events makes sense from a certain perspective. Future of event handling on many devices.
  7. Becoming A Mobile Web Developer: Some tips and tricks for becoming a mobile web developer. Mostly about which devices your lab should have and how to collect them, but also a bit about a few aspects of desktop web development that may not translate to mobile.
  8. The Future of the Web on Mobile: A quick look into the future. What's next? How will the web evolve on mobile?

In general, and with my financial well-being in mind, I’d say everyone who reads this should buy it. That especially goes for web developers who want to understand mobile browsers and the mobile web more than they do today.

August 21, 2014 12:17 PM

Eric Meyer


Being here, in the same vacation spot we were last year when Rebecca fell ill, wasn't as difficult as I thought it would be" until last Friday, August 15th, the first anniversary of her seizures and life flight to CHOP.

That night, the next day, and the days since were much more difficult for me, as we moved through the anniversaries of her first and second surgeries.  Today is the anniversary of the third, when they implanted the drainage tube that probably kept her functional and complete until the last few days of her life.

These days have been so difficult because I've been experiencing what I've come to refer to as "divergence stress".  I feel as though last year's August and this year's are running in parallel, branching from this past Friday.  I am here, sitting in our rental, looking at the beach and the ocean waves, and feel as though another of me is up in Philadelphia, gaunt and teary-eyed in a dim intensive care ward and hoping against hope that our daughter will survive, while I sit in sunshine and luxury, wondering why I am not with my little girl who so desperately needs me right now, who I so desperately want to hold and talk with again.

Or worse, that another me isn't up in Philadelphia, but Rebecca still is, lying unconscious and alone in the intensive care unit.  As though the loop has restarted, but I have stepped out of it, abandoning my baby to her cancer.

I know this isn't the truth.  She is not there.  We are not there.  We are here, now, and she is not.

But someone else, right now, as you read this, is there.  Another family is assembling around a PICU bed, surrounding their child and hoping against hope and sick, choking fear that their beloved will survive.  Maybe they will.  Many do.

That family, and all the families still to come, need research to give their children a better chance to live.  Many of them will need a place to stay while their child endures weeks or months of surgeries and treatments, just as we did.

To that end, our friends Nancy Massey and Kimberly Blessing have launched a fundraiser with two aims.  The first is to support research into pediatric brain cancer.  The second is to sponsor a room at the Philadelphia Ronald McDonald House for a year.  The $10,000 fundraising goal will allow both.  Going beyond that goal will make it possible to support even more research.

It's not much to make sure those other families have a welcoming place to stay and a better chance at continued life than we did.  If you can, please make a contribution.

by Eric Meyer at August 20, 2014 01:39 PM

Eric Meyer

One Year

Exactly one year ago, in the emergency department of Cape Regional Medical Center, Rebecca had the first of her seizures, and our nightmare began.

Now we are back in the same place for our annual family vacation.  The same resort, the same building, even the same floor, though not the same room.  We go to the beach, we swim in the pools, we play games on the boardwalk.  All the things Rebecca loved to do.  In fact, her first wish with Make-A-Wish was not to go to Disney World.  Her wish was that it be summer so she could come back to New Jersey and do all those things.  Disney was a distant runner-up, a sort of consolation prize for not being able to do what she really wanted to do.

Even as we organized for that Disney trip, Kat and I decided to bring the family to New Jersey for an early vacation, if Rebecca was well enough once June finally came.  And then to come again in August, unless Rebecca was still alive but too sick to make the journey.  Neither came to pass.

Instead, we're here without her.  I had feared this would be too painful for us to bear, but it isn't.  New memories are being made with our children, and if sometimes Kat and I are drawn up short by a specific memory, or a wish that Rebecca were here to enjoy the trip with us, or just having the instinct to count three heads before realizing that we only have to count two, it is usually a wistful sorrow rather than a sharp agony.  Usually.

Those newly-made memories, of jumping waves and digging holes in the sand and boardwalk ice cream and going to water parks, are the building blocks of healing.  Forming them in the place that Rebecca loved so much is, we hope, the mortar that will glue them together.  It helps that we love it here too, and that love is limned by the memory of her love.

It all still seems unreal.  Our lives were proceeding as lives do, and then, in the middle of our special family time away, we were suddenly confronted with the horror that our middle child, our five-year-old girl, had a tumor in the middle of her brain.

I remember all the shock and terror and anguish, but not like it was yesterday, because it wasn't.  It was a year ago today.

by Eric Meyer at August 15, 2014 09:55 PM

Microsoft - IEBlog

Announcing new F12 dev tools features in August update

Today we're excited to share all the F12 features that shipped in the August update to IE11!

In April, we shipped a swath of new features of F12 Developer Tools in Internet Explorer 11 focusing on providing accurate data in the DOM Explorer, actionable data in the memory and performance tools and a smoother debugging experience with Just My Code.

With the IE Developer Channel in June we previewed more features in the F12 Developer Tools and now all of these features are shipping out to all of our customers. It's a long list which you'll find below or on MSDN but the highlights are:

  • Import and export sessions in the Memory and UI Responsiveness tools
  • Improved filtering capabilities in the Memory and UI Responsiveness tools
  • A color picker in the DOM Explorer that allows you to pick colors from any window on your desktop.

With this update to IE11 and F12, we're keeping the pace of updating the F12 developer tools more often, getting you the latest features and bug fixes as soon as we can. Expect to see and hear from us more and if you'd like to provide feedback, or ask for new features and help simply reach out on Twitter @IEDevChat, or on Connect.

" Andy Sterland, Senior Program Manager, Internet Explorer

Changes to the F12 user interface

  • New icons and notifications

    The icons for the Memory and Profiler tools have changed.

    There are now indicators on the icon bar for errors in the Console, changes in Emulation settings, and for active profiling sessions in the Memory, Profiler, and UI Responsiveness tools. The image below shows the new icons with notifications on the Console and Memory tool icons, indicating there are two Console errors displaying and that a Memory profiling session is currently in progress.

    New icons for memory and profiler

  • F6 superset navigation within tools

    Using F6 is like using the tab key to navigate around a tool, but it "tabs" through a selected set of the most commonly used elements in a tool pane, rather than through every selectable item. This is part of an overall cleaner system for using the keyboard to navigate within and between tools.

  • Move back and forth between recently used tools using the keyboard

    Use CTRL + [ to move backwards in your tool navigation history, CTRL + ] to go forward, much like the back and forward arrows when you're browsing.

  • Quick access to document mode

    Want to access the Document mode without switching tools? We added a new dropdown at the top that gives you access to the document mode from any tool.

    Quick access to document mode

Console changes

  • console.timeStamp()

    When called from the Console or within code, it outputs to the Console the number of milliseconds the current browser tab has been open. If called while running a profiling session with the UI Responsiveness tool, it creates a user mark on the session's timeline with a timestamp based on the time since the session started.

  • CTRL+L clears the console of all messages

  • Accurate autocomplete

  • Console's autocomplete no longer includes indexer properties, making for a cleaner and more accurate selection of autocomplete suggestions.

    $, $$, $x, $0-$5, and $_ have been added to the Console autocomplete list for the convenience for those who use them and to make the Console's behavior more consistent with other browsers.

  • Stale message indicator

    If you have chosen to turn off the Clear on navigate option, older console messages have their icons greyed out to help distinguish between messages for the active page and messages from prior pages in your history.

    Stale message indicator

DOM Explorer changes

  • Change bars in Computed pane

    The change bars (different colors for changed properties, added properties, and deleted properties) users have been enjoying the Styles pane, now appear in the Computed styles pane.

    Change bars in Computed pane

  • Color Picker

  • Clicking on the color picker icon (or by using the keyboard shortcut ctrl+k) will open up a free standing version of the color picker with the expanded color wheel that's useful for getting colors that are then going to be pasted elsewhere either in F12 or back in a text or image editor.

    Color picker

  • Color Wheel

    The color wheel is the 2nd icon on the color picker and when activated will expand to show the color wheel. The actual color wheel is a set of four sliders (as below) which can be used to change the HSL and transparency values for a color.

    Color wheel

  • Color Swatch

    The swatch on the color picker is a palette of all the colors F12 found in the CSS files associated with the page sorted by the number of occurrences. This should make finding common colors, such as accent colors, much easier. The swatch can be navigated with the left and right arrow keys which will scroll through all the colors.

  • Color Square

    Clicking on a color square brings up the color picker with the color wheel collapsed and can be used to set the color for the particular CSS property.

  • Eye Dropper

    The eye dropper can be used to pick a color under the cursor from any screen on the computer which is great for getting values from image editors or from other Web pages. There's a limitation in the eye dropper where the color will be off by 1/255 of its real value. We'll fix this in a future update.

Debugger changes

  • Sourcemaps designate

    Right-click on a document's tab in the Debugger and you can specify a source map. This makes it possible to use source maps with shipped code that has had the source map comment removed.

    Sourcemaps designate

  • Autocomplete in watches

    Now, when adding a watch, you get autocomplete options suggested.

    Autocomplete in watches

  • Return value inspection

    When breaking on a function with a return value, step into the function until you've stepped to the closing curly bracket. The return value will be displayed in the Locals portion of the Watches pane. Step again and the value will be returned to the code that called for it.

    For a quick demonstration, try this code in the Console:

    function showval() { var x = 0; x++; debugger; return x; } showval(); 

    It will call the function, break on debugger, and you can step into it to see the return value.

  • Multi-select for breakpoints

    CTRL + CLICK, SHIFT + CLICK, and CTRL + A work to select multiple breakpoints in the Breakpoints pane.

  • Continue and ignore breaks

    Press F5 to continue to the next break. Hold F5 to continue past multiple breaks until you release F5.

  • Event breakpoints and tracepoints

    These work much like the breakpoints and tracepoints already present in F12 tools, but instead of being triggered when a specific block of code is executed, they are triggered when a specific event fires. Each has an optional conditional filter to help you narrow down their scope to the specific instance of an event that you want to inspect. They can be added using the Add event tracepoint and Add event breakpoint icons highlighted in the image below.

    Event breakpoints and tracepoints

  • Async call stack code

    You can now see the call stack for those pesky async calls!

    Async call stack code

UI Responsiveness tool changes

  • Import/export performance sessions

    You shouldn't have to reproduce your test case every time you want to analyze data it produces or share that data with a colleague. The import (folder) and export (disk) icons on the UI Responsiveness tool's icon bar let you save your memory snapshots to a file that can be imported later.

  • Image preview

    If you've seen an HTTP request for an image and wondered which image it was, the image is now previewed in the event details.

    Image preview

  • Filtering events

    The Filter events button is small but mighty. Hidden behind that button is a menu that lets you filter events in multiple ways and each way has a significant impact.

    Event name filter

    Filter for any event name containing a match for the filter text.

    UI activity filter

    Using the checkboxes, you can exclude larger categories of events to make it easier to focus on the area you're investigating. For example, if you're just interested in network activity, you can filter out all the noise of the UI and garbage collection.

    Time threshold filter

    This feature filters out top-level events less than 1ms in duration. In many scenarios, this dramatically simplifies the waterfall view and helps you focus on more impactful events.

    Time threshold filter

  • HTML5 scripting events

    If you use media query listeners or MutationObservers, you can now identify their respective costs when running a performance profiling session.

    HTML5 scripting events

  • Frame grouping

    The button between the Sort by dropdown and the Filter events menu toggles Frame grouping. This groups top-level events into their corresponding unit of work (or "frame") during periods of time where animations/visual updates were occurring. The frames are treated like other events, so they can be sorted and filtered, and they provide an Inclusive time summary.

    Frame grouping

  • User measures

    If you use the performance.mark() API to add triangles to the timeline, indicating where specific events happened, the performance.measure() API extends the usefulness of performance marks. Use the performance.measure() to create a User measure event encompassing the time between two performance.mark() events, right click the event, and use the Filter to event option to select just the events between the two marks.

    User measures

  • Colorization for DOM

    This feature adds colorization to DOM elements, string literals and number literals. Besides making the content within the different F12 tools look and behave more alike, it adds a little more visual interest to the UI Responsiveness tool.

  • Selection summary

    When you select a portion of the timeline, the event details pane will show a summary of the selection. Hover over different segments of the circular chart for a tooltip with the segment's event category.

    Selection summary

  • Support for console.timeStamp()

    Using the console.timeStamp() method in your code or in the console during a profiling session creates a user mark on the timeline with the time since the profiling session began.

Memory tool changes

  • Dominator folding

    Dominator folding helps simplify the contents of a snapshot by removing objects from the top-level views that are logically components of another object (e.g. a <BR> within a <DIV>, a Scope held on to by a Function) and tend to be extra details that don't improve your insight into the data, but could waste your time.

    For example, the image below shows before and after views, demonstrating how dominator folding improves the "story" the tool is telling. The folded view shows 30 HTML <DIV> elements, which account for 15.64 MB of memory, and are holding on to detached DOM nodes. In many cases, it isn't important to know the composition of an object, so much as simply knowing that it is too large, or that it is leaking (especially when using third-party libraries).

    Dominator folding

  • Colorization of DOM, String & Number literals

    This feature adds colorization to DOM elements, string literals, and number literals. Besides making the content within the different F12 tools look and behave more alike, it makes memory analysis a little more visually interesting.

  • Roots cycle filtering

    Want to be able to investigate the composition of an object without getting unknowingly lost in a circular reference path? This feature detects child references which are circular and "trims" them, so that you don't get confused by traversing them into infinity. Additionally, it annotates these references so that it's clear when a reference has in fact been "trimmed."

  • Import/export session

    You shouldn't have to reproduce your test case every time you want to analyze data it produces or share that data with a colleague. The import (folder) and export (disk) icons on the Memory tool's icon bar let you save your memory snapshots to a file that can be imported later.

    Import/export session

Emulation tool changes

  • Settings persistence and reset

    A Persist Emulation settings icon is added to the Emulation tool. This will maintain your current emulation settings until specifically disabled, allowing you to work, close the browser, and come back with your emulation settings intact. To its right is a Reset Emulation settings icon, which quickly resets the tool back to default values.

    Emulation settings persistence and reset

by ieblog at August 14, 2014 05:58 PM

Powered by: Planet
Hosted by: Keller Technologies Inc.