| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
It turns out, Blink also sends DidFailLoad for the error page, which was causing
testOnPageFinishedCalledAfterError test to fail.
BUG=370950,386300
Review URL: https://codereview.chromium.org/348843002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278934 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The android_webview build will require there only be
a single R class (details in bug).
This change makes the necessary changes to the build
infrastructure for this to happen but the actual swap
to building the webview this way will land as a subsequent
CL.
BUG=387155
build-only change, all trybots compile fine.
NOTRY=true
Review URL: https://codereview.chromium.org/255613003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278849 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
preloader changes.
As much as I would like to keep all tests working,
it seems unreasonable to hold-back performance improvements
for all of Chromium (particularly android) to keep
this test "passing".
https://codereview.chromium.org/302063002/
BUG=387101
TBR=mnaganov@chromium.org
Review URL: https://codereview.chromium.org/343213002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278830 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the following to the shouldInterceptRequest params:
- isMainFrame
- hasUserGesture
- method
- headers
This adds the following to InterceptedRequestData:
- status code
- response phrase
- headers
BUG=387086
android_webview-only CL, trybots are happy.
NOTRY=true
Review URL: https://codereview.chromium.org/284123004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278806 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's a goodness to sequester build configuration in the build/
directory. The gn secondary_source stuff was under tools/gn for
historical reasons, so move it to a more appropriate place.
BUG=None
TEST=do a gn build of base_unittests, run said unittests.
Review URL: https://codereview.chromium.org/340153004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278355 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=386300
TBR=mnaganov@chromium.org
Review URL: https://codereview.chromium.org/342713003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278284 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=322395
Change-Id: Ie0376052892349f18db5d60737f6329b8c92eb1c
Review URL: https://codereview.chromium.org/333003003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278207 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Remove locks, post tasks, and complexity used to support legacy
rendering path.
BUG=344087
Review URL: https://codereview.chromium.org/331103002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277907 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's possible that we end up hanging the browser
process waiting for the response to a popup window
due to a bug in the AwContents hand-over when swapping
out the popup content into the user-supplied WebView.
This patch ensures that we don't end up with two AwContents
instances pointing to the same java AwContentsClientBridge
java object during deletion.
BUG=
Review URL: https://codereview.chromium.org/305823005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277816 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tests
The three tests being flaky (testContentUrlAccessWithTwoViews, testFileUrlAccessWithTwoViews and testCacheModeWithTwoViews) are all implicitly rely on the fact that when a page load error happens, onPageFinished is only called once. This behaviour had been broken since about M33, but due to happy timing, it just didn't cause the tests to fail.
The solution is to filter onPageFinished callbacks on AwContentsClient side, since the flow of passing the URL of the error page appears perfectly normal in the context of Chrome.
Other changes:
-- testContentUrlAccessWithTwoViews was in fact incorrect, as it wasn't expecting an error in case when access to content: URLs is blocked;
-- modified ClientOnPageFinishedTest.testOnPageFinishedCalledAfterError to catch situations when onPageFinished / onReceivedError is called twice, to avoid future regressions;
-- added ClientOnPageStartedTest to catch similar problems with onPageStarted.
BUG=370950,371983
Review URL: https://codereview.chromium.org/281563002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277787 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=344087
NOTRY=true
Review URL: https://codereview.chromium.org/334263009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277594 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch does not change the existing functionality and
purely refactors existing code.
These changes are required to support the new fullscreen video path
(with html5 controls and subtitles) which we will enable in a
subsequent cl (see https://codereview.chromium.org/320273002/)
BUG=385121
Review URL: https://codereview.chromium.org/315973004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277554 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
View size does not necessarily indicate root render pass size, since the
render pass can be smaller, and thus can change when view size stays the
same. Check render pass size changes instead.
BUG=344087
NOTRY=true
Review URL: https://codereview.chromium.org/331093002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277520 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also save other state from context_state_autogen.h that were
missed.
Internal bug b/15023700
BUG=
NOTRY=true
Review URL: https://codereview.chromium.org/334103002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277515 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also fix double disabling accelerated 2d canvas and webgl.
Currently using gpu thread context causes GL errors and triggers some
DCHECKs, and perf is not great, but otherwise works just fine.
BUG=344087
NOTRY=true
Review URL: https://codereview.chromium.org/334123002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277489 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
content api convention as midi/geolocation/notifications.
R=mkosiba@chromium.org
Review URL: https://codereview.chromium.org/337913002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277438 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277345 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
switching the code to using RenderFrames.
As part of this, I also simplified the Content API like I did with geolocation in 277038.
BUG=304341
R=avi@chromium.org
TBR=mkosiba, nasko
Review URL: https://codereview.chromium.org/335993002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277293 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
TBR=ycheo@chromium.org
BUG=384753
Review URL: https://codereview.chromium.org/332063002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277280 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=384559
R=boliu@chromium.org
Review URL: https://codereview.chromium.org/335583005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277079 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This is the model I used for notifications and will use for other features as they move from RenderView to RenderFrame.
BUG=304341
R=avi@chromium.org, mkosiba@chromium.org
Review URL: https://codereview.chromium.org/330143002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277038 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add plumbing for registration from push service-agnostic content layer
to GCMDriver in chrome layer.
To achieve this, GCMProfileService owns an implementation of a new
PushMessagingService class, which can be used from the content layer.
Based on mvanouwerkerk's prototype in https://codereview.chromium.org/186023002, but significantly refactored.
BUG=350384
TBR=benm@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=276792
Review URL: https://codereview.chromium.org/317823007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277016 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=367221
Review URL: https://codereview.chromium.org/286903018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277009 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Split widevine_key_systems.(cc|h) into andorid_key_systems.* and
widevine_key_system.*.
- Add a method MediaDrmBridge::GetPlatformKeySystemNames().
BUG=322395
Review URL: https://codereview.chromium.org/320383005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276953 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://codereview.chromium.org/328713002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276932 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Android, the browser compositor lies to CC about the
device_scale_factor (always setting it to 1), because it places its
layers in physical pixel space. Because of that, the delegated device
scale inversion added in https://codereview.chromium.org/311253004 does
the wrong thing. Rather than cancelling the inversion with other
transforms, the simplest fix is to lie about the frame_data
device_scale_factor as well.
BUG=383572,383436,384134
NOTRY=true
Review URL: https://codereview.chromium.org/336433003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276882 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change caused the sole push_messaging layout test to fail :(.
> Hook PushMessagingMessageFilter up to GCMDriver
>
> Add plumbing for registration from push service-agnostic content layer
> to GCMDriver in chrome layer.
>
> To achieve this, GCMProfileService owns an implementation of a new
> PushMessagingService class, which can be used from the content layer.
>
> Based on mvanouwerkerk's prototype in https://codereview.chromium.org/186023002, but significantly refactored.
>
> BUG=350384
> TBR=benm@chromium.org
TBR=johnme@chromium.org
BUG=350384
Review URL: https://codereview.chromium.org/327423006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276834 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add plumbing for registration from push service-agnostic content layer
to GCMDriver in chrome layer.
To achieve this, GCMProfileService owns an implementation of a new
PushMessagingService class, which can be used from the content layer.
Based on mvanouwerkerk's prototype in https://codereview.chromium.org/186023002, but significantly refactored.
BUG=350384
TBR=benm@chromium.org
Review URL: https://codereview.chromium.org/317823007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276792 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This silences a line of log spew that's generated on every launch of a local
debug build.
BUG=none
TEST=less log spew
R=rsesek@chromium.org
TBR=jam@chromium.org
Review URL: https://codereview.chromium.org/333493002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276787 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows the android_aosp bot to better model the behavior of
the automerger.
We add a 'android_rsync_build' method to
android_webview/buildbot/deps_whitelist.py
which returns all black listed paths (not just blacklisted deps)
and has a list output format (as opposed to dictionary format of
the other methods).
Then we add the 'all_incompatible_directories' option to
android_webview/tools/webview_licenses.py to get all the
incompatible directories rather that just the unknown
ones. This exposes the same code the automeger uses directly as
a command line argument.
BUG=311868
Review URL: https://codereview.chromium.org/324813006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276639 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=377720
NOTRY=true
Review URL: https://codereview.chromium.org/302843002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276617 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=327046
Review URL: https://codereview.chromium.org/329473002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276287 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The DRM ID can be exploited to identify users. so the information
should be handled under user's explict permission.
This CL hooks up Chromium's permission request with Android Webview's
permission mechanism.
BUG=346841
Review URL: https://codereview.chromium.org/309553004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276149 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
kAboutScheme and kAboutBlankURL are used in code shared by iOS, and are general
enough to live in //url instead of //content.
TBR=yoz,benm
Review URL: https://codereview.chromium.org/325443002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275988 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old gallery was once removed. The CL reverts the files and adds a flag to take back the old gallery just in case.
BUG=380521
TEST=launch new/old Gallery.
R=mkosiba@chromium.org, yoshiki@chromium.org
Review URL: https://codereview.chromium.org/312093002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275976 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
We want to refactor AwRenderViewExt to AwRenderFrameExt, this is the
first cl in that sequence.
BUG=304341
Review URL: https://codereview.chromium.org/317043002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275842 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Since he is no longer on the project. Sniff. :'(
BUG=none
R=jln@chromium.org
Review URL: https://codereview.chromium.org/317243005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275756 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"Client" rather than "Delegate" is the canonical name for embedder delegate
interfaces.
Also renames TabAutofillManagerDelegate to ChromeAutofillClient.
BUG=none
TEST=compiles
R=blundell@chromium.org
Review URL: https://codereview.chromium.org/306053008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275612 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
That use is both wrong (request IDs are global) and unnecessary since cert
enrollment is not a multi-step process. There's some stub code and indirections
for prompting to add a cert that's never actually used. Collapse it all to
simplify things. Move other random things out of SSLTabHelper which is also
no longer necessary.
(If anything, this stuff should probably go through the downloads
infrastructure to inherit all the user-gesture and throttling checks.)
Also move the AddCertificate hook from render_view_id to render_frame_id.
BUG=376003
TEST=Visit https://davidben.net/mixed-content-test.html; Click button. Lock
icon should change to lock icon with warning.
Review URL: https://codereview.chromium.org/302653006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275503 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
The name AwRenderFrameObserver is insufficiently explicit since it
deals only with printing.
BUG=
Review URL: https://codereview.chromium.org/314103002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275256 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As we still don't have the infrastructure work to reuse the chrome
version number in place, bump the fake version number to 37.0.0.0 to
reflect that trunk is based on Chromium 37.
BUG=297522
NOTRY=true
Review URL: https://codereview.chromium.org/313183006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275152 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This had become important since the rewrite of gesture support into native
code. Previously, calls to ZoomSupportChangeListener ended up in an instance
of stateful Java class ZoomManager. But after the rewrite, these settings
go down into native through RenderWidgetHostAndroid which isn't there until
WebObservers receive OnRenderViewCreated.
BUG=381084
Review URL: https://codereview.chromium.org/313243005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275151 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This constant is used in code shared by iOS, and is general enough to be placed
in //url.
TBR=benm,yoz
Review URL: https://codereview.chromium.org/319613002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275055 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
transform origin.
This is the cc side change that listens to transform origin
instead of anchor point. Blink is already populating both
fields.
BUG=372837
Review URL: https://codereview.chromium.org/295193002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274990 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=380367
NOTRY=true
Review URL: https://codereview.chromium.org/314573006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274949 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In DevTools, if port 0 is requested, query the HttpServer for the port
actually used, and write the port to a well-known location: the file
"DevToolsActivePort" in the user's profile directory. Currently this
handshaking protocol is only implemented for Chromium, not
content_shell, but this is the only scenario in which flakiness has
been observed.
Add a hidden command-line argument to Telemetry's desktop browser
backend which uses this new code path. The bots will specify this
argument. Telemetry must support browsers two releases back, so once
Chrome 37 goes to the Stable channel, the old initialization path will
be removed. Issue 379980 has been filed to remove the old code.
Tested with and without the new --use-devtools-active-port command
line argument with -v. Verified the new code path is taken. Once these
changes are committed, the bots will begin verifying this new code.
BUG=372560
NOTRY=true
Review URL: https://codereview.chromium.org/315503002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274935 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently in AreURLsInPageNavigation, we only trust renderer_says_in_page if
the before and after urls are identical. This prevents us from correctly
classifying history.pushState and history.replaceState navigations as in-page.
Navigations via the history API are required to be same-origin, but can differ
by more than just the ref component, so we get the correct behavior without
the renderer process being able to lie about a cross-origin navigation.
BUG=138324
TEST=Added cases to NavigationControllerTest.IsInPageNavigation
Review URL: https://codereview.chromium.org/304763002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274734 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Request interceptors are the new way to handle intercepting URL
requests, to be used by ServiceWorkers and AppCache. This CL
hooks them up to the URLRequestContext in AndroidWebview.
BUG=350286
Review URL: https://codereview.chromium.org/294023015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274586 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change adds code to get gamepad data from java objects and
provide these updates to the GamepadProvider which then writes to
GamepadHardwareBuffer which in turn is read by SharedMemoryReader and
later returned by JS to the web page.
This also adds new framework classes/methods required for Gamepad API
support. Frameworks changes are responsible for :
- Identifying gamepad devices and their capabilities.
- Managing connected gamepad devices
- Map the connected gamepad devices to standard Gamepad format.
- Keeping gamepads axes/buttons data up-to-date and returning it to
native whenever requested. In android we cannot get gamepad data
directly from sources, so framework is modified to capture
gamepad key and motion events and extract gamepad data from these
events.
* Class GamepadPlatformDataFetcherAndroid : Android specific
implementation of gamepad data fetcher.
- Responsible for communication with java class and accessing gamepad data.
- It adds methods for communication with singleton java GamepadList class
to get gamepads data.
* Class ContentViewCore : Manages gamepad list and notifies of new
key/motion event for gamepads.
* Class GamepadList : A new class to manage connected gamepad devices
* Class GamepadDevice : A new class to manage information related to
each gamepad device.
* Class GamepadMappings : This class is responsible for mapping of
known gamepads to the standard gamepad.
This change enables gamepad API by default.
Adds support for parsing float array return type in JNI generator.
NVIDIA Shield and XBox360 gamepads are mapped to the standard gamepad
BUG=330094
TEST=http://www.html5rocks.com/en/tutorials/doodles/gamepad/gamepad-tester/tester.html
R=tsepez@chromium.org
R=darin@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=270620
Review URL: https://codereview.chromium.org/133943002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274212 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Webviews and OOP iframes now have non-empty parentId property pointing to the target they are nested into. Also added 'webview' and 'iframe' target types.
TBR=bulach,mnaganov (for dev_tools_server.cc aw_dev_tools_server.cc)
BUG=378457
Review URL: https://codereview.chromium.org/305903004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274178 0039d316-1c4b-4281-b951-d872f2087c98
|