Source/core/layout/style/LayoutStyle.h - Issue 921843004: Stop explicit inheritance if LayoutStyle doesn't change.

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

Unified Diff: Source/core/layout/style/LayoutStyle.h

Issue 921843004: Stop explicit inheritance if LayoutStyle doesn't change. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Created 5 years, 10 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « LayoutTests/fast/css/invalidation/explicit-inheritance-propagation-expected.txt ('k') | Source/core/layout/style/LayoutStyle.cpp » ('j') | Source/core/layout/style/LayoutStyle.cpp » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: Source/core/layout/style/LayoutStyle.h

diff --git a/Source/core/layout/style/LayoutStyle.h b/Source/core/layout/style/LayoutStyle.h

index 22991f87966e85da69a4d1f3773f36932d0bef70..d7dba4e775e5dd61aeb610e7b108196b0de68177 100644

--- a/Source/core/layout/style/LayoutStyle.h

+++ b/Source/core/layout/style/LayoutStyle.h

@@ -227,7 +227,6 @@ protected:

&& affectedByDrag == other.affectedByDrag

&& pseudoBits == other.pseudoBits

&& unicodeBidi == other.unicodeBidi

- && explicitInheritance == other.explicitInheritance

esprehn 2015/02/13 02:29:13 This doesn't seem right, why is it okay to return

&& unique == other.unique

&& emptyState == other.emptyState

&& isLink == other.isLink;