181216 - Anchor 'Harness' displays as text, not an anchor, and will not bring up the HFEF destination.

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Brad K.]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021119
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021119

This page is a table of anchors, and none of them work as anchors.  This page
works correctly in IE 6.0, Netscape® Communicator 4.72, but *not* Netscape 6.2.
 This may be a CSS issue.

The HTML for the 'Harness' entry is:
  <tr>
    <td bgcolor=#FFFF99>
      <a class=catlist
href="caa_content.asp?PageType=Dept&Key=6&MType=HA&MTypeDesc=Harness"></a>
      Harness</a>

    </td>
  </tr>

The 'catlist' style, from caa.css:
  A.catlist {color:#006600; 
     text-decoration:none;
     font-family: Georgia, Times, Serif;
     font-size: 10pt;
     font-weight=bold; } 
  A.catlist:active {color:#006600;} 
  A.catlist:hover {color:#33FF00;} 
  A.catlist:visited {color:#006600;}
  A.catlist:visited:hover {color:#33FF00;}

---


Reproducible: Always

Steps to Reproduce:
1. Enter URL http://www.carriageassoc.com/caa_content.asp?PageType=Dept&Key=6
2. scroll down page to 'Harness'
3. Attempt to click on 'Harness'

Actual Results:  
The text cursor appears over 'Harness', and the page stays as it is.

Expected Results:  
Follow the anchor link to the 'Harness' page.

As far as I can see the only workarounds are to use another browser.

Comment 1

[Chris Lyon]

Here's the problem:
<a class=catlist
href="caa_content.asp?PageType=Dept&Key=6&MType=HA&MTypeDesc=Harness"></a>     
Harness</a>

Notice the two </a> tags?  The first one closes the link, so the text "Harness"
is treated as plain text.

Although IE is much more forgiving, this is not a Mozilla bug.  I suggest you
email the webmaster.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Actaully, the source is:

<a class=catlist
href="caa_content.asp?PageType=Dept&Key=6&MType=HA&MTypeDesc=Harness"</a>
Harness</a>

(view-source is off in this case).  But yes, we're not likely to change that
part of the parser...