Hey guys,

Just wondering if anyone had encountered an issue like this. I've been coding something into an existing CMS, the content is generated offline and uploaded (Actinic v9 to be precise). Now I've spent a while on this and its baffling me, its nothing to do with the software but how Firefox is outputting the file.

When FF gets to even just literally <script></script> it is placing two </div> tags in front of it, closing off the area its in and forcing the script to run in the wrong place. IE is fine!

Has anyone come across a problem like this?

Regards,

Leonard

If you can see these </div> tags in the source, it isn't being done by a browser.

As far as I can tell I'm afraid it is...

...all signs point to that as the html file on disk opened in notepad doesn't show this error in the code. Opening in Firefox and viewing source and generated source backs this up... the generated source contains this error, which is what leads me to believe it is Firefox generating these tags. At this stage I don't know what else it could be unless you have any other suggestions?

EDIT:
I know you know your stuff Chris, so just wanted to add that I hope that didn't sound snotty. I've been scouring over the code to try and work out this issue and as far as I can tell its a FF bug not anything else. I will try and clean up some code to post to try and demo this.

Right, I found the solution! It came down to some residual code coming from Actinics labyrinth like template system. When cleaning up the code to post it I found that the Product box divs I was inserting the code into was nested between a <table ...> and a </table>. No rows or cells, just that. Took them out, problem solved.

I guess Firefox sees that and figures I'm an idiot and it probably knows better. Well it was half right, but it didn't know better in this occassion! Thought I'd report it in case someone bumps into a similar issue in the future.

The various classes of browsers have slightly different ways of dealing with malformed code, which is why it is important to form it correctly, and since there is no standard as to what a browser is supposed to do with bad code, it is hard to predict what will happen. Glad you got it figured out.

Browsers by themselves do not arbitrarily add code - they render (sometimes badly) what is sent TO them by the server.

Actually there is a method to make firefox appear to add code. Try rendering some bad code such as the following:

aaa<table><td> hello </table> bbb

Firefox will only use the code you have supplied it, which in this case is bad code. Doing a view source will show our bad code.

Now try highlighting the text and doing a view selected source. This time the code will be different and the table will have closing tags added. This is because the view selection source builds the code instead of showing your root code.