[Webkit-unassigned] [Bug 256850] New: The "tableborder" attribute (on its own) creates a visible border in WebKit

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=256850

            Bug ID: 256850
           Summary: The "tableborder" attribute (on its own) creates a
                    visible border in WebKit
           Product: WebKit
           Version: Safari 16
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tables
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: dholbert at mozilla.com
                CC: zalan at apple.com

Created attachment 466364

  --> https://bugs.webkit.org/attachment.cgi?id=466364&action=review

testcase 1

This issue affects both Chromium and WebKit. The Chromium version of this bug report is https://bugs.chromium.org/p/chromium/issues/detail?id=1446014

STR:
1. View attached testcase.

EXPECTED RESULTS:
The first table should have no border (just like the second one).

ACTUAL RESULTS:
The first table does have a blue border.


The first and second tables both set the color of the border, but don't explicitly activate the border using the `border` attribute or the `border-style` property, which is why the border should not render.

The problematic first table here is just <table bordercolor="blue">.  Per the html spec at https://html.spec.whatwg.org/multipage/rendering.html#tables-2 , the browser is supposed to "treat the [bordercolor] attribute as a presentational hint setting the element's 'border-top-color', 'border-right-color', 'border-bottom-color', and 'border-left-color' properties to the resulting color."

If that were what WebKit were doing, then it would render that table the same as the second one, with no border.

Firefox gives expected results here.  So does EdgeHTML (pre-Chromium Edge).
Chromium and WebKit give "actual results".  I suspect this is a webkit-ism that predated the Blink fork.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230516/4889a96c/attachment.htm>