html firefox imagemap help

Associate
Joined
4 Apr 2003
Posts
1,821
Location
Manchester
Why does this not work in firefox but does in ie?

firefox when hovering over the click point doesn't show the share name gbmcppfs001 in the link on the bottom bar

thx

Code:
<DIV ALIGN=left>

<MAP NAME="map1">

<AREA
	 HREF="\\gbmcppfs001\traffordpark$\Trafford Site IMS Manual\main.htm" ALT="Trafford Park" TITLE="Trafford Park"
	 SHAPE=CIRCLE COORDS="264,192,6">

</MAP>

<IMG SRC="map.jpg"
   ALT="map of GH site" 
   USEMAP="#map1"><BR>


</DIV>
 
ok , I can look at that but would it explain it because if I change the link to something within the folder i.e. main.htm it works in FF.

So will re-writing it change the way it handles the share name?
 
Try using modern code, it may well fix your problems

Code:
<div style="text-align:left">

	<map name="map1">
		<area href="/gbmcppfs001/traffordpark$/Trafford Site IMS Manual/main.htm" alt="Trafford Park" title="Trafford Park" shape="circle" coords="264,192,6">
	</map>

	<img src="map.jpg" alt="map of GH site" usemap="#map1"><br>

</div>
 
Worked it out. Nothing to do with the imagemap in the end

Linking to network shares is turned off in firefox by default. To get round that I used a UNC path

file://///servername/share/file.ext

as described here

Thanks for the help with the code though. I will change to that
 
Worked it out. Nothing to do with the imagemap in the end

Linking to network shares is turned off in firefox by default. To get round that I used a UNC path

file://///servername/share/file.ext

as described here

Thanks for the help with the code though. I will change to that

Sorry I'm trying to understand what you are doing here. Are you using a local machine to serve up webpages to the outside world; or is it an intranet?
 
Try using modern code, it may well fix your problems

Code:
<div style="text-align:left">

	<map name="map1">
		<area href="/gbmcppfs001/traffordpark$/Trafford Site IMS Manual/main.htm" alt="Trafford Park" title="Trafford Park" shape="circle" coords="264,192,6">
	</map>

	<img src="map.jpg" alt="map of GH site" usemap="#map1"><br>

</div>

Sorry but there is no such thing as modern code... all you've done is written xhtml4 style markup, which is fine but wont fix anything because browser do not care about it.

Also HTML5 removes everything to do with markup recommendations you can go back to writing HTML how you like :)

Don't get me started with validation... as it means nothing in the real world, sure its good to know but it does not mean anything but a way of patting yourself on the back.
 
Sorry but there is no such thing as modern code... all you've done is written xhtml4 style markup, which is fine but wont fix anything because browser do not care about it.

Also HTML5 removes everything to do with markup recommendations you can go back to writing HTML how you like :)

Don't get me started with validation... as it means nothing in the real world, sure its good to know but it does not mean anything but a way of patting yourself on the back.

This is parody, surely?
 
Sorry but there is no such thing as modern code... all you've done is written xhtml4 style markup, which is fine but wont fix anything because browser do not care about it.
If there is no such thing as modern code, why the hell are there deprecated tags? xhtml4 lol? -_-

Also HTML5 removes everything to do with markup recommendations you can go back to writing HTML how you like :)
Sounds good, I'll start using <FONT> again. Just because you can do this doesn't mean you should.

Don't get me started with validation... as it means nothing in the real world, sure its good to know but it does not mean anything but a way of patting yourself on the back.

http://www.vanseodesign.com/web-design/validating-code/
 
If there is no such thing as modern code, why the hell are there deprecated tags? xhtml4 lol? -_-

You can still use HTML3 now if you wanted, it wouldn't stop working and you can still continue to use ANY deprecated elements in future versions.

The only time you have to worry is when BROWSERS drop support, not what W3C specs say.

Sounds good, I'll start using <FONT> again. Just because you can do this doesn't mean you should.

Fine, it's more effort but there is nothing wrong with it, browsers will still display it correctly.


You seem to be missing my point, it was suggested that his problem was due to his markup style which was totally incorrect, even with valid XHTML it would still be broken.
 
You can still use HTML3 now if you wanted, it wouldn't stop working and you can still continue to use ANY deprecated elements in future versions.


The only time you have to worry is when BROWSERS drop support, not what

You said "xhtml4", there is no such thing.

And what happens when one browser stops the support and others don't? You have cross-browser incompatibility!

You seem to be missing my point, it was suggested that his problem was due to his markup style which was totally incorrect, even with valid XHTML it would still be broken.

Most of the questions asked here to do with html/css are answered by correcting markup, by following standards.
 
You said "xhtml4", there is no such thing.

Well spotted, would you like a badge?

And what happens when one browser stops the support and others don't? You have cross-browser incompatibility!

Show me a browser that has stopped supporting any of the previous versions of HTML?

Most of the questions asked here to do with html/css are answered by correcting markup, by following standards.

Most might, but this one wasn't.
 
Show me a browser that has stopped supporting any of the previous versions of HTML?

http://www.w3schools.com/TAGS/tag_applet.asp
http://www.w3schools.com/TAGS/tag_basefont.asp


Most might, but this one wasn't.
Let me guess you knew the answer right?

Validating is the first thing people should to when they are having browser incompatibility. Why would anyone leave it to the browser to assume how to correct quirks when all you have to do is follow standards?
 
Don't get me started with validation... as it means nothing in the real world, sure its good to know but it does not mean anything but a way of patting yourself on the back.

Most might, but this one wasn't.

So it means nothing in the real world but can solve most problems? I agree that it had nothing to do with this situation as was suggested, but that's not what you said at first :)

If everyone could work to following current standards, browser developers wouldn't have to make crappy backwards support to deal with people who feel the need to use out-dated things. It's stuff like this which throws in some bloat, bugs, and of course the whole world of inconsistency between browsers. Yes you can use deprecated elements, but why hinder progress? I see your point, but surely you can see it's a bad attitude to think you should abuse quirks mode letting you do it however you like!
 
Sorry but there is no such thing as modern code... all you've done is written xhtml4 style markup, which is fine but wont fix anything because browser do not care about it.

Also HTML5 removes everything to do with markup recommendations you can go back to writing HTML how you like :)

Don't get me started with validation... as it means nothing in the real world, sure its good to know but it does not mean anything but a way of patting yourself on the back.

Try using modern code, it may well fix your problems

I didn't say it would fix this particular time but may well be worth a try!

In my experience of fixing cross browser compatability issues making sure that the code in question is written using up to date standards (hence the term modern code) often fixes any issues.
 
Back
Top Bottom