Issue 2368843002: Make sure there's a table header before attempting to account for its offset

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2368843002: Make sure there's a table header before attempting to account for its offset (Closed)

Created:
4 years, 2 months ago by rhogan

Modified:
4 years, 2 months ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/pending/branch-heads/2785

Project:
chromium

Visibility:
Public.

Make sure there's a table header before attempting to account for its offset Fix an error introduced by https://codereview.chromium.org/2199553002 BUG=634155 Review-Url: https://codereview.chromium.org/2214093002 Cr-Commit-Position: refs/heads/master@{#410264} (cherry picked from commit 3d5361e0f6ff60c6e79d77b73dff07692ef1848a) Committed: https://chromium.googlesource.com/chromium/src/+/67a748b079a7152ba7d508a3499a14ce5160054c

Created: 4 years, 2 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+17 lines, -1 line)			Patch
A	third_party/WebKit/LayoutTests/fragmentation/no-repeating-thead-no-crash.html	View	1 chunk	+13 lines, -0 lines	0 comments	Download
A	third_party/WebKit/LayoutTests/fragmentation/no-repeating-thead-no-crash-expected.txt	View	1 chunk	+3 lines, -0 lines	0 comments	Download
M	third_party/WebKit/Source/core/layout/LayoutTableSection.cpp	View	1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 2 (1 generated)

rhogan

4 years, 2 months ago (2016-09-25 18:04:23 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
67a748b079a7152ba7d508a3499a14ce5160054c.