|
|
Posted by Mika on 11/23/07 10:27
"Ian Hobson" <ian.hobson@ntlworld.com> wrote in message
news:MyX0j.596$8k2.353@newsfe4-win.ntli.net...
> The mess has been created by the templating system that has not helped
> you.
We would agree - Microsoft Expression Web Editor to be precise. It is
upsetting that it has caused many problems. We have been trying to work
through some today.
We have now solved the issue this thread was about. We now call the j/s in
a different file:
<script type="text/javascript" src="mapscript.js"></script>
However the problem with the templating system was that if we tried to but
this *after* the </body> tag, it would not allow it and moved it back.
Furthermore the reason we used SSI was after advice from this group a year
ago. The reason was the MS border navigation system which inserted our top
and bottom borders to all pages, did so by creating a table... and Google
Maps API cannot work within a table!
So all of this mess was caused by Microsoft (Expression Web, and IE)
incompatibilities or lack of understanding of Google Maps API. We have done
our best.
*Good news!* Our workaround is to edit the page in a text editor as the
final stage before uploading, and we move that tag to after the </body> tag.
* We can now refresh without Operation Aborted :)
* We have been able to dispense with SSI and use the top/bottom border :)
* We have also changed the doctype to Strict as suggested here (it was
Transitional because someone else here suggeted that months ago!). Again,
doing our best.
This leaves us with a problem hopefully someone here will be able to help us
fix?: In Firefox, there seem to be extra spaces or lines messing up the
formatting. See how the top border is broken up, and the table cells have
large lines above/below? This was after alterting the doctype, btu why?
Constructive polite replies welcomed :)
Navigation:
[Reply to this message]
|