Robert Bradshaw wrote:
On Feb 15, 2010, at 11:38 PM, David Kirkby wrote:
But invalid web pages are quite likely to cause different behaviour
with different browsers, which can not be a good thing given there at
least 4 browsers in common use today.
Works for google: http://validator.w3.org/check?uri=http%3A%2F%2Fgoogle.com
Yes, Google is a well known example of a site that does work properly, despite
invalid HTML. But Google has the advantage over Sage, in that anyone making a
browser is going to test it works with Google, whereas they are far less likely
to test it with Sage.
There is so much more going on with an AJAX app than the HTML that the
success or failure of validating the HTML alone has little meaning.
- Robert
It can not help a browser render something properly if the HTML is invalid. It
may or may not be the cause of the observed problems. I realise you can take a
perfectly valid HTML page, with bad scripts, which validates as HTML, but does
not function as desired.
Dave
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
