Bug 43346 - table is missing right border depending on existence of colspan
Summary: table is missing right border depending on existence of colspan
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-02 07:18 PDT by harrije
Modified: 2012-03-26 11:40 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description harrije 2010-08-02 07:18:26 PDT 
My problem is that some tables do not display the right side borders with browsers that use webkit, i.e. Safari and Chrome. The version of Safari I am using is 4.0.4 (531.21.10) according to the about menu item under help. The version of Chrome I am using is supposedly the most recent according to Google's web site, but I could not find an "about" menu option under help to confirm the version...

The problematic tables are those that are using the colspan attribute depending on the number of columns. If the table has two or less columns with colspan, then the table displays correctly with the right border. If the table has 3 or more columns with colspan, then the table displays with a missing right side border. If the table does not have colspan, then the table displays correctly regardless of the number of columns. Why would the number of columns plus the colspan attribute have anything to do with the price of eggs in China?

BTW: the tables rendered correctly in IE, FF, and Opera... the problem is only with Safari and Chrome...

Here is the HTML source for the two column example that displays correctly:

<HTML>
<HEAD><TITLE>test Webkit with 2 columns</TITLE></HEAD>
<BODY>
    <TABLE id="GridView1" border="0" cellSpacing="0"
        style="BORDER: #714938 2px solid; BORDER-COLLAPSE: collapse;">
        <TBODY><TR><TD colSpan=2>no items found</TD></TR></TBODY>
    </TABLE>
    <TABLE id="GridView2" border="0" cellSpacing="0"
        style="BORDER: #714938 2px solid; BORDER-COLLAPSE: collapse;">
        <TBODY>
            <TR>
                <TH scope=col>id_pur</TH>
                <TH scope=col>subscription_pur</TH>
            </TR>
            <TR><TD>11</TD><TD>2</TD></TR>
        </TBODY>
    </TABLE>
</BODY>
</HTML>

The above example renders two tables, both tables display the right side border.

Here is the HTML source for the three column example, where one table renders incorrectly:

<HTML>
<HEAD><TITLE>test Webkit with 3 columns</TITLE></HEAD>
<BODY>
    <TABLE id="GridView1" border="0" cellSpacing="0"
        style="BORDER: #714938 2px solid; BORDER-COLLAPSE: collapse;">
        <TBODY><TR><TD colSpan=3>no items found</TD></TR></TBODY>
    </TABLE>
    <TABLE id="GridView2" border="0" cellSpacing="0"
        style="BORDER: #714938 2px solid; BORDER-COLLAPSE: collapse;">
        <TBODY>
            <TR>
                <TH scope=col>id_pur</TH>
                <TH scope=col>subscription_pur</TH>
                <TH scope=col>purchaser_pur</TH>
            </TR>
            <TR><TD>11</TD><TD>2</TD><TD>85</TD></TR>
        </TBODY>
    </TABLE>
</BODY>
</HTML>

For the above example the first table, which has colspan, is missing the right border when displayed with webkit browsers, but the second table without colspan is not missing the border.
Comment 1 sramshetti 2011-05-20 02:38:24 PDT 
Same issue is happening with latest chrome browser as well.

Google Chrome	11.0.696.68
WebKit	534.24
Comment 2 Julien Chaffraix 2012-02-23 16:24:53 PST 
I just looked at your attachment (second test case both quirks mode and not) and it seems to be working on Chrome now (tried on the dev channel). A lot has happened in the code since the bug was filed. Could you just confirm that the bug has been fixed? Thanks!
Comment 3 Julien Chaffraix 2012-03-26 11:40:20 PDT 
No reply for a month, considering this old bug fixed. Please comment on this bug if this is not the case.

Thanks for the report!