LayoutTests/fast/dom/shadow/inner-scope-important-wins-expected.txt - Issue 1134173002: Get rid of TreeBoundaryCrossingRules.

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: LayoutTests/fast/dom/shadow/inner-scope-important-wins-expected.txt

Issue 1134173002: Get rid of TreeBoundaryCrossingRules. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Missing important UA rules. Created 5 years, 7 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/dom/shadow/inner-scope-important-wins.html ('k') | LayoutTests/fast/dom/shadow/outer-scope-lower-specificity-wins.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/fast/dom/shadow/inner-scope-important-wins-expected.txt

diff --git a/LayoutTests/fast/dom/shadow/inner-scope-important-wins-expected.txt b/LayoutTests/fast/dom/shadow/inner-scope-important-wins-expected.txt

new file mode 100644

index 0000000000000000000000000000000000000000..23e258c34b6538dea7c19b3bdaa6a1053fbffdad

--- /dev/null

+++ b/LayoutTests/fast/dom/shadow/inner-scope-important-wins-expected.txt

@@ -0,0 +1,10 @@

+Inner scope !important rules wins, even with lower specificity.

+On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".

+FAIL getComputedStyle(target).color should be rgb(0, 128, 0). Was rgb(255, 0, 0).

+PASS successfullyParsed is true

+TEST COMPLETE