Apple, Opera, and Mozilla Push For HTML5

foo fighter writes "The World Wide Web Consortium (W3C) has been slumbering the past several years: HTML was last updated in 1999, XHTML was last updated in 2002, and no one is taking seriously their largely incompatible work on 'next-generation' XHTML or 'modularized' XHTML. Both HTML and XHTML are in sorry need of removing deprecated items while being updated to reflect the current practices of web and browser developers and remaining compatible with legacy Recommendations. The much more open and transparent WHATWG (Web Hypertext Application Technology Working Group), formed in 2004 to address this problem, and has been hard at work on developing a draft spec for HTML5 to update and replace legacy versions of both HTML and XHTML. The quality of this work has reached the point that Apple, Opera, and Mozilla have requested the adoption of HTML5 as the new 'W3C Recommendation' for Web development."

Comments

Update CSS not XHTML/HTML

[oliverthered]

What we need is an updated version of CSS that lets you do things like reference other elements attributes so that you can create tables and line up things across/down the page. The ability to put different images on the left and right hand sides and top and bottom and all variants off would be great for putting rounded corners on things etc... instead of having to do hacks link putting in extra p tags just for the image.

HTML is more or less fine, give me a better version of CSS anyday.

Re:Update CSS not XHTML/HTML

[drinkypoo]

IMO what we really need in CSS is variables and math. Variables are really key. And to be able to say that the width of an element is n% of the width of another element, even when it is not nested within that elements, is also key - otherwise you have to use javascript for assloads of things. Of course other similar things would be possible. This is absolutely critical. Without it CSS makes life harder in a disturbing number of situations.

Re:Update CSS not XHTML/HTML

[richdun]

Some of that is in the CSS3 and further specs, like the advanced layout module, but those are beyond the reach of even the latest versions of FF, Opera, KHTML, etc. at the moment.

But, really, XHTML 1.1 is a great standard, and instead of moving ahead, let's try to get everyone to use it first. It hasn't been updated in forever (forever in web terms, of course) because the push has been to get everyone to actually use standards, and to get browser support of CSS2 and eventually CSS3 complete across all platforms and engines.

Just glancing over it, the HTML5 standards up at WHATWG worry me slightly. There seems to be a lot fo presentational/non-structural markup sneaking back in. Not necessarily as obvious as some of the older tags that were dropped in HTML4/XHTML1, but still. We have to keep in mind the separation of powers - XHTML/HTML for markup, CSS for presentation, and DOM for scripting - or things will just get way too complicated again.

Make things easier and more accessible for the developer/design? Sure. Add presentational content to HTML so he/she doesn't have to learn how to properly use CSS and the DOM? No. Do this, and it'll open the floodgates for everyone (MSFT) to add "special" tags to further "help" the developer/designers. Next think you know we'll be running around with a bunch of "Works best in ..." graphics like its 1998 again (only this time we'll be using PNGs or JPEG2000s instead of GIFs).

Re:The More they add, the less I like

[Bogtha]

I actually find things like "normal <B>bold <I>bold italic</B> italic</I> normal" useful

I hate to break it to you, but that's not HTML 4.01 Transitional either. No version of HTML has permitted overlapping elements in the way that you describe. You are merely exploiting error handling that is fairly common amongst web browsers.

Re:The More they add, the less I like

[Bogtha]

It's like watching people program without a care about optimizing for size or speed. They're paid by the hour, not for the quality of the code.

Funny, that's how I feel about people who don't use CSS. Seriously, if you are that concerned with the size of pages and bandwidth, like you say in your other comment, then why are you transmitting your style information on every single page load?

Re:The More they add, the less I like

[nine-times]

I don't really get your complaint. I mean, I share your annoyance with uselessly flashy pages, and literally Flash-y pages, but what's wrong with refining standards? Many of the updates to HTML have made things cleaner, more precise, and more consistent. Some of the added features have allowed web developers to do more with less code (if you can call HTML "code"). Much of what's added in-- if you don't want to use it, don't use it. But if you have some reason to do something flashy on your site, it's probably better to have it be done in some standard way rather than though some hack or by adding Flash to your page.

Re:The More they add, the less I like

[Bogtha]

You prefer writing little-stupid javascript functions to just putting a :hover rule in your CSS?

I get the impression he's not a professional web designer, so he can just ignore stuff like that entirely.

HTML 3.2 is really the only standard the most browsers agree upon

There's a very good reason for that. The W3C were working on HTML 3 when it became apparent that their work was diverging from what browsers understood; browser vendors were adding stuff at a crazy rate while ignoring the HTML 3 work. So the W3C decided to scrap HTML 3 and make a decent description of what browsers understood in HTML 3.2.

Basically, the reason why "most browsers agree upon HTML 3.2" is because HTML 3.2 was merely rubber-stamping what browsers already did.

IE6/7 have all those weird box model problems with XHTML 1.0

There's no such thing as a "box model" in XHTML 1.0. The box model is a feature of CSS.

Forget HTML, it's CSS that's Broken, deal with it

[StreetFire.net]

I WANT A REAL LAYOUT LANGUAGE!!!!!!!!

I've tried, I really have, to embrace the Zen garden Juu-Juu of CSS, can you make a simple blog page work in CSS? sure! Can you make an massive website with many different templates and variable width data-areas work in CSS? Yea, if you're a complete lunatic. but you have to get there with hack over hack over hack over hack. Here is the deep dark secret of CSS, it's not designed for layout. It's fantastic for styling, but try doing a Box-model or Float layout and you quickly realizing you're asking CSS to do things it wasn't intended to do, and it simply does not break gracefully the way a simple table layout does (You know floats were originally intended for pictures, not layout areas). So while I respect the purity of a CSS for style, HTML for content concept, in practice CSS is just as much of a kludge as Table design. I've saved hours of time and reached wider audiences of compatibility by going for a hybrid design, but this breaks the "standards".

IMO, standards should follow simple elegant solutions, a hundred lines of CSS browser compatibility code and float hacks is far from an elegant solution. PLEASE PLEASE PLEASE give designers a proper layout language!!

Re:Today is NOT a good day to die.

[drix]

Meh. First, you're talking gross. What's his margin on those $1600 worth of orders? If it's "standard" retail, let's say 5%. So $80 bucks a day. Now, how much extra time and effort did it take you, the developer, to support browsers that are almost a decade old and that, by your own admission, affect roughly 2% of the userbase? My guess is at least a couple thousand dollars, unless you adopted a lowest-common-denominator approach, in which case the site must look unappealingly 1997. More importantly, what sort of tradeoffs were you forced to make? Have you studied at all how much business your client is forgoing by not leveraging the current "formatting fanciness"? Here are a couple points to consider.

1. People like sites that are clean looking and easy to use. Marketing studies have consistently shown that people will pay more for the exact same item from a place that sells it in a more aesthetically pleasing manner. (I'm not saying this can't be done with HTML 3.2 or whatever, but it's much harder.)
2. Standards-compliant sites that use semantic markup place higher in search engines, netting more impressions and more sales.
3. Table-based layouts are slow and unresponsive. How many people here remember good old NS 4 sitting there blank-faced, cranking away on the old, complicated table layouts of yore. I do. Responsiveness is huge; people have come to expect it as the rule, not the exception--a marked departure from the dark days of IE5 and NS4.