Issue 216823002: [Android WebView] Use container view's Context instead of target app's

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 216823002: [Android WebView] Use container view's Context instead of target app's (Closed)

Created:
6 years, 9 months ago by mnaganov (inactive)

Modified:
6 years, 9 months ago

Reviewers:
mkosiba (inactive)

CC:
chromium-reviews, android-webview-reviews_chromium.org

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Visibility:
Public.

More Reviews

Description

[Android WebView] Use container view's Context instead of target app's A follow up to https://codereview.chromium.org/214543009 where boliu@ noticed that we are using getInstrumentation().getTargetContext() in AwSettingsTest instead of simply getting the context of the container view. This change required some overhaul of testing classes as they didn't have access to the container view. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=260210