The W3C Navigation Timing specification provides a browser API and visibility into the timing and performance data behind the life of every request in the browser. Let's inspect the components, as each is a critical piece of delivering the optimal user experience:
Given the URL of a resource on the web, the browser starts by checking its local and application caches. If you have previously fetched the resource and the appropriate cache headers were provided ( Expires…
…they've stayed remarkably stable because that's the best way to prevent breakage. Like the W3C says: Cool URIs don't change . Which means this isn't much of a problem in the wild and even if it was, hypermedia APIs would still have big holes with direct links break.
Enabling discoverability
Good API docs explain what all the possible attributes of a resource are. They explain the possible values of those attributes. The options available and …
…magic image format ( mif) . How do we deploy it? As a recent bug on W3C points out , our markup provides no facility to specify different formats for a single image. Let's assume we add such mechanism. The syntax does not matter, I'll just make it up for the sake of an example:
<img srcset= "awesome.jpeg 1x, awesome.mif 2x" alt= "Use awesome MIF for retina screens!" >
So far, so good. The browser reads the page and decides to load the . mif …
to help coordinate cross-technology architecture developments inside and outside W3C
As Alex has said before , the existing web architecture needs reform that would make it more layered. We should be able to explain the declarative parts of the spec (like markup) in terms of lower level primitives that compose well and that developers can use for other purposes.
And the W3C must coordinate much more closely with TC39, the (very active) committee that is designing …
On November 18, 2010, the W3C made the decision to no longer support the standard. This was due to disagreement from a number of vendors - including Mozilla and Microsoft - on how it should be practically implemented and incomplete browser support. As a result, IndexedDB was introduced as an alternative standard for web data storage.
However, IndexedDB is not a browser database but an Object Store . It allows for applications to design, store and manipulate objects, without sterilization, …
In this week's news, we look at RUM, Node.js 0.8 and more.
* The Atlantic interviews the developers behind Obama's campaign website .
* Steve Sounders compares RUM and synthetic page load times .
* Node.js News reports on the performance improvements in Node.js 0.8.
* Slides from the November W3C workshop on web performance have been posted.
* Fresh Squeezed talks about web performance in their latest podcast.
…powerful future releases. Using tools like Sass or LESS will only help us get ready and force a future that is on its way. Vanilla CSS is sloppy and tedious in nature and the more people using pre-processors, the more pressure is on the W3C working group for CSS. As with anything, the fear of the unknown can be really strong. Stop fearing and start Sassing today! Take some insights from your peers and give it a go.
Selections are essentially the same as jQuery selectors, and defined by the W3C selectors API.
jQuery - select all paragraphs:
$ ( 'p' )
D3 - select all paragraphs:
d3. select ( 'p' )
In this way, D3 is declarative. Instead of manually finding and looping through arrays of DOM nodes, you specify what you want to operate on, then operate on the entire selection at once
Dynamic Properties
Styles, attributes, and other properties of the DOM can …
…There's some new "picture" element they're playing with in the standards bodies (the W3C?).
"Starting with the desktop may be an increasingly backwards way of thinking about a Web product." -- Luke Wroblewski
He said half of your users are mobile.
Opera is the most popular mobile browser world wide (I assume this refers to cellphones that aren't running Android or iOS).
He said QA is very important. You have to test on many different devices. …
…but are still in an early draft phase at W3C. They actually consist of two different W3C RFCs: The Shadow DOM and HTML Templates . When you combine those two dudes, the result is simply amazing: Imagine being able to write your own HTML elements or widgets, package everything what is needed for them ( HTML, CSS and even event handling JavaScript) together and be able to distribute those elements or widgets without having to even think about any side effects on the …