IT's the Real Thing .....
"[Fire up the hookah, boys - Ed]" ..... ? :-) Very Transcandental.
The first major update to HTML in 10 years - factoring in changing tastes around rich-media applications and online collaboration - has been unveiled by the World Wide Web Consortium (W3C). The group has published the first public working draft for what it termed a "major revision" to the mark-up language. Much has changed …
"Members include Google, IBM, Microsoft, Mozilla and Nokia"
"HTML 5 is designed to inject more consistency into the ways vendors and end users have gone about building today's generation of sites"
Considering Microsoft's efforts to spoil / start and win a war on Open Document Standards, I think ratification of HTML 5 might happen around 2020 at the earliest...
HTML is complex enough and has grown far too much already. Scrap it. Why is it that any full featured web-browser is a huge behemoth, even the supposedly lightweight ones such as Opera or Firefox? HTML is so big, poorly structured and historically lenient of errors that any HTML parser is by necessity a sizable chuck of code in its own right.
Leave it to become obsolescent and upgrade XHTML and related standards instead. Provided the current lack of tolerance to mal-formed documents is preserved we have a much better chance of getting it right the second time around.
Who knows? We might even get a world wide web that actually works properly.
If they support the standard (standard, that is what we do, just ask us!), maybe IE will follow it (not bloody likely if you ask me).
The standard needs to say something like: If it is broken, you must reject it! Only then will you get standards based stuff.
Just makes more trouble for web developers, more browsers to support.
Please bring back plain text! (especially for email!). Gotta go now...
Wow, now we have to decide whether we should build our sites using HTML 5 or it's XHTML cousin. All sounds quite exciting!
I wonder when we will expect to see HTML 5 supported in user agents. I bet the Mozilla crowd get there before Microsoft. There! I have thrown down the gauntlet... :-)
Isn't (or shouldn't) XHTML more or less replacing html anyway? Why not just put old-fashioned html to bed altogether?
That objection aside, making more consistent a precise rules for recovering from parse errors is much-needed. Some of my web-design work has seen errors which Internet Explorer recovers from gracefully, and even produces the intended output, but which causes Firefox to just crash or go into an infinite loop.
My understanding is that HTML 5 is a fully XML compliant SGML rather than HTML 4.0 on speed. The major issue will be like with WAI 2, how much pointless "we want you to buy X" rubbish makes it into the final version. WAI 2 was watered down so much by companies with product to sell it was self defeating.
Unless the standard includes a requirement for servers to redirect semi-compatible (read: Intentionally incompatible) browsers to a standardized page listing actually compliant browsers, this will have exactly zero impact on cleaning up the mess with supporting pages for broken-by-design browsers.
The standard should also include requirements for compliant browsers to automatically reject pages that use proprietary extensions that is impossible for all browsers to render correctly. And no, I'm not talking about flash, I'm talking about garbage like ActiveX on pages.
Of course introducing such requirements for compliant products would mean Microsoft shafts this standard like they shafted the ODF group to create their own "standard", but since this is likely to happen anyway, I don't see the problem.
This post has been deleted by its author
I think its more of a case of Poor coding by people that dont know what they are doing and people doing websites in programs like word or front page
Not the HTML its self
"Who knows? We might even get a world wide web that actually works properly."
That will never happen since anyone can put up a site these days
Just as I thought we'd got a way from a messy, immature web and were moving to a more mature, clean, accessible web the W3C go and legitimise this awful standard.
Last thing we need is a new "HTML for children" standard to prolong the problems the web has suffered pretty much since it's creation. HTML5 puts even more of a burden on web browsers than any other HTML standard ever before and they couldn't get it right previously so how the hell can they be expected to get and even more messy, ambiguous spec right?
Rather than changing the standard to "fix" the Microsoft problem, why not sell an HTML 5 license for $10K together with a contract that says "if you don't pass this array of conformance tests you don't get to put the code into any public app".
And have a reference implementation.
OK, I'm dreaming, back to work.
I (could be wrong), but always thought that HTML was the language, and XHTML was just the way you should use it and put it together.
......HTML is the language, but XHTML is just the standard you should use when implementing it (bit like programming languages and design patterns).
Therefore with HTML 5, they will just update the w3c scheme to reflect the new elements, and therefore you have XHTML compliant HTML5.0
HTML 5 *is* XHTML which is an XML document type.
Being XML it is also Unicode, meaning that it is of course compatible with any text editor (was this a joke?).
As far as criticisms of W3C's standards work go, I find it extraordinary that the one organisation which has been consistent and successful in promulgating useful standards for the web should be subject to criticism on the basis of how others - browser vendors and SVG vendors - have responded in the marketplace. Adobe's decision to dump SVG was a commercial one, nothing to do with the standard's efficacy. And surely we all know by now that the problem with CSS 2 support was IE's implementation, IE-specific web development, and the commercial interests of browser developers in general.
Web users need to get behind W3C's efforts to ensure wide and full implementation of web standards, and stop moaning about issues that, apparently, half of us don't even understand.
It doesn't look like they've addressed one of the big bugbears of HTML/XHTML/CSS though; all the recommendations are not to use <table> for layout, but with current browsers its the only way to get a layout to work (yes I've tried <div> ing and <span> ing 'til the cows come home!).
They need to address layout by having a table-like set of tags that can be ignored/understood by non-visual user-agents (readers etc.)
Excellent idea: some sort of software patent held by W3C: patent based on DTD, licensing is conditional on the following terms:
1] If you support any part of the DTD, you must support it *all*
2] You must not support proprietary extensions of the DTD without prior approval from W3C, and without providing full documentation of those extensions, and an open licence for other implement same.
Any attempt to implement by M$ to implement a "lookalikee" standard (ODF / OOXML, anybody), will swiftly be batted down by a quick patent violation trial.
As for the new HTML 5 standard: I do hope this really is based in the real world, in contrast to some of the more outlandish thought processes that seemed to go into CSS 1 / 2... floated element clearing and element height / containment rules, for instance.
I'm just dreading the IE8/9 implementation... with IE5+ MS used their IE monopoly to deliberately mis-render CSS, forcing developers to code specifically for IE, thus making sites appear broken in other standards compliant browsers. If they do this with html 5, I'm going to beat monkey boy to death with a thin client!
Jesus, people: this isn't slashdot.
Are you writing through some kind of time rift from 1999? Have you upgraded your browser past Netscape Navigator 4? The problems of semantically clean cross browser design have been solved time and again in many different ways. Just look at a few web design sites or blogs and you will find hundreds of different solutions to the problem you're regarding as insurmountable.
Any wood turner could take a lathe and a set of chisels, put a decent piece of wood in and make something useful with it. I'm pretty sure I couldn't, but I'm not going to blame the lathe, chisels or wood for that.
If you'd *followed the link* in the article to the W3C page and scrolled down to the "Syntax" section, you'd have your answer. Here's the link again...
Ironically, HTML's great innovation was the link. It seems that some folks haven't "gotten it" yet. Still, it's only been twenty years.
"Web sites have moved from being a collection of static pages to media-rich communities leveraging participation."
Thanks for that - I'll be chuckling all day - -especially having just read the thread on Web 2.0.
Maybe it should read "Web sites have moved from being a collection of static pages to media-rich communities leveraging participation comprising of the old static stuff having Java thrown at it."
(does 'participation' mean 'sales'? by any chance)
I did a really beautiful site using CSS instead of tables for layout. I used the correct combination of absolute and relative positioning and everything. It looked absolutely gorgeous in Konqueror (my browser of choice), and only slightly less gorgeous in Firefox (mainly due to the latter jarring against my desktop theme; ignoring the window dressing, the site was how it was meant to look).
Why must Microsoft insist to behave differently from everyone else? If I asked for a background colour in a div, I expect the whole div to appear with that background colour. Like the standard says, and like Konqueror and Firefox do. Is that really so hard?
All web-related software is a huge pile of crap, that only ever seems to get bigger and crappier.
When he invented HTML and HTTP, Tim Berners-Lee was at CERN, surrounded by mathematicians and physicists. At least a significant proportion of these people must already have been using LaTeX. Yet after two decades, the typographical output of web browsers is still way inferior to what TeX could produce when Don Knuth first released it. I say that <i>even for plain text</i> - whilst there are very good programs like Hevea for translating a decent language (LaTeX) into HTML/CSS crap, the result on the web browser is still awful.
its another standard big deal,
to be fair might do some useful things like make an elegant way to embed flash in markup...
something like <flash src="some.swf" id"...
all id really want then is a simple 2d polygon generation in markup (just a circle would suffice) and vertical positioning that worked properly...
probably wishful thinking but never mind
<table> elements react to content.
<div> elements react to context.
The reason a site like El Reg would use <table> elements is because their content is king. It is supplied by a large number of authors and streams. Their layout must adapt to the content. They eschew tight layout control in favor of being able to deliver their content.
<div> elements control the layout rigidly, and allow content to do things like overflow display areas, etc.
It's quite possible to have this site use <div> tags, but then, they'd need an editor to act as "Kontent Kop," ensuring that all content fits within the layout.
Here's what I mean:
<div style="border:1px solid black;width:5em">Supercalifragilisticexpialidotious</div>
<table cellpadding="0" cellspacing="0" style="border:1px solid black"><tr><td style="width:5em">Supercalifragilisticexpialidotious</td></tr></table>
I don't think we need a new tag for tabular layout. We already have one. It's called "<table>," and it's one of the oldest, most well-understood and robust elements in the lexicon.
Technically he's got a point. Use DIVs and CSS as much as you like there is no way to have 2 DIVs the same height (without defining that height).
For example; you've got a menu on the left and content on the right with different coloured backgrounds - you want them both to be the same height no matter which has the "tallest" content.
Currently 2 columns in a table do this perfectly.
The only way to do it with DIVs is to put both in a "container DIV", give the container the background colour of say the "menu" and the "content" another background colour. Position the "menu" absolutely and give the "content" a "margin-left" the same width as the "menu".
Now, to make IE display the same as everything else you have to ensure there's no padding on the "menu" since IE pads opposite to the standard (in rather than out). Then nest another DIV inside that menu (width: auto) to sort your padding out. Still with me? It does work and there's less markup involved but it feels like a dirty hack and uses a lot of CSS.
However - this is all resolved in CSS3, so this is not really an HTML issue at all.
Anyway - after having read the HTML 5 spec... it looks like XHTML2 without the modularisation (forms for instance rather than moving to xForms). There is actually some good stuff on the way but personally, I think I'll just move to XHTML2/CSS3 when they've matured.
A lot of the work I do is with automatically generated content, and tables work great for that; however I still end up using <table> to lay out controls and forms, just like the form I'm filling in now!
the CSS properties for "display" (table, table-row, table-cell etc.) work fine in Firefox and Safari, and I can lay out <div> and <span> elements just like a table. But IE7 ignores them, just like the w3 specification says it can (http://www.w3.org/TR/REC-CSS2/tables.html). Works ok in Pocket IE though...
Anything that annoys the fanboys who've been mindlessly coding in XHTML for the last 5 years (or worse still, wasting time recoding existing HTML pages that display fine already to XHTML) without knowing *why* they were doing it - other than to copy/impress their 1337 cyberfriends - and then send them over HTTP as text/html is a good thing in my book.
I haven't had so much fun since Russell T Davis said the TV movie was canon and credited Christoper Eccleston as "Doctor Who" in the end titles.
Anyway, here's to hoping Firefox will pass the HTML4/CSS Acid2 test by the time HTML5 becomes a Recommendation...
This post has been deleted by its author
"They need to address layout by having a table-like set of tags that can be ignored/understood by non-visual user-agents (readers etc.)"
They have this: it's called the table tag. The table tag is brilliant for laying out content that is readable in a text-only browser. The key is to actually check your design in a text-only browser (or Opera's text browser simulation) as you develop it. That way nasties can be caught and fixed early. As an added bonus, this method avoids the unreadable vile bodge that is DIVs & CSS used to do little more than simulate tables.
I've heard rumours that frames have been dropped in HTML 5.0.
I know I could have a look at the spec meself, but I'm about to nip out for a paper, so I thought I'd harness the mighty opinionsphere that is the El Reg comments form instead.
If true, it will be a bit of a pain. I know tha tpurists rather look down on frames, but I do find them to be useful on occasion.
Note the following quote from the W3C statement of HTML 5 differences from HTML 4:
"The HTML 5 specification will not be considered finished before there are at least two complete implementations of the specification. This is a different approach than previous versions of HTML had. The goal is to ensure that the specification is implementable and usable by designers and developers once it is finished."
Biting the hand that feeds IT © 1998–2020