PUBLIC MARKS with search define

The component model for the Web (aka Web Components) consists of four pieces designed to be used together to let web application authors define widgets with a level of visual richness not possible with CSS alone, and ease of composition and reuse not possible with script libraries today.

A precursor to Alexander’s A Pattern Language, in which he and Chermayeff define what’s wrong with the design of the suburbs, and outline the principles behind a more human (and urban) environment. As interesting for its approach to the problem as it is for any of the proposed solutions.

The Web is not HTML, CSS, and JavaScript. It's not DOM, SVG, WebGL, PNG, or Flash. The Web is really just HTTP over TCP/IP. What gets transported over HTTP does not define the Web. There is, however, one other characteristic that does define the Web, and that is the humble hyperlink.

Observing this gives me all the more sympathy for bodies like the W3C et al who kill themselves trying to define standards for things that to many people are still profoundly arcane abstractions (but as we see, are very real, very affective.)

We are working with Mozilla to define a common approach to solving the challenges that web integrators face today. We are interested in hearing your thoughts and we are still thrashing out the API so bits of it might change but the intent is still the same.

If you define an “HTML5 browser” as one that supports all features of HTML5 then there are precisely zero in existence. (You’d need to define “HTML5″, of course, but that’s another story.)

Huhu

The truth is that browser manufacturers are driving it collaboratively because if browsers don’t render HTML interopably, developers will use some proprietary technology instead.

La vérité c'est que les développeurs visent Apple Webkit aka "néo IE6" (utilisé dans Apple Safari et Google Chrome / Chromium), et essaient d'être compatible avec le reste derrière, avec en compatibilité prioritaire Mozilla Gecko (utilisé dans Mozilla Firefox...). C'est comme ça que voyages-scnf.com est un site Web, alors que capitainetrain.com est un site Webkit. Ou alors, c'est parce que les développeurs web les plus audibles sont des macqueux, et ils ont oublié au passage ce qu'était l'interopérabilité (One Browser, One OS, One Store).

As I realize that open source is going to define my professional life (and

likely my personal one as well), my tolerance for assholes gets smaller and

smaller.

What do we do for browsers that don't support rem units? We can specify the fall-back using px, if you don't mind users of older versions of Internet Explorer still being unable to resize the text (well, there's still page zoom in IE7 and IE8). To do so, we specify the font-size using px units first and then define it again using rem units.

html { font-size: 62.5%; } body { font-size: 14px; font-size: 1.4rem; } /* =14px */ h1 { font-size: 24px; font-size: 2.4rem; } /* =24px */

Oct 04, 2010

karlpro said...

HTTP gives you a way to handle the right user (agent) interaction. In the discussion there is a missing piece above. What is the URI? The HTTP code will give information about a URI and its evolution in time. For a user agent, is it a fixed one or temporary one? I'm surprised you didn't use a 307 Temporary Redirect. The information accessible at this URI is not accessible anymore, you can send the client to another URI with with an Expire field, with the information that the client has reached its limits and should retry the original URI in xxxx minutes. What is happening on the server side, machine limits, disks, etc. is *not* important and not part of the exchange of messages. Think about what is useful for going to the next meaningful interactions in terms of messaging (for a human or a software).Note also that HTTP WG is at work to define HTTPbis and it is the right time to have contributions of people who have real implementations issues. I would encourage you to send an email to the HTTP Working Group at ietf-http-wg@w3.org with the link to this blog post and an introduction.The draft documents are available at http://tools.ietf.org/wg/httpbis/