16 April 2014

The Ruby Reflector

Topic

World Wide Web Consortium

  Source Favicon
Email

W3C Method ( Working Draft )

Ex: Pure red would have a W3C lightness of 76 ( 0.299 normalized).

sRGB Luma ( Rec. 709 )

Ex: Pure red would have a lightness of 54.2 ( 0.21 normalized).

Using Weighted Euclidean Distance in 3D RGB Space

This method is not official, but it has been reported that it produces better results than the above two:

Ex: Pure red would have a lightness of 125.1 ( 0.49 normalized).

Tests

In order to determine which of …

robots.thoughtbot.com Read
  Source Favicon
On ZURB 6 months ago.
Email

…years later, the stylesheet was introduced in the HTML4 specification along with the W3C Validator service. The service was designed to help people generate syntactically accurate markup in both HTML and CSS. It worked. In the early 2000s validation symbolized professionalism among web developers. Everyone had the badges on their page. Everyone was drinking the validation kool-aid.

Validation Is No Longer Useful

Over the past five or so years our web development workflows have begun …

zurb.com Read
  Source Favicon
Email

How to use the W3C Geolocation and Google Geocoding APIs to reverse-geocode at a browser level

How to speed up responses with caching

How to test virtually every aspect of the app as it's built

Includes the source code of a Rails app with easy to read code and high performing geospatial queries

The book includes a fully functional Rails application written in Rails 4 and Ruby 2 with a full test suite of RSpec acceptance tests (using Capybara), unit tests, and CoffeeScript

robots.thoughtbot.com Read
  Source Favicon
By wycats of Katz Got Your Tongue? 11 months ago.
Email

Alex Russell posted some thoughts today about how he wishes the W3C would architect the next version of the Content Security Policy.

I agree with Alex that designing CSP as a "library" that uses other browser primitives would increase its long-term utility and make it compose better with other platform features.

Alex is advocating the use of extensible web principles in the design of this API, and I wholeheartedly support his approach.

Background

yehudakatz.com Read
  Source Favicon
On igvita.com 1 year ago.
Email

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

igvita.com Read
  Source Favicon
By David of Signal vs. Noise over 1 year ago.
Email

…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 …

37signals.com Read
  Source Favicon
On igvita.com over 1 year ago.
Email

…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 …

igvita.com Read
  Source Favicon
By wycats of Katz Got Your Tongue? over 1 year ago.
Email

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 …

yehudakatz.com Read
  Source Favicon
By Leigh Shevchik of New Relic over 1 year ago.
Email

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, …

newrelic.com Read
  Source Favicon
By Leigh Shevchik of New Relic over 1 year ago.
Email

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.

newrelic.com Read