Closed
Bug 58172
Opened 24 years ago
Closed 24 years ago
<a> tags don't seem to recognize an applied class
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Tracking
()
RESOLVED
INVALID
People
(Reporter: obijuan, Assigned: pierre)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (Win98; U)
BuildID: 2000101014
If I specify a class on an A tag, it the color settings defined in the style
sheet should override the default color. For some reason I can't make this
work.
--
<EXTERNAL CSS>
.nav { color: #ffcc00; }
<HTML>
<a href="#" class=nav>
--
I'm using an external style sheet on this page, con't know if this has anything
to do with it.
Reproducible: Always
Steps to Reproduce:
1. Look at http://djkos.com/
2. The navbar at the top is supposed to be yellow. It's blue.
3.
Actual Results: The navbar at the top should be yellow. It works fine on
Netscape 4.0 and IE on PC.
Expected Results: Instead, the navbar is the default hyperlink blue.
Comment 1•24 years ago
|
||
Your style.css contains SGML comments. These are not allowed in external style
sheets. As a result the parser parses that rule as:
<!-- header --> .nav { color: #ffcc00; }
and throws it out per the spec.
If you want to inlude comments in the style sheet, they should be like this:
/* This is a comment */
Comment 2•24 years ago
|
||
Marking INVALID per previous comments.
(Note that actually, "<!--" and "-->" are allowed in certain places of CSS, they
are then treated as whitespace. The result in this case is that the rule becomes
header .nav { color: #ffcc00; }
...and since there is no <header> element...)
Boris: Thanks for catching that!
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Comment 3•24 years ago
|
||
Netscape's standard compliance QA team reorganised itself once again, so taking
remaining non-tables style bugs. Sorry about the spam. I tried to get this done
directly at the database level, but apparently that is "not easy because of the
shadow db", "plus it screws up the audit trail", so no can do...
QA Contact: chrisd → ian
Comment 4•23 years ago
|
||
reassigning QA to petersen since I resolved this bug
QA Contact: ian → petersen
You need to log in
before you can comment on or make changes to this bug.
Description
•