[Mozile] Newbie needs help setting up mozile.

[Ian Hobson]

Hi James,

Thanks for the reply. I can shed some more light on things.

For a completely unrelated reason I had to install Apache on the 
machine, and point it to serve the same set of files. So I tried the 
test case out of curiosity, and it worked!

Switch back to Xitami and it fails.

So the problem is something to do with the settings of Xitami "out of 
the box". I have not had time to look into things further. It is a fresh 
install and and the only thing I have done is to turn on SSI.

Could a mime type on the .js files be wrong?

Btw - I got the save working. I used SSI to include the filename as the 
content attribute in a meta tag with name="source", so it comes back 
with the file save and the script can save it back where it goes.

While reversing out the SSI changes, I discovered the hard way that 
attributes come back in random order, so my reg-ex to match the meta tag 
was a head scratcher!

I have noticed a number of strangenesses about the returned format, most 
notably that the newline between my </script> tag and the </head> got 
dropped. Suspect this is where the extra script tags are added and 
removed dynamically.

Regards

Ian

James A. Overton wrote:
> Hi Ian,
>     Sorry for the late reply. The mailing list filter caught your 
> message, and I didn't get a chance to clean the filter this weekend.
>     From what you say, everything seems to be correct. The test page is 
> fine, the settings are fine, and the scripts are being loaded. Using 
> your test page in my local setup works perfectly: I can see the editable 
> DIV and edit it. I tested it using FF 1.5.0.4 under Mac OS X and Win98.
>     So I'm not sure what the problem might be. It doesn't sound much 
> like a Mozile problem. Does the page render correctly when the <script> 
> tag is removed? 
yes.
Are there any error messages to the JavaScript Console?
No
> Does the DOM Inspector show that the DIV element exists? 
I didn't look.
You could try
> using an HTML doctype instead of an XHTML one.
>     Sorry. You've provided a lot of useful information, but I can't 
> figure out what's wrong. If you find anything else, or make any 
> progress, let me know.
>