[whatwg] Thoughts on HTML 5

Giovanni Campagna scampa.giovanni at gmail.com
Tue Dec 16 06:38:44 PST 2008

2008/12/16 Nils Dagsson Moskopp <
nils-dagsson-moskopp at dieweltistgarnichtso.net>

> It is not hard to reject input if its not well-formed. If browsers can
> do it, why shouldn't web apps be able to ?
Browser assume that author knows XML because he's put an application/*+xml
mime type.
On the other hand, this assumption cannot be done for blogger, who aren't
expected to know XML / XML 1.1 / XHTML 1.0 / HTML5 specs (they're not
expected to know about what or w3c either)

> As I said, invalid input should be rejected in the first place. When I
> write a blog post, I usually catch errors like this when I click on the
> "preview" button and its all yellow.

two way to implement:
- server-side checking: every input from user is checked to be well-formed
Can you imagine what a blogger can think when the web page reports:
> Could not save you post, invalid XML markup (Mismatched end tag, expecting
<img>, found </p>)
> See W3C XML1.1 specification (link to  XML spec) for further information
about this.
Or just "Not well-formed (attribute values must be encoded in double
It is difficult to understand and debug for an experienced web designer,
guess for a casual poster
- client-side checking (the all-yellow page you mentioned)
The browser says "Not well formed" (this is what Firefox and Opera
generically say)
You know what it means and you open the source code. Then you find an
unencoded ampersand... And then?
You have no page, thus no way to edit!
Giovanni Campagna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20081216/0df40076/attachment-0001.htm>

More information about the whatwg mailing list