Craig Grannell from .Net magazine got in touch to ask me a few short questions about last week’s events around HTML5. I thought I’d share my answers here rather than wait for the tortuously long print release cycle. What are your thoughts on the logo? The logo is nice. Looks pretty sharp to me. Why were you unhappy with W3C’s original stance (“general purpose visual identity”)? … Read the rest here
Two good things have happened. WHATWG Firstly, as I hoped , the WHATWG have updated the name of their work to simply be HTML . This is something they tried to do a year ago , and I kicked up a stink. I was wrong. Having a version number attached to an always-evolving standard just doesn’t make sense… Read the rest here
Webmonkey: HTML5 Gains Logo, Loses Meaning It doesn’t really matter if the New York Times thinks CSS 3 or SVG are HTML5, but we’d like to think that at least the organization in charge of describing what is, and is not, HTML5 would make some effort to distinguish between tools. Lumping everything together is as silly as a carpenter referring to every tool in their toolkit as “a hammer.” CNET News: W3C’s new logo promotes HTML5—and more Curiously, though, the standards group—the very people one might expect to have the narrowest interpretation of what exactly HTML5 means—instead say it stands for a swath of new Web technologies extending well beyond the next version of Hypertext Markup Language. GigaOM: The Truth Behind HTML5′s New Logo Fiasco It’s as if the government suddenly announced that from today, all vegetables will be called potatoes, just because some vegetables are potatoes. The Register: W3C tackles HTML5 confusion with, um, more confusion And much like Apple, Google, and Microsoft before it, the organization that oversees HTML5 has confused it with all sorts of other web standards. The Web Standards Project: HTML5 logo: be proud, but don’t muddy the waters! Now the W3C has come out and essentially condoned the branding of everything from CSS to actual HTML5 to WOFF as “HTML5”. We can’t imagine a single action that will cause more confusion than this misguided decision (and the W3C has produced some pretty impenetrable specs in its time) Roger Johansson: HTML5 now includes CSS3, SVG and WOFF? … Read the rest here
Webmonkey: HTML5 Gains Logo, Loses Meaning It doesn’t really matter if the New York Times thinks CSS 3 or SVG are HTML5, but we’d like to think that at least the organization in charge of describing what is, and is not, HTML5 would make some effort to distinguish between tools. Lumping everything together is as silly as a carpenter referring to every tool in their toolkit as “a hammer.” CNET News: W3C’s new logo promotes HTML5—and more Curiously, though, the standards group—the very people one might expect to have the narrowest interpretation of what exactly HTML5 means—instead say it stands for a swath of new Web technologies extending well beyond the next version of Hypertext Markup Language. GigaOM: The Truth Behind HTML5′s New Logo Fiasco It’s as if the government suddenly announced that from today, all vegetables will be called potatoes, just because some vegetables are potatoes. The Register: W3C tackles HTML5 confusion with, um, more confusion And much like Apple, Google, and Microsoft before it, the organization that oversees HTML5 has confused it with all sorts of other web standards. The Web Standards Project: HTML5 logo: be proud, but don’t muddy the waters! Now the W3C has come out and essentially condoned the branding of everything from CSS to actual HTML5 to WOFF as “HTML5”… Read the rest here
One year ago, I objected strenuously when the WHAT WG temporarily changed the name of their spec from “HTML5” to plain ol’ “HTML”: Accurate as that designation may be, I became very concerned about the potential confusion it would cause. I understand why the WHATWG need to transition from using the term HTML5 to simply using the term HTML to describe their all-encompassing ongoing work, but flipping that switch too soon could cause a lot pain and confusion. Now that term the “HTML5” has become completely meaningless— even according to the WC3 —I think it’s time to rip off the bandaid and flip that switch. I was wrong. Hixie was right. The spec should be called HTML … Read the rest here
One year ago, I objected strenuously when the WHAT WG temporarily changed the name of their spec from “HTML5” to plain ol’ “HTML”: Accurate as that designation may be, I became very concerned about the potential confusion it would cause. I understand why the WHATWG need to transition from using the term HTML5 to simply using the term HTML to describe their all-encompassing ongoing work, but flipping that switch too soon could cause a lot pain and confusion. Now that term the “HTML5” has become completely meaningless— even according to the WC3 —I think it’s time to rip off the bandaid and flip that switch. I was wrong. Hixie was right. The spec should be called HTML … Read the rest here
The W3C unveiled a new logo and branding strategy today. (You might have heard.) It brings all the deliciousness of a Soviet-era Transformers logo to the yummy conflation of several related technologies! Did you get your WOFF in my HTML, or did I get my CSS all over your HTML? As per usual, a lot of people have said a lot of things about this. For my part, I figure, hey, given that CSS3 is now a branded part of your nutritious HTML5 breakfast, why not go with the flow? … Read the rest here
:toggle : A lovely toggle button demo by simurai using only HTML5 and CSS3. All it needs now is a badge. /via CSS3 Watch … Read the rest here
W3C Introduces HTML5 Logo : Wait, is it April 1? Is this for real? Apparently so. Here’s the official word from W3C and the design notes from Ocupop . … Read the rest here
The W3C have unveiled a logo for HTML5 . I’m not sure the world needs such a logo, but I think it looks pretty good. It reminds me of some of the promotional materials used by the Web Standards Project back in the day—simple bold lines that work well at small sizes, with a whiff of Russian constructivism. But I take issue with the scope of what this logo is supposed to represent. From the Frequently Asked Questions : The logo is a general-purpose visual identity for a broad set of open web technologies, including HTML5, CSS, SVG, WOFF, and others. What. … Read the rest here
The W3C have unveiled a logo for HTML5 . I’m not sure the world needs such a logo, but I think it looks pretty good. It reminds me of some of the promotional materials used by the Web Standards Project back in the day—simple bold lines that work well at small sizes, with a whiff of Russian constructivism. But I take issue with the scope of what this logo is supposed to represent. From the Frequently Asked Questions : The logo is a general-purpose visual identity for a broad set of open web technologies, including HTML5, CSS, SVG, WOFF, and others. … Read the rest here
Hey, any interest in spending a few days in a luxury lodge in the Great Smoky Mountains this coming spring with me and Aaron Gustafson, learning about and working with HTML5 and CSS3? Then you might want to sign up for Retreats 4 Geeks: HTML5 & CSS3 in the very near future, because it was announced late yesterday and as of now there are only six spots still available. It’ll be a very focused two days of training and a day of hands-on project work with a very small group of people, and it’ll be a ton of fun! Personally I’m looking forward to this for many reasons, but two stand out: this sort of very-small-group training and team project work setup is a new thing for me, and it’s the sort of thing I’ve thought about doing on and off for more than a decade but never quite found the time to do. Aaron, thankfully, did find the time and I’m honored that he asked me to take part. I hope I’ll see some of you this April in Tennessee! … Read the rest here
HTML5 Mania : A gallery of sites using HTML5. … Read the rest here
HTML5 Mania : A gallery of sites using HTML5. … Read the rest here
One of the many form enhancements provided by HTML5 is the datalist element . It allows you to turn a regular input field into a combo-box . Using the list attribute on an input , you can connect it to a datalist with the corresponding ID. The datalist itself contains a series of option elements. <input list=”suggestions”> <datalist id=”suggestions”> <option value=”foo”></option> <option value=”bar”></option> <option value=”baz”></option> </datalist> I can imagine a number of use cases for this: “Share this” forms, like the one on Last.fm, that allow you to either select from your contacts on the site, or enter email addresses, separated by commas. … Read the rest here
One of the many form enhancements provided by HTML5 is the datalist element . It allows you to turn a regular input field into a combo-box . Using the list attribute on an input , you can connect it to a datalist with the corresponding ID. The datalist itself contains a series of option elements. <input list=”suggestions”> <datalist id=”suggestions”> <option value=”foo”></option> <option value=”bar”></option> <option value=”baz”></option> </datalist> I can imagine a number of use cases for this: “Share this” forms, like the one on Last.fm, that allow you to either select from your contacts on the site, or enter email addresses, separated by commas. Using input type=”email” with a multiple attribute, in combination with a datalist would work nicely… Read the rest here
A few changes for beta 2 of the updated reset, presented here: /* http://meyerweb.com/eric/tools/css/reset/ v2.0b2 | 201101 NOTE: THIS IS A BETA VERSION (see previous line) USE WITH CAUTION AND TEST WITH ABANDON */ html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video { margin: 0; padding: 0; border: 0; font-size: 100%; font: inherit; vertical-align: baseline; } /* HTML5 display-role reset for older browsers */ article, aside, details, figcaption, figure, footer, header, hgroup, menu, nav, section { display: block; } body { line-height: 1; } ol, ul { list-style: none; } blockquote, q { quotes: none; } blockquote:before, blockquote:after, q:before, q:after { content: ”; content: none; } table { border-collapse: collapse; border-spacing: 0; } First, the small changes: adding embed , output , and ruby to the first rule. I went back and forth on these quite a bit, which is why they weren’t in the first cut. However, none of them seem to be replaced so they’re in. Others, such as command , are replaced and so stay out for the same reason that form inputs are left out. ( img is a special case.) The HTML5 element I’m still stuck on is datalist , which seems sort of replaced but then again maybe not. I’m really close to including it on the same grounds that I include canvas , but it’s hard to know if that’s a good idea… Read the rest here
David made a comment on Twitter about some markup he was working on: Feels dirty setting id’s on main HTML5 page header and footer, but overriding inheritance they cause seems needlessly laborious. I know the feeling. I don’t like using IDs at all, unless I want part of a document to be addressable through the fragment identifier portion of the URL. While I think it’s desirable to use the id attribute to create in-document permalinks, I don’t think it’s desirable to use the id attribute just as a styling hook. … Read the rest here
David made a comment on Twitter about some markup he was working on: Feels dirty setting id’s on main HTML5 page header and footer, but overriding inheritance they cause seems needlessly laborious. I know the feeling. I don’t like using IDs at all, unless I want part of a document to be addressable through the fragment identifier portion of the URL. While I think it’s desirable to use the id attribute to create in-document permalinks, I don’t think it’s desirable to use the id attribute just as a styling hook. Its high specificity may seem a blessing but, in my experience, it quickly leads to duplicated CSS… Read the rest here
Here’s what’s on my desk at work: an iMac (with keyboard, mouse and USB cup warmer), some paper, pens, a few books and an A4-sized copy of Paul Downey ’s The URI Is The Thing —an intricately-detailed Boschian map of all things REST ful. It’s released under a Creative Commons license, so feel free to download the PDF from archive.org , print it out and keep it on your own desk. I love good URL design. I found myself nodding vigorously in agreement with just about every point in this great piece on URL design : URLs are universal . … Read the rest here