Displayedness issue with the spec and tests

I have found an interesting issue with displayedness. I was about to make a change to MicrosoftEdgeDriver when I found that the most recent version of the ChromeDriver also has the same issue. This is new in ChromeDriver, so I believe they broke because they now match the spec...

I'm planning on adding a new test case for this, but really wanted to make sure we modify the spec if necessary.

The scenario is this: given a Table, trying to click on one of the TR elements may fail because WebDriver finds the center of the TR, discovers it is a table border, and believes the Table is obscuring the TR. it requires that the table borders be in the exact center of the table (so not really common), but it's interesting to think that the table border prevents us from clicking on the row.

HTML:

<table border="1">
    <tr id="tableRow">
        <td>foo</td>
        <td>bar</td>
    </tr>
</table>

WebDriver Example:
_driver.FindElementById("tableRow").Click();

Because the table cells are the same size, the border is the middle of the table.

I hope that makes sense. The spec currently says we should follow the Selenium tests - but I didn't see this test case called out there.

Start by comparing the displayedness behavior described in the issue with the WebDriver specification and the existing Selenium tests. Reproduce the HTML table and _driver.FindElementById("tableRow").Click() scenario, then determine whether the specification needs clarification and add the proposed test case if appropriate.