Android Police | Google Has Started Automatically Converting Flash Ads To HTML5 Android Police Google started offering advertisers the option of backing up Flash ads as HTML5 last year. These ads would then be served on devices where Flash was not supported. Now Google will start doing that automatically for all new and existing Flash ads that ... |
Flash flushed: Google's AdWords to convert ads to HTML5 automatically The Register In the latest blow to Adobe's little-loved Flash graphics format, Google has begun nudging customers of its AdWords ad network to wean themselves off Flash by offering automatic conversion of Flash ads to HTML5. "Over half of time spent online is now ... |
The Linked Data Platform (LDP) Working Group has published a W3C Recommendation of Linked Data Platform 1.0. “Linked Data” refers to an approach to publishing data that puts linking at the heart of the notion of data, and uses the linking technologies provided by the Web to enable the weaving of a global distributed database. This specification defines a set of rules for HTTP operations on Web resources, some based on RDF, to provide an architecture for read-write Linked Data on the Web. Learn more about the Data Activity.
The Web Application Security Working Group has published a Working Draft of Content Security Policy Pinning. This document defines a new HTTP header that allows authors to instruct user agents to remember (“pin”) and enforce a Content Security Policy for a set of hosts for a period of time. Learn more about the Security Activity.
The group also published a Working Draft of Upgrade Insecure Requests. This document defines a mechanism which allows authors to instruct a user agent to upgrade a priori insecure resource requests to secure transport before Fetching them. Learn more about the Security Activity.
The HTML5 Image Description Extension (longdesc) was published today as a Recommendation by the HTML Working Group, with the approval of the Protocols and Formats Working Group. This extension for HTML5 adds a longdesc attribute that is used to provide links to detailed descriptions of images, and is part of W3C’s work to ensure that the Open Web Platform is accessible to people with disabilities. Learn more about the HTML Activity and the WAI Technical Activity.
The Web Content Accessibility Guidelines (WCAG) Working Group today published updates of two Notes that accompany WCAG 2.0: Understanding WCAG 2.0 and Techniques for WCAG 2.0. This is not an update to WCAG 2.0, which is a stable document. The WCAG guidelines and success criteria are designed to be broadly applicable to current and future web technologies, including dynamic applications, mobile, digital television, etc. The supporting resources published today provide specific guidance — including code examples, resources, and tests — and are updated periodically to cover current practices for meeting WCAG. For an introduction to the WCAG documents, see the WCAG Overview. Read about the Web Accessibility Initiative (WAI).
SVG Accessibility API Mappings 1.0 (SVG-AAM) was published today as a First Public Working Draft by the Protocols and Formats Working Group and SVG Working Group. This specification allows SVG authors to create accessible rich internet applications, including charts, graphs, and other drawings. It provides SVG-specific guidance to define how the SVG user agent must respond to keyboard focus, native SVG features, and role, state, and property attributes provided in web content via WAI-ARIA . SVG-AAM is the first technology-specific module that provides accessibility API mapping support for features in WAI-ARIA 1.1; other technology-specific mappings will follow. Learn more about the Interaction Domain and the Web Accessibility Initiative (WAI).
Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile was published today as a First Public Working Draft by the Mobile Accessibility Task Force, a joint Task Force of the Web Content Accessibility Guidelines Working Group (WCAG WG) and the User Agent Accessibility Guidelines Working Group (UAAG WG). This document describes how WCAG 2.0 principles, guidelines, and success criteria apply to mobile web content, mobile web apps, native apps, and hybrid apps using web components inside native apps. It provides guidance on mobile accessibility issues — such as small screen size, touch target size, zoom, gestures — and how they relate to WCAG 2.0. It links to a list of existing WCAG Techniques that apply to mobile.
The document also highlights the relevance of UAAG 2.0 and ATAG 2.0 in the mobile context, and links to UAAG 2.0 mobile accessibility examples. This document provides informative guidance, and does not set requirements. It may become a W3C Working Group Note, or the information may be integrated into WCAG Techniques and Understanding WCAG. (It will not impact WCAG 2.0 itself; WCAG 2.0 is a stable standard that does not change.) For information on W3C WAI’s broader work related to mobile accessibility, see Mobile Accessibility. Learn more about the Web Accessibility Initiative (WAI).
Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile was published today as a First Public Working Draft by the Mobile Accessibility Task Force, a joint Task Force of the Web Content Accessibility Guidelines Working Group (WCAG WG) and the User Agent Accessibility Guidelines Working Group (UAAG WG). This document describes how WCAG 2.0 principles, guidelines, and success criteria apply to mobile web content, mobile web apps, native apps, and hybrid apps using web components inside native apps. It provides guidance on mobile accessibility issues — such as small screen size, touch target size, zoom, gestures — and how they relate to WCAG 2.0. It links to a list of existing WCAG Techniques that apply to mobile.
The document also highlights the relevance of UAAG 2.0 and ATAG 2.0 in the mobile context, and links to UAAG 2.0 mobile accessibility examples. This document provides informative guidance, and does not set requirements. It may become a W3C Working Group Note, or the information may be integrated into WCAG Techniques and Understanding WCAG. (It will not impact WCAG 2.0 itself; WCAG 2.0 is a stable standard that does not change.) For information on W3C WAI’s broader work related to mobile accessibility, see Mobile Accessibility. Learn more about the Web Accessibility Initiative (WAI).
Google Announces The Automatic Conversion Of Flash Ads To HTML5, Starting ... WCCFtech Adobe Flash ads can be converted to HTML5 starting today, announced Google. With the introduction of this new conversion system by Google, it will be much more easier than ever for the advertisers to target users without a device or any sort of browser ... |
Google Steps up Snub of Adobe Flash, Auto-Converting Flash Ads to HTML5 DailyTech Over half of time spent online is now spent on mobile devices [http://goo.gl/wba3N6].^ This presents a tremendous opportunity for marketers to reach their customers throughout the day, whenever they may be browsing. But there is an all-too-common ... |
Google REALLY wants you to see ads -- Adwords automatically converts Flash ... BetaNews That's why we're introducing a way to automatically convert Flash ads to HTML5, giving advertisers better access to the portion of Google Display Network inventory that is HTML5-only", says Google. The search-giant further explains, "with this new tool ... |
The Data on the Web Best Practices Working Group has published a First Public Working Draft of Data on the Web Best Practices, to encourage and enable the continued expansion of the Web as a medium for the exchange of data. Data should be discoverable and understandable by humans and machines. Where data is used in some way, whether by the originator of the data or by an external party, such usage should also be discoverable and the efforts of the data publisher recognized. In short, following these best practices will facilitate interaction between publishers and consumers.
The group also published today a Group Note of Data on the Web Best Practices Use Cases & Requirements with scenarios of how data is commonly published on the Web and how it is used. This document also provides a set of requirements derived from these use cases that will be used to guide the development of the Best Practices document and also two new vocabularies: Quality and Granularity Description, and Data Usage Description. Learn more about the Data Activity.
You can’t read about service workers without getting excited—they’re the behind-the-scenes infrastructure that make it possible for web pages to act more like web applications. Upcoming web platform features like background sync and push notifications will rely on service workers, and following the release of Chrome 40, service worker-based caching is available to use today. If you’ve wanted to add service worker-powered offline support to your sites, but weren’t sure how to get started, the sw-precache module is for you! sw-precache hooks into your existing node-based build process (e.g. Gulp or Grunt ) and generates a list of versioned resources, along with the service worker code needed to precache them. Your site can start working offline and load faster even while online, by virtue of caching.
The service worker generated by sw-precache will cache and serve the resources that you configure as part of your build process. For smaller, mostly static sites, you can have it precache every image, HTML, JavaScript, and CSS file that makes up your site. Everything will both work offline, and load fast on subsequent visits without any extra effort. For sites with lots of dynamic content, or many large images that aren’t always needed, precaching a “skeleton” subset of your site often makes the most sense. You can combine sw-precache with one of the service worker “recipes” or techniques outlined in the offline cookbook to provide a robust offline experience with sensible fallbacks—e.g. when a large, uncached image is requested offline, serve up a smaller, cached placeholder image instead.
Because sw-precache integrates into your site’s build process, you can use wildcards to precache all of the resources that match a pattern—there’s no list of files or URLs that you have to manually keep up to date. What’s more, the module automatically versions all your cached resources based on a hash of each file’s contents. When a change to any file is detected as part of your build process, the generated service worker knows to expire the old version and fetch the new version of the resource. All of the cache entries that remain the same are left untouched.
Here’s a basic example of using sw-precache as part of a gulp build:
gulp.task('generate-service-worker', function(callback) {
var fs = require('fs');
var swPrecache = require('sw-precache');
var rootDir = 'app';
swPrecache({
staticFileGlobs: [rootDir + '/**/*.{js,html,css,png,jpg,gif}'],
stripPrefix: rootDir
}, function(error, swFileContents) {
if (error) {
return callback(error);
}
fs.writeFile(path.join(rootDir, 'service-worker.js'), swFileContents, callback);
});
});
You’ll see information about which resources will be precached, as well as the total precache size as part of the task output:
Starting 'generate-service-worker'...
Caching static resource 'app/css/main.css' (65 B)
Caching static resource 'app/images/one.png' (593 B)
Caching static resource 'app/images/two.png' (641 B)
Caching static resource 'app/index.html' (2.09 kB)
Caching static resource 'app/js/a.js' (7 B)
Caching static resource 'app/js/b.js' (7 B)
Caching static resource 'app/js/service-worker-registration.js' (3.37 kB)
Total precache size is about 6.77 kB for 7 resources.
Finished 'generate-service-worker' after 14 ms
There’s a lot more information at the GitHub project page, including a demo project with gulpfile.js and Gruntfile.js samples, and a script you can use to register the generated service worker. If you’d like to see it in action, just check out the recently launched Google I/O 2015 web app—thanks (in part) to sw-precache, you can browse it at your leisure, online or off.
The Cascading Style Sheets (CSS) Working Group has published a Working Draft of CSS Basic User Interface Module Level 3 (CSS3 UI). This specification describes user interface related selectors, properties and values that are proposed for CSS level 3 to style HTML and XML (including XHTML). It includes and extends user interface related features from the selectors, properties and values of CSS level 2 revision 1 and Selectors specifications. It uses various selectors, properties and values to style basic user interface elements in a document. Learn more about the Style Activity.
The Pointer Events Working Group has published a W3C Recommendation of Pointer Events. The Pointer Events specification defines a unified set of events and interfaces for device-neutral pointer input, such as a mouse, touchscreen, and pen-tablet, including capabilities for handling pointer pressure, contact geometry, and tilt; it also defines a mapping to traditional mouse events. This specification provides additional functionality not available in the related Touch Events specification; for more information on the relationship between these two specifications, see the Touch Events Community Group. Learn more about the Rich Web Client Activity.
Front End Developer - JavaScript/HTML5/Angular/Backbone CIO Australia THE most amazing culture Immediate start Sydney CBD This is an opportunity like no other!! The worlds largest search engine is on the hunt for a super talented Front End Developer to join them on an 11 month contract. You will join the creative ... |
The Web Real-Time Communications Working Group and Device APIs Working Group have published a Working Draft of Media Capture from DOM Elements. This document defines how a stream of media can be captured from a DOM element, such as a video, audio, or canvas element, in the form of a MediaStream. Learn more about the Ubiquitous Web Applications Activity.
The XML Query Working Group has published a Last Call Working Draft of XQuery Update Facility 3.0. This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility 3.0 provides expressions that can be used to make persistent changes to instances of the XQuery and XPath Data Model 3.0. Comments are welcome through 19 March. Learn more about the Extensible Markup Language (XML) Activity.
Today the XSLT Working Group and the XML Query Working Group jointly published a Candidate Recommendation for, and invite implementations of, XSLT and XQuery Serialization 3.1. The serialization specification defines output methods in XML, HTML, plain or formatted text and JSON. The specification returned to Working Draft to add an Adaptive serialization closer to industry practice for ad-hoc formatting of results. An extensive test suite is available. Learn more about the Extensible Markup Language (XML) Activity
The Web Application Security Working Group has published a Candidate Recommendation of Content Security Policy Level 2. This specification updates Content Security Policy, fine-tuning the existing policy options, and introducing a number of new mechanisms that site authors can use to mitigate the risk of content injection and related attacks. Major differences from Content Security Policy Level 1 may be found in Section 1.1 of the document.
With this publication, we move the earlier edition off the Recommendation Track to a Note (Content Security Policy 1.0) and invite implementers to share their experience with CSP Level 2. Learn more about the Security Activity.
W3C congratulates the IETF for the approval by the IESG of the HTTP/2 draft, which represents a major update on the core protocol of the World Wide Web. This new version of HTTP will allow better and faster Web Applications, and help reduce the gap between installable and Web applications. It will also boost interoperability and reduce the need for some existing performance “hacks.”
The Web Performance Working Group has published a Working Draft of Server Timing. This specification introduces Server Timing, which enables the server to communicate performance metrics about the request-response cycle to the user agent, and a JavaScript interface to enable applications to collect, process, and act on these metrics to optimize application delivery. Learn more about the Rich Web Client Activity.
The Second Screen Presentation Working Group has published a Working Draft of Presentation API. This specification defines an API to enable web content to access external presentation-type displays and use them for presenting web content. Learn more about the Ubiquitous Web Applications Activity.
Front End Developer - Javascript/HTML5/Angular/Backbone Techworld Australia THE most amazing culture Immediate start Sydney CBD This is an opportunity like no other!! The worlds largest search engine is on the hunt for a super talented Front End Developer to join them on an 11 month contract. You will join the creative ... |
Forex Magnates | IQ Option Delivers Own HTML5 Binary Options Platform With CySEC License Forex Magnates The current IQ Option platform is an HTML5 solution which is extremely powerful when compared to what's out there in the market. The company is delivering candlestick charts and a very smooth user experience differentiating it materially from the ... |
To Markup or to Markdown? Digital Book World Many digital publishers agree HTML5 is one of the best mediums not only for outputting ebook content but for authoring it, too. Personally, I'm not so sure. At this year's Digital Book World conference, I attended a panel session titled, “In Publishing ... |
W3C published the report of the W3C Workshop on Privacy and User– Centric Controls workshop held on 20-21 November 2014 in Berlin. This exploratory workshop attracted extensive participation, including browser vendors, researchers, network operators, entrepreneurs, and government representatives.The group recognized that issues related to implementing and achieving adoption related to privacy and security may be similar to those for accessibility and internationalization. The Workshop identified concrete next steps that will be brought to the attention of the Privacy Interest Group for further discussion. The Workshop was hosted by Deutsche Telekom and sponsored by the European Commission. Learn more about the Privacy Activity.
The Web Applications Working Group has published a Working Draft of Manifest for web application. This specification defines a JSON-based manifest that provides developers with a centralized place to put metadata associated with a web application. This includes, but is not limited to, the web application’s name, links to icons, as well as the preferred URL to open when a user launches the web application. The manifest also allows developers to declare a default orientation for their web application, as well as providing the ability to set the display mode for the application (e.g., in fullscreen). Additionally, the manifest allows a developer to “scope” a web application to a URL. This restricts the URLs to which the application can be navigated and provides a means to “deep link” into a web application from other applications. Learn more about the Rich Web Client Activity.
The Device APIs Working Group has published a Working Draft of Wake Lock API. This document specifies an API that allows web applications to request a wake lock. A wake lock prevents some aspect of the device from entering a power-saving state (e.g., preventing the system from turning off the screen). Learn more about the Ubiquitous Web Applications Activity.
The Timed Text Working Group has published a Working Draft of Timed Text Markup Language 2 (TTML2). This document specifies the Timed Text Markup Language (TTML), Version 2, also known as TTML2, in terms of a vocabulary and semantics thereof. Learn more about the Video in the Web Activity.
The Web Real-Time Communications Working Group and Device APIs Working Group have published a Working Draft of Media Capture and Streams. This document defines APIs for requesting access to local multimedia devices, such as microphones or video cameras. This document also defines the MediaStream API, which provides the means to control where multimedia stream data is consumed, and provides some control over the devices that produce the media. It also exposes information about devices able to capture and render media. Learn more about the Ubiquitous Web Applications Activity.
The Device APIs Working Group has published a W3C Recommendation of Vibration API. This specification defines an API that provides access to the vibration mechanism of the hosting device. Vibration is a form of tactile feedback. Learn more about the Ubiquitous Web Applications Activity.
The Web Real-Time Communications Working Group has published a Working Draft of WebRTC 1.0: Real-time Communication Between Browsers. This document defines a set of ECMAScript APIs in WebIDL to allow media to be sent to and received from another browser or device implementing the appropriate set of real-time protocols. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group and an API specification to get access to local media devices developed by the Media Capture Task Force. Learn more about the Ubiquitous Web Applications Activity.
The Web Real-Time Communications Working Group and Device APIs Working Group have published two First Public Working Drafts today:
Learn more about the Ubiquitous Web Applications Activity.
Getting Last Point on an ARC() and length of ARC()? HTML5 GameDev.net So I been playing around with this experiment and I am starting to realize how important math is for games. Its even more important then I realized before. =]. A snipplet, I didnt include vars context.beginPath(); context.arc(centerX, centerY, radius ... |
The language of mobile app development: native or HTML5? WhaTech Despite the progress in HTML5, most of the companies that Lopez Research interviewed still believe that native app development delivers the best experience. In 2015, most firms will deliver greater than 60 percent of their mobile experiences via a ... |
W3C today updated its General Document License to permit non-specification derivative works, such as inclusion of specification text in software, in supporting materials accompanying software, and in documentation of software. The license also makes all Code Components included in Specifications available under the W3C Software License. This update affects both upcoming publications, as well as existing publications, which are also now available under the new license.
The Web Applications Working Group has published a Working Draft of Service Workers. This specification describes a method that enables applications to take advantage of persistent background processing, including hooks to enable bootstrapping of web applications while offline. The core of this system is an event-driven Web Worker, which responds to events dispatched from documents and other sources. A system for managing installation, versions, and upgrades is provided. The service worker is a generic entry point for event-driven background processing in the Web Platform that is extensible by other specifications. Learn more about the Rich Web Client Activity.
Top Tech News | YouTube Dumps Flash, Now Defaults to HTML5 Video Top Tech News It might not be the "nail in the coffin" for Flash that some critics have called it, but YouTube announced Tuesday that it will now default to the HTML5 video player instead of Flash. The change will apply to viewers using Chrome, Internet Explorer 11 ... |
Reddo Leverages HTML5 to Allow Developers to Create New Mobile Front-ends ... App Developer Magazine This model is used to construct a reflected interface using responsive, cross-platform HTML5 controls. This reflection UI is created completely automatically. It looks and behaves like the desktop UI, but is comprised of actual HTML5 controls. As the ... |
Savision Previews New Free Mobile-Friendly HTML5 Dashboarding Solution at ... PR Newswire (press release) It provides customers with a fast, and fluid HTML5 based tool, including a free version, that can be easily customized using drag and drop functionality and viewed on any mobile device anywhere. Rob Doucette, CTO of Savision, commented "With the ... |
Infragistics Updated Development Platform Features WYSIWYG Web-based ... App Developer Magazine The platform features the Infragistics Indigo Studio interactive prototyping tool which can generate standards-based HTML5 and JavaScript with Infragistics Ignite UI controls, which can be further refined by the newly added WYSIWYG Page Designer for ... |
Flash is dead: YouTube drops Flash in favour of HTML5 TechRadar Adobe Flash was already on the way out, but YouTube just stabbed it in the heart by dropping it as a standard video delivery format in favour of HTML5. HTML5 has long been heralded as the natural successor to Flash, and it'll now be the default ... |
The Cascading Style Sheets (CSS) Working Group invites implementation of the Candidate Recommendation of CSS Counter Styles Level 3. It adds new built-in counter styles to those defined in CSS 2.1, but, more importantly, it also allows authors to define custom styles for list markers, numbered headings and other types of generated content. This Candidate Recommendation incorporates responses to all feedback received during the previous two Last Calls.
The Internationalization Working Group has also updated their Working Draft of Predefined Counter Styles, which provides custom rules for over a hundred counter styles in use around the world. It serves both as a ready-to-use set of styles to copy into your own style sheets, and also as a set of worked examples.
Learn more about the Style Activity and the Internationalization Activity.
The Cascading Style Sheets (CSS) Working Group has published a Working Draft of CSS Positioned Layout Module Level 3. This module contains the features of CSS level 3 relating to positioning and stacking of elements. It includes and extends the functionality of CSS level 2, which builds on CSS level 1. The main extensions compared to level 2 are the ability to position elements based on CSS Region boxes, the ability to specify different containing blocks for elements and sticky positioning. Other kinds of layout, such as tables, “floating” boxes, ruby annotations, grid layouts, columns and basic handling of normal “flow” content, are described in other modules. Also, the layout of text inside each line is defined elsewhere. Learn more about the Style Activity.
The Web Applications Working Group has published a W3C Recommendation of Server-Sent Events. This specification defines an API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events. The API is designed in a way that it can be extended to work with other push notification schemes such as Push SMS. Learn more about the Rich Web Client Activity.
In recognition of increased consumer demand for data and services in Connected Cars, W3C announced today a new automotive industry collaboration to bring drivers and passengers a rich Web experience. The effort, a new Automotive Working Group, will focus initially on giving application vendors standard and more secure access to vehicle data. “Connectivity is transforming the car industry,” said Matt Jones, Head of Future Infotainment at Jaguar Land Rover. “We believe the Web is the auto industry’s best path forward to keep up with rapidly changing consumer expectations and evolving technology, as well as addressing challenges such as over-the-air updates and advanced diagnostics.” Read more support from industry in the full press release.
