Issue 542863007: Remove hasContentsLayer and isMainFrameRenderViewLayer from CLM

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 542863007: Remove hasContentsLayer and isMainFrameRenderViewLayer from CLM (Closed)

Created:
6 years, 3 months ago by pdr.

Modified:
6 years, 3 months ago

Reviewers:
kouhei (in TOK)

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

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

Project:
blink

Visibility:
Public.

More Reviews

Description

Remove hasContentsLayer and isMainFrameRenderViewLayer from CLM This patch removes some deadcode from CompositedLayerMapping: 1) hasContentsLayer - this function name was confusing. 2) isMainFrameRenderViewLayer - state is now all within CLM. No new tests, no change in behavior. Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=181526