596749 - <HR> determined not to follow color command, sometimes...

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[john]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9

At the above URL, the <HR> in this code shows displays two "Navy" HR, despite that the source displayed in fox, and the original source show "Green" for the second one:

<HR COLOR="Navy" SIZE=4 NOSHADE>

<table width=100%><tr><td>
<font size="-1" face="arial" >All Content Copyright &copy; 1997-2010 John Ruskin.  All rights reserved.
<BR><A HREF="mailto: JohnRuskin (at) ComplianceOfficer.Com">LighterSide Project WebMaster  (at)  ComplianceOfficer (dot) Com</A>
</font>
</td><td align=right><font size=+1><a href="#_top">Top</a>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="index.htm">LighterSide subHome</a>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="../index.html">Way Home...</a></font>
</td></tr></table>

<HR COLOR="Green" SIZE=4 NOSHADE>

This code is at the bottom of the page.  IE displays it as expected.  The local variant on my laptop displays as expected.

Quite quirky.

Firebug shows off Green, as expected, in the Dom

But -- for the Style -- I have a css which sets HR as Navy.   I would expect the explicit declaration as green to overcome that; but Firebug says no....

What am I missing?  Do <HR> css declarations become absolute, unlike other element declarations that can be declared in css, but whose inheritance is topped by explicit declarations? 

Reproducible: Always

Steps to Reproduce:
1.   go to URL shown, and examine the two horizontal rules at the bottom.  One is Green and the other is Navy in HTML, but both display as navy.

Comment 1

[j.j.]

Don't use <hr color >, it's quirky.

AFIK simple CSS color:blue; doesn't work in Opera(?), Safari and Chrome.
For cross-browser color styling of <hr> elements see

 http://forums.mozillazine.org/viewtopic.php?t=592788

Comment 2

[john]

I guess the funny thing is that coloring an HR works, sort of.   

Fox -will- color an HR element; as long as it is being colored by current Fox [regardless of standard] shouldn't the inheritance work?  The peculiar quirk I landed on, has a quirk which exhibits inconsistently [it -is- a quirk, after all] - the inconsistency isn't in the coloring, but in the inheritance. 

By itself, it [the HR quirk] -is- trivial and, on reflection, not really the subject of my bug.  It makes me wonder if there is something odd in the way the inheritance function functions....  which makes me wonder if there are other subtle problems with inheritance in the DOM.

[am I using "DOM" in the right context, here....?]

. . . . For which my vote would be for retaining the inheritance bug.

Comment 3

[j.j.]

   <style> hr { color: blue } </style>

   <hr color=red>

this <hr> is blue, because CSS always overrides HTML attributes.
IE is buggy in this case (interestingly only in strict mode)

Comment 4

[john]

AHHH.!  I assumed that an explicit declaration within an HTML element overrode....My error!  

...In which case, IE is buggy in strict -and- transitional modes -- in my code I had declared a transitional document coding.

Out of curiosity...Where in the CSS standard does it say that CSS overrides an explicit declaration by an element?  I tried hunting in/around W3.org, and couldn't locate it.

Comment 5

[j.j.]

http://www.w3.org/TR/CSS2/cascade.html#preshint

> I had declared a transitional document
That is not necessarily quirks mode, see
  http://hsivonen.iki.fi/doctype/#handling

Comment 6

[john]

Now, I am -really- laughing, after looking at the second URL offered....

When I mentioned 'quirky' in my original post, I meant it in the English sense, not docType sense.

I now see that the move towards standards appears [to the sort of folk such as I], as a move towards conditionality....   

Very, -very- reminiscent of the blossoming number of physics particles -- I soon expect that there will be quarks in the land of docTypes....

The internet has not eased the movement of information about me, towards those who might want it.  Instead, it has complicated the assembly of information, so that those who might read it -might- read what I am thinking, arranged in a style of random'd choosing.  Now, in the realm of saying something, it is plausible to spend more time deciphering assembly, than in constructing good sense . . . . 

I do thank you for straightening me out, above, on precedence.

Comment 7

[j.j.]

Note that the only doctype you should use these days is just
  <!DOCTYPE html>
from the HTML5 spec.  It is backwards compatible and triggers strict mode in all browsers.