Hello standardistas,
I just published a page with the new Google pages service and I
would like to share it with you all:
http://sirokai.googlepages.com/home
If you do a view source you will see some pretty bad markup. An XHTML
1.0 Strict doctype with invalid nesting and font tags. Seems like a
Christian Montoya wrote:
http://sirokai.googlepages.com/home
If you do a view source you will see some pretty bad markup. An XHTML
1.0 Strict doctype with invalid nesting and font tags.
No surprises there...
Welcome to the future
...It will look a lot like the past, I'm afraid.
Gunlaug Sørtun wrote:
Neither Google, nor most of those who might use that or similar
services, care all that much about XHTML - or any other standard.
Now, which Task Force over at http://www.webstandards.org/ should take
on the task of fixing this Google service? Should keep any Task Force
Ian Anderson wrote:
Gunlaug Sørtun wrote:
Neither Google, nor most of those who might use that or similar
services, care all that much about XHTML - or any other standard.
I think this is a little harsh.
Ok ;-)
I tend to be quite pessimistic after having seen the results of many
such
On 2/23/06, Ian Anderson [EMAIL PROTECTED] wrote:
Gunlaug Sørtun wrote:
Neither Google, nor most of those who might use that or similar
services, care all that much about XHTML - or any other standard.
Now, which Task Force over at http://www.webstandards.org/ should take
on the task
I've worked with a number of JS browser based HTML editors, I'm
integrating TinyMCE with an existing web app at the moment.
In my experience the authors of these JS HTML editors actually have
very little control of the code produced by these editors as it
relies heavily on HTML related
