Showing and hiding content with HTML

Update Two Letters app with startup image and scroll recall at some point.

Good to know.

A boilerplate for body fonts and colors.

HTML video framework

Framework for making responsive websites.

Insane.

Interview talking about the future of JS and Flash on the web.

Something to refer next time I … wait, I never code emails. Something to point others too, I guess.

Position:fixed is the big one, but some nice iterative improvements as well.

For the next time I need to make an image scale.

Some good, general advice for the mobile web.

Tip for making HTML5 and Flash videos expand with the browser.

Synchronization problem's we'll face as the server is no longer the only location for application data but merely the canonical location.

"Documentistas would have it so. I can’t possibly build anything for the web without every piece of it being addressable like a document. Users must be able to deep-link into any docu state of my application. These URLs must return content to robots too – because where would we be without web crawlers? – and of course it all needs to degrade nicely for legacy browsers and screen readers. In fact, I may as well just fake the whole thing with server-side markup and progressive enhancement anyway. Many do."

Elliot Jay Stocks demos a technique for transition image sizes as the browser width varies.

Like most people, I imagine, I don't know what to think about URL syntax and client-side routing. I hope Jeremy and co. will sort it out.

Impressive web rendering demo (2:00). Bing Vision (4:15) looks hot. Live tiles are a great idea (6:10). Social activity integration and threads (8:45) look interesting, but not something I need. Ten minute video.

Consistently styled form elements across browsers.

Jamie Kasoy urges developers to group hug and work it out. I'm all for it, but it won't change anything. The Wheels of Progress are turning. (See my comment at the bottom. Read from the bottom up. The newest are on top. It threw me the first time.)

It's a shame Zeldman had to clarify what should have been perfectly clear from his original post on Flash and the iPad. That said, read it. He hits every major point that made me write my original post. (Furthermore, these facts are obvious and have been for quite some time. He and I were hardly the first to say them.)

Wondering why I even bother writing articles when people like Faruk are around to say it better.

Andy's right. Expecting the site to look the same in all browsers is rarely the client's perspective. Too often we introduce that requirement internally. It's beyond time to move on.

If only these hacks, hints, and tips weren't so necessary.

If hand-coding semantic markup for search engines and browsers that can't take advantage of it is your thing, Jeremy Keith's got a tempest in a teapot just for you.

Jeff slams microformats, then admits he's using them anyway. I sympathize.

iTunes Extras using web technologies

«In the following table, Quirks Mode, Standards Mode and Almost Standards Mode are denoted by Q, S and A, respectively. When a browser only has two modes, the Standards Mode is marked as “S”, if the line height in table cells works as in Mozilla’s Standards Mode, and as “A”, if the line height in table cells works as in Mozilla’s Almost Standards Mode.»

On this page I compare 19 WebKits in order to prove that there is no “WebKit on Mobile” and to figure out which one is the best. My hope is that eventually I’m going to gain some insight in the “family tree” of all WebKits.

"The package, called SVGWeb, consists of some javascript and an SWF (Flash) file. Thankfully, this is not an API, and there is no custom language or function calls to use it . You simply put your SVG content in your page as you would normally would (in a perfect world), and include the JS library which will detect if the browser has native SVG support or not. If it has support, it will essentially do nothing special. If it doesn't (IE), SVGWeb will take over and use Flash."

"We’ve had a number of people asking about templates, boilerplates and styling for HTML 5 so to give you all a helping hand and continue on from those basic building blocks that Remy talked about last week I’ve created a HTML 5 reset stylesheet for you to take away and use, edit, amend and update in your projects."

"To the extent that W3C specifications remain modular, practical, and accessible to the non-PhD in computer science, they will be adopted by browser makers and the marketplace. The farther they depart from the principles Bert articulated, the sooner they will peter out into nothingness, and the likelier we are to face a crisis in which web standards once again detach from the direction in which the web is actually moving, and the medium is given over to incompatible, proprietary technologies."

"Did you ever want to resize a video on the fly, scaling it as you would an image? Using intrinsic ratios for video, you can. This technique allows browsers to determine video dimensions based on the width of their containing block. With intrinsic dimensions, a new width triggers a new height calculation, allowing videos to resize and giving them the ability to scale the same way images do."

More on why HTML > XHTML

I'm convinced. All past projects have been coded in XHTML 1.0 Transitional. Henceforth, it's going to be HTML 4.01 Transitional or bust.

If it wasn't obvious already, <canvas> has a lot of potential.

Using (css) tables for layout.

No, they shouldn't.