278601 - vkzla.com - Mapping functions do not work in mozzilla

Status: RESOLVED INVALID

(Core Graveyard :: GFX, defect)

Description

[Todd A. Moore]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 

this mapping function will not work in Mozilla, it works fine in both of the 
other major web browsers, but it inop in Firefox

<p align="center"><map name="KZLA_Map">
<area href="/airports/KBUR.htm" shape="rect" coords="187, 216, 225, 228" 
alt="Burbank-Glendale-Pasadena">
<area href="/airports/KLAS.htm" shape="rect" coords="284, 122, 330, 150" 
alt="Las Vegas/McCarran International">
<area href="/airports/KLAX.htm" shape="rect" coords="190, 228, 227, 240" 
alt="Las Angeles International">
<area href="/airports/KSBA.htm" shape="rect" coords="139, 204, 176, 216" 
alt="San Bernardino">
<area href="/airports/KPSP.htm" shape="rect" coords="268, 218, 305, 251" 
alt="Palm Springs">
<area href="/airports/KLGB.htm" shape="rect" coords="212, 239, 250, 251" 
alt="Long Beach">
<area href="/airports/KSAN.htm" shape="rect" coords="241, 272, 279, 284" 
alt="San Diego">
<area href="/airports/KGCN.htm" shape="rect" coords="377, 114, 416, 130" 
alt="Gran Canyon">
<area href="/airports/KEDW.htm" shape="rect" coords="222, 179, 266, 195" 
alt="Edwards Air Force Base">
<area href="/airports/KAVX.htm" shape="rect" coords="161, 253, 198, 270" 
alt="Avalon/Catalina">
<area href="KZLA_CHARTS.htm" shape="polygon" coords="231, 59, 429, 62, 434, 
134, 360, 186, 387, 290, 334, 274, 263, 289, 127, 379, 32, 223, 173, 138" 
alt="Click here for all KZLA airport listings">
<area href="kzlc.htm" shape="polygon" coords="225, 1, 232, 58, 430, 61, 498, 
17, 498, 0" alt="Salt Lake City ARTCC">
<area href="kzak.htm" shape="polygon" coords="0, 173, 33, 224, 173, 139, 233, 
60, 226, 0, 0, 0" alt="Oakland ARTCC">
<area href="mmzt.htm" shape="polygon" coords="143, 399, 129, 380, 263, 290, 
336, 276, 475, 321, 499, 319, 499, 399" alt="Mazatlan FIR">
<area href="kzab.htm" shape="polygon" coords="499, 319, 476, 319, 389, 292, 
361, 187, 436, 134, 499, 121" alt="Albaquerque ARTCC">
<area href="kzdv.htm" shape="polygon" coords="498, 120, 435, 134, 430, 63, 
499, 15" alt="Denver ARTCC">
<area href="kzoa.htm" shape="polygon" coords="0, 172, 124, 377, 145, 399, 0, 
399" alt="Oakland Oceanic ARTCC">
</map>
<img src="/graphics/kzla.gif" alt="KZLA Sector"</p usemap="#KZLA_Map" 
width="500" height="400">


Reproducible: Always

Steps to Reproduce:
1.just click anywhere on the map, it does nothing
2.
3.

Actual Results:  
nothing happens

Expected Results:  
gone to another web page where you click on the map

Comment 1

[Patrick]

you've got 
  shape="polygon"

the correct statement is 
  shape="poly"

Comment 2

[Patrick]

That's just a warning, most of all, the map you call is wrong :)

The site now says,
<img src="kzla_map_files/kzla.gif" alt="KZLA Sector" border="0" usemap="#Map">

but a few lines up, where the map is defined it reads:
  <map name="KZLA_Map">

Changing the img tag to:
<img src="kzla_map_files/kzla.gif" alt="KZLA Sector" border="0" usemap="#KZLA_Map">

fixes your problem.

Comment 3

[Patrick]

adding URL to summary.

I checked your site again but this time via a "view source" looking not at the
code as RENDERED by Mozilla but at the SOURCE as it is on your web server and
this revealed a spurious "</p" in your image tag: 

<img src="/graphics/kzla.gif" alt="KZLA Sector"</p usemap="#KZLA_Map"
width="500" height="400">

This causes Mozilla/Firefox to ignore the rest of the line [as it should] and
thus it misses the map name specified by you. Removing that lost bit of code
will fix your site.

[PS: the source as RENDERED by mozilla is the one listed in my comment 2]

Comment 4

[Patrick]

i checked the page again today, and it's now fixed.

Moving this to CORE, to get a second opinion. Maybe we need to change the error
handling?

Comment 5

[Boris Zbarsky [:bzbarsky]]

There is no error handling...  '<' is a valid way to end a tag and start a new
one at the same time in HTML.

I'm not sure why this got dumped into GFX, but the bug's clearly invalid.