400162 - Underlining Icons when using Link relation (rel-attribute) and CSS-formatting

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Nils]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7

As far as I can tell, using CSS-property "content" along with pseudo-tag ":before" to generate an icon in front of a link should not make the icon underlined. Other browsers (Safari, Opera, Konqueror) do it right. 

Placing items "before" should not make them part of <a> but be set as <img> before and handled as such.

Here is one example of what I am talking about:

.mainContent a[rel="internal"]:before {
  content: url("/images/ico_link_internal_main.gif");
  padding-right: 0.2em;
}

Reproducible: Always

Steps to Reproduce:
simply open the demo-website in FireFox
Actual Results:  
Icon is being underlined (if underline is set as CSS-attribute of course)

Expected Results:  
Icon should not be underlined, because it is being placed :before <a>

Comment 1

[winner5]

I think that firefox does the right thing, because I remember that :before becomes the first child of the node.

Comment 2

[Tyler Downer [He/Him]]

This bug was originally reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.6 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.