Issue 479563002: Remove additionalOutlineSize in ShadowList: it is always 0.

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 479563002: Remove additionalOutlineSize in ShadowList: it is always 0. (Closed)

Created:
6 years, 4 months ago by jbroman

Modified:
6 years, 4 months ago

Reviewers:
Stephen Chennney, f(malita)

CC:
blink-reviews, blink-reviews-rendering, zoltan1, eae+blinkwatch, leviw+renderwatch, jchaffraix+rendering, pdr., rune+blink

Base URL:
svn://svn.chromium.org/blink/trunk

Project:
blink

Visibility:
Public.

Remove additionalOutlineSize in ShadowList: it is always 0. Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=180370

Created: 6 years, 4 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+7 lines, -7 lines)			Patch
	M	Source/core/rendering/style/ShadowList.h	View		1 chunk	+2 lines, -2 lines	0 comments	Download
	M	Source/core/rendering/style/ShadowList.cpp	View		3 chunks	+5 lines, -5 lines	0 comments	Download

Total messages: 5 (0 generated)

jbroman

More cleanup while running through the shadow code. This one's pretty trivial.

6 years, 4 months ago (2014-08-15 14:52:32 UTC) #1

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/jbroman@chromium.org/479563002/1

6 years, 4 months ago (2014-08-15 16:12:25 UTC) #4

Message was sent while issue was closed.

Committed patchset #1 (1) as 180370