ok so all my clientside

netsperience — Mon, 30 Jun 2008 21:46:33 +0000

ok so all my clientside methods are neutered

what about PHP? Lassoscript?

(I actually work sometimes on a Lassoscript site)

and I found this:

Gecko implementation of createElement doesn't conform to the DOM spec for XUL and XHTML documents: localName and namespaceURI are not set to null on the created element.

DOM methods include

webwiz — Mon, 30 Jun 2008 04:25:07 +0000

DOM methods include document.createElement, node.appendChild, and so on.

You can't use innerHTML when serving XHTML as an XML MIME type either. Sorry.

aha the W3C recommends that

netsperience — Sat, 28 Jun 2008 00:51:26 +0000

aha

the W3C recommends that the dynamic scripting achieved in HTML with document/write() be managed with DOM in XHTML

http://www.w3.org/MarkUp/2004/xhtml-faq#docwrite

I suppose this means changing innerHTML values on the fly?

What situation would the

webwiz — Wed, 25 Jun 2008 02:50:07 +0000

What situation would the page be "served" as xml... ?

A server sends information to the browser about every file it sends. One piece of data is known as the MIME type. For HTML the MIME type is text/html. Any file can be sent as text/html, including php files, .cf files, and so on.

The browser in turn sends information to the server as to what MIME types it can handle. A number of webmasters will send files as one of the possible XHTML MIME types to browsers that can handle it. There are several ways to do this, from server settings to using PHP.

As you are using HTML, the restrictions of XHTML/XML do not apply. Same with XHTML sent as HTML - only the validator takes any notice of the difference - browsers treat the code as regular HTML, not XHTML.

Presumably some of those using XHTML do so to get the benefits of XML-- or why put up with unnecessary restrictions? Hence my caution about using code that will break when they eventually send their elaborately coded pages as the "correct" MIME type.

Hope you can make sense of all this! :\

P.S. One way of sending XHTML is described at Keystone Websites.com.

I never had a problem with

netsperience — Tue, 24 Jun 2008 03:50:46 +0000

I never had a problem with document.write() but I am mostly adding JavaScript to PHP pages or Lassoscript these days, or HTML.

Do you mean XHTML files using a .xml extension? What situation would the page be "served" as xml, in rss?

I'm not questioning you, but I'm curious, I never encountered a situation like that.

netsperience

webwiz — Tue, 24 Jun 2008 01:17:59 +0000

netsperience suggested:

document.write ('<scr' + 'ipt type="text/javascript" src="js2.js"></scr' + 'ipt>');

Well, yes. You could. But bear in mind that document.write does not work in XHTML mode (on XHTML pages served as XML).

Although you are more likely to be using HTML mode for your pages. Just thought I'd mention it.

you can do that if you use

netsperience — Tue, 24 Jun 2008 00:40:56 +0000

you can do that if you use document.write() to embed the second js file:

<script type="text/javascript" src="js1.js"></script>

and in js1.js have this code:

document.write ('<scr' + 'ipt type="text/javascript" src="js2.js"></scr' + 'ipt>');

notice that I have separated the script tags so they do not interfere with the container script...

Nope. Basically, a .js file

webwiz — Fri, 06 Jun 2008 19:18:32 +0000

Nope.

Basically, a .js file interprets JavaScript, not HTML. But you can combine two .js files into one and use the combined file as the SRC to the SCRIPT. A tiny bit more work, but does what you want-- if I understand you correctly.