There are a couple of irregularities in the markup
1. Line 12 a stray <br />. This irritates IE
2. Line 85 the red highlighted quotes are missing
3. Line 91 a stray </embed>
Looking at the raw XML file, there are some irregularities such as extra blank lines (e.g. line 412). I don't think these matter, but it is worthwhile keeping in mind.
On my test server, I added another 150 odd lines to the XML and noticed no problem.
I did, what I usually do, place ALL scripts and links to scripts at the bottom of my document. Don't know if this makes a difference, but again it worked for me.
Thank you very much for your advice.
I tried everything but it makes no difference.
Only some scripts aren't properly compiled when I place them outside the <head>, so I put them back.
The <embed> is necessary to display the .swf.
You were right it's an IE problem - Chrome and Firefox display ok.
I've left it live, so you can see the problem.
Sorry for the delay, I have spent some time trying to find the culprit. Finally I decided to start afresh with the following markup, which works quite well in all browsers.
May I suggest that you copy and paste the markup into a new document to then start adding your own stuff, making sure that you test in IE7 or IE8 at each step.
Note that I have left xpath.js out of the markup. I think it will work either way. Just keep an eye on it.
I did reformat the XML to delete all of the empty lines. Not sure if this helped or not. You can do this within DW as follows
Message was edited by: Altruistic Gramps
I can't get it working when arranged like this. Basicaly, when i only want to display the xml data it won't work. In <HTML xmlns:spry="http://ns.adobe.com/spry"> seems necessary - although an error message when validating.
played with div tags but that didn't work. the only thing that fixes this poblem is removing
<div style="clear:both;" ></div>
but when i do this the div blocks are completelely misplaced in the display. Quite strange that this solves the XML problem.
Maybe i"ve messed up something in the code, but i really have no idea.
I'll take a closer look at the <div> nesting, maybe that's an issue.