On Feb 15, 2010, at 11:38 PM, David Kirkby wrote:
On 16 February 2010 07:25, William Stein <[email protected]> wrote:
On Mon, Feb 15, 2010 at 10:54 PM, David Kirkby <[email protected]
> wrote:
On 16 February 2010 06:31, William Stein <[email protected]> wrote:
To Dana -- you might want to try Firefox if possible -- that's
what us
dev's use the most, so it is the most reliable for using the
notebook.
Just to emphasize this, note that I think right now everybody who
has done much work on the notebook in the last few months is using
Linux, and Safari isn't available on Linux, so Firefox as a
notebook
client tends to be more well tested.
-- William
It might help if the notebook produced valid HTML. The last time I
checked, with the online W3C validator
http://validator.w3.org/
the notebook was not producing clean HTML file. There are several
browers in semi-common use now
* Internet Explorer
* Firefox
* Safari
* Google Chrome
By producing valid HTML, the notebook should work with any of them.
I'm guessing you haven't done much AJAX programming. The notebook
involves many thousands of lines of Javascript (much in third party
libraries like jsmath, jquery, TinyMCE, etc.). There is much more
going on than just HTML.
But the browser does not see what generates the code
No, it's AJAX--the javascript itself that's doing the code generation
(or, often, generating the DOM directly with no intermediate HTML at
all). Unlike HTML (pick your flavor), javascript is still stuck in the
murky world of being defined by what browsers can do rather than
coding to the specs (and if one sticks to the parts that are well
defined and consistent across browsers, that's too small of a subset
to do much of interest).
- only that the document claims to be HTML 4.01 strict, but it is not.
Having the HTML that the notebook server generators be valid would be
nice. However, doing so isn't going to ensure that "the notebook
should work with any of them". I wish it were so simple.
-- William
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
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
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
