All users were logged out of Bugzilla on October 13th, 2018
499 bytes, text/html
648 bytes, text/html
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.0-test3 i686; en-US; m18) Gecko/20000801 BuildID: 2000080113 Mozilla seems to prefer style definitions from a:link over ones specified in class= Not sure if this is a bug or a feature. Reproducible: Always Steps to Reproduce: 1. create a style definition for a:link and a.xyz 2. <a href="..." class="xyz" ... > 3. mozilla preferes a:link over a.xyz definitions to render the link Expected Results: Good question. At least other browsers seem to priorize a.xyz over a:link.
Confiriming, changing OS/Plat to all in hopes someone who knows the exact css specs knows which should hold precedence.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Need a testcase. Sounds like an INVALID bug, since it should depend on order (pseudo-classes and normal classes have the same specificity).
Marking INVALID: testcase shows that Mozill ais cascading correctly.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
Thanks for the clarification. As said initially it was not clear to me what the correct behaviour is. I just noticed that NS and IE did display it differently.
Adding 'verifyme' keyword
To clarify the difference, i added a test case which behaves differently between NS and Mozilla.
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
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.