Why does this render correctly in IE, and not Firefox?

[cr3ative]

I rarely ask for help, so bear with me on this one :rolleyes:

I've got a small image upload service running at www.b3ta.cr3ation.co.uk , and when the user uploads a file, they get a congratulations dialog, and some text boxes telling them how they can link to the files.

Here's an example of the "congratulations" page's code:

http://www.b3ta.cr3ation.co.uk/codeexample.htm

Here's what I'm seeing in internet explorer:
http://www.b3ta.cr3ation.co.uk/images/ie.JPG

And in Firefox:
http://www.b3ta.cr3ation.co.uk/images/firefox.JPG

However, even more strangely, it only happens on certain filenames.
Any reason this is happening? It validates as XHTML 1.1 perfectly.

cr3ative

/edit: Grargh! Now it's working in the code example! It's such an irritating problem.

[jscheuer1]

Hey cr3,

Seems to me that it may be in your template for the file rather than in the resulting file. Or in the code that generates the file from the template. In any case, simply looking at a page that works to find 'the problem' is tough for me. Is there a way that you could, next time it happens, snatch that particular page's source code? That in itself might hold your answer.

[cr3ative]

Okay, now it's happening again in the code example ( http://www.b3ta.cr3ation.co.uk/codeexample.htm ).

I'm losing hair over this one.

And now it's not.
Auuuuugh!

Here's a zip of the entire site's code (no images included):
http://b3ta.cr3ation.co.uk/b3ta.zip

[cr3ative]

I've submitted this one to bugzilla, seeing as it changes almost every refresh.

cr3

[jscheuer1]

I have yet to be able to observe it behaving badly. I've tried in FF on numerous occasions, often with numerous refreshes. Perhaps an OS related bug. One thing, probably nothing but, in your screenshot images, both the IE and FF ones, you have a semicolon to the right of the HTML text input but, I don't see this in either browser on the demo.

[cr3ative]

Yes, I corrected that, it was just an additional ;, nothing important.

Bugzilla has confirmed as a bug and it's been fixed for the release of Firefox 1.5 (Deer Park Alpha 2).

Thanks :)