Re: xhtml 2.0 noscript

David,

The issue *is* an XML one.

document.write() is normally carried out as the document is loading,
by interspercing <script> elements within the normal mark-up. This
means that the *initial* document at the point of completion of the
'onload' event could be different when running in a browser with
script, and one without.

But with XML we really need to have the document fully loaded and
parsed before we can start manipulating it, which means that
document.write() doesn't mean anything.

So if XHTML doesn't have document.write(), then that means that
whatever mark-up you put into the body of your document you can
guarantee it will be the same after the 'onload' event regardless of
whether the browser has script turned on or off, or doesn't even
support script.

Of course, once the document has finished loading, further changes to
the DOM could be made using script, but the key point is that by this
time the 'base' or 'core' document has already been finalised, so were
script to be disabled or not supported, then this document would in
effect be the <noscript> option. (Which is what Steven said in his
earlier post on this.)

Regards,

Mark


On 29/07/06, David Dorward <david@dorward.me.uk> wrote:
>
> On Sat, Jul 29, 2006 at 10:01:15AM +0100, David Woolley wrote:
> >
> > > This is a browser support issue, not something required by the XML or
> > > XHTML specifications.
> >
> > It's a standards issue as well.
>
> But not a difference between HTML and XHTML.
>
> --
> David Dorward                                      http://dorward.me.uk
>
>
>
>


-- 
Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
http://www.formsPlayer.com/

Received on Saturday, 29 July 2006 13:21:41 UTC