DescriptionUse effective columns when cells with colspan are present.
Colspan brings some mess when cells for particular coordinates
are returned. Effective column's conversion should be used to make sure we
operate on exact column. Let's consider a very simple test case:
<table><tr><td colspan="10"></td><th></th></tr></table>. Currently
cellForColumnAndRow(1, 0) returns a first cell not the second.
Basically columnIndexRange produces wrong information {0, 10} instead of {0, 1}
which is wrong. Effective columns are fixing this issue.
BUG=457687
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=190160
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=190442
Patch Set 1 #Patch Set 2 : Just updating expectation result #
Total comments: 1
Patch Set 3 : Fixed typo and added effective col's calculation to column's headerObject method #Patch Set 4 : Second attempt to land this patch #
Messages
Total messages: 19 (5 generated)
|