W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2012

[whatwg] <table> Relation between "bordercolor" and "border" attributes

From: Kang-Hao <kennyluck@csail.mit.edu>
Date: Thu, 08 Mar 2012 11:08:54 +0800
Message-ID: <4F5822C6.8080004@csail.mit.edu>
(12/03/06 17:58), Kishore Bolisetty wrote:
> But it doesn't talks about the behaviour - what if border is not specified
> but bordercolor is specified? Looks like browsers have taken their own
> implementations on this, Opera and Mozilla displays bordercolor only if
> border is specified, where as Safari displays bordercolor assuming a
> default border.

I'll add one more testing result. IE9 and IE quirks mode match Opera and
Mozilla's behavior.

> Which one is correct behaviour? Is it not necessary to explicitly state
> this in the spec?

I don't know what is correct but Safari is certainly less interoperable
here, and the spec matches the interoperable behavior. That is, I think
the spec is pretty clear: bordercolor only changes the border color, not
whether the border shows up or not ('border-style') or border width
('border-width').

(12/03/07 0:35), Tab Atkins Jr. wrote:
> This behavior depends on the browser's default stylesheet, and whether
> they default borders to "border-style: solid; border-color:
> currentColor;" or "border-style: solid; border-width: 0px;".  Browsers
> are allowed to do either.

I don't understand your examples. I think you are probably suggesting
that browsers are allowed to put "table[bordercolor] { border-style:
solid}" in the default stylesheet, but I don't think that's the case
since it makes the browser that does this not "supporting the suggested
default rendering".



Cheers,
Kenny
Received on Wednesday, 7 March 2012 19:08:54 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:40 UTC