GitLab

Note that private dirty is already measured on Android.

BUG=347919

Review URL: https://codereview.chromium.org/190743002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255913 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255912 0039d316-1c4b-4281-b951-d872f2087c98

The Blink roll broke browser_tests in Chromium OS:
http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%282%29/builds/22180

> Blink roll 168755:168805
> 
> http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=168756:168805&mode=html
> TBR=
> BUG=
> 
> Review URL: https://codereview.chromium.org/192373003

TBR=haraken@chromium.org

Review URL: https://codereview.chromium.org/192373006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255911 0039d316-1c4b-4281-b951-d872f2087c98

* Drop SyncTaskManager::Schedule{,Sync}Task
* Rename Schedule{,Sync}TaskAtPriority to Schedule{,Sync}Task

BUG=344769

Review URL: https://codereview.chromium.org/190663004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255909 0039d316-1c4b-4281-b951-d872f2087c98

The componentization is straightforward, following the patterns of other
Autofill test componentizations.

BUG=303083
R=isherman@chromium.org

Review URL: https://codereview.chromium.org/177013005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255908 0039d316-1c4b-4281-b951-d872f2087c98

Currently we do this header-fixup in two places: PartialData and AppCache,
and I'm planning to do the very same header-fixup in yet another module,
ServiceWorker.  I want to have a common utility in net/http/http_util
to do this so that all 3 modules can share it.

BUG=349319
TEST=HttpResponseHeadersTest.UpdateWithNewRange

Review URL: https://codereview.chromium.org/187583002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255905 0039d316-1c4b-4281-b951-d872f2087c98

BUG=350533

Review URL: https://codereview.chromium.org/190063008

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255904 0039d316-1c4b-4281-b951-d872f2087c98

This renaming puts the Signin embedder interface in line with the agreed-upon
convention wherein a component Foo's embedder interface should be named
FooClient. ChromeSigninManagerDelegate is similarly renamed to
ChromeSigninClient, and variable names are updated.

BUG=334168
TBR=joi

Review URL: https://codereview.chromium.org/192253002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255903 0039d316-1c4b-4281-b951-d872f2087c98

BUG=347557

Review URL: https://codereview.chromium.org/182623003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255902 0039d316-1c4b-4281-b951-d872f2087c98

This moves the core functionality (frontend, backend and local storage
implementations) to src/extensions while leaving Chrome-specific sync storage
and managed storage implementations in src/chrome.

BUG=348058
TEST=unit_tests *Storage*:*Settings* browser_tests ExtensionSettings*
TBR=zea@chromium.org for header file move touching chrome/browser/sync/test/integration/extension_settings_helper.cc

Review URL: https://codereview.chromium.org/189263013

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255901 0039d316-1c4b-4281-b951-d872f2087c98

Linux is unaffected. All changed code already is inside sandbox.

BUG=348692

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=255311

Review URL: https://codereview.chromium.org/185293014

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255900 0039d316-1c4b-4281-b951-d872f2087c98

This CL adds a Show and Hide to the app list SearchBoxView in preparation
for work pertaining to the experimental app list. The Show and Hide also
require that the AppListView's background repaints which have required
changes to the AppListView, AppListMainView and SearchBoxViewDelegate.

BUG=349727

Review URL: https://codereview.chromium.org/185623002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255899 0039d316-1c4b-4281-b951-d872f2087c98

H.264 standard allows for an optional max_num_reorder_frames parameter to be
specified in VUI parameters. When present, it indicates the maximum number
of frames that may precede a given frame in decode order, but come after it
in output order. This means, that if the number of decoded and not yet outputted
frames exceeds max_num_reorder_frames, we are allowed to output until this no
longer holds true.

In case max_num_reorder_frames is not present, the value is to be inferred
to be either 0 or equal to the size of DPB. In case of the latter, we would
always have to wait until the DPB is full before outputting anything. This means
we could incur visible stuttering whenever DPB had to be cleared (on IDRs,
etc.). max_num_reorder_frames seems to be very common in streams these days
however, so it should be a relatively rare occurrence.

Relying on max_num_reorder_frames also gives us an ability to handle streams
with negative POC values, which are produced by some camera models.

TEST=video playbacks, vdatest, switchtests
BUG=chromium:177692

Review URL: https://codereview.chromium.org/177583002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255898 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255897 0039d316-1c4b-4281-b951-d872f2087c98

http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=168756:168805&mode=html
TBR=
BUG=

Review URL: https://codereview.chromium.org/192373003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255896 0039d316-1c4b-4281-b951-d872f2087c98

FinishCommit() is used to inform that painting is complete and we can
ready to commit to scheduler.
So, NotifyReadyToCommit() is more suitable for its role.

R=brianderson@chromium.org
BUG=349889
TEST=None (No functional change)

Review URL: https://codereview.chromium.org/191293004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255895 0039d316-1c4b-4281-b951-d872f2087c98

Forced commit only should proceed to its BeginMainFrame when there is a
scheduled BeginMainFrame().
So, Forced commit only should wait for COMMIT_STATE_BEGIN_MAIN_FRAME_SENT.

R=brianderson@chromium.org
BUG=350585
TEST=cc_unittests

Review URL: https://codereview.chromium.org/189553007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255894 0039d316-1c4b-4281-b951-d872f2087c98

We configure opus to encode at 48khz. But on some platforms like Linux
the incoming data is at 44.1khz. We need to resample the data before
giving it to the cast library.

Fixing this allows us to have proper audio with a receiver.

BUG=349295

Review URL: https://codereview.chromium.org/187493002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255893 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255892 0039d316-1c4b-4281-b951-d872f2087c98

Upon receiving a resource, if it is a file system, the V8 Var converter
automatically converts it into a Blink DOMFileSystem and makes it
available in the V8 JavaScript context.

This also adds the possibility of converting other resource types to
JavaScript objects in the future.

BUG=345158

Review URL: https://codereview.chromium.org/173143005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255891 0039d316-1c4b-4281-b951-d872f2087c98

TBR=nyquist@chromium.org
BUG=80194,348951

Review URL: https://codereview.chromium.org/183563004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255890 0039d316-1c4b-4281-b951-d872f2087c98

This adds cancellation ability for the clients that will need it. Adds
user gesture awareness to the API. Removes button customization. Adds icons.
Some code reorganization as well.

R=leng@google.com
BUG=332115

Review URL: https://codereview.chromium.org/176053002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255889 0039d316-1c4b-4281-b951-d872f2087c98

With the change to Blink only needing the monotonic time the wall time can be
removed.

DEPS=185633002,185643002
BUG=299945

Review URL: https://codereview.chromium.org/184433007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255888 0039d316-1c4b-4281-b951-d872f2087c98

information from disk cache.

R=rch@chromium.org

Review URL: https://codereview.chromium.org/189963002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255887 0039d316-1c4b-4281-b951-d872f2087c98

Instead, call it once at creation, and then call addSublayer
to cover up the layer when content comes in.

Remove the atomic add-layer-and-remove-old-one functions,
since the new arrangement allows adding the new layer before
removing the old one.

Change places that used [self layer] to explicitly call out to the
software and compositing layers.

The reason for this change is that it is not safe to dynamically
call setLayer on NSViews because of the following undocumented
feature of CoreAnimation:

Ordinarily, the NSView hierarchy and the CALayer hierarchy
match. That is, the ordering of a NSView's subviews' CALayers is
the same as the ordering of the NSView's CALayer's sublayers.
This gets completely broken when you call setLayer on a NSView.
The new CALayer will be appended to the end of the NSView's
superview's CALayer's sublayer array, even if that NSView wasn't at
the end of its superview's subview array.

BUG=348490

Review URL: https://codereview.chromium.org/188873005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255886 0039d316-1c4b-4281-b951-d872f2087c98

R=asvitkine@chromium.org
BUG=287730

Review URL: https://codereview.chromium.org/179873004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255885 0039d316-1c4b-4281-b951-d872f2087c98

CustomFrameViewAsh::GetMaximumSize() should add the height of the
title bar, if a maximum size constraint is specified.

BUG=349229
TEST=ash_unittests (CustomFrameViewAshTest.*)

Review URL: https://codereview.chromium.org/183793011

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255884 0039d316-1c4b-4281-b951-d872f2087c98

Review URL: https://codereview.chromium.org/187173002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255883 0039d316-1c4b-4281-b951-d872f2087c98

Move location marker to make logs meaningful.

BUG=344769

Review URL: https://codereview.chromium.org/190243003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255882 0039d316-1c4b-4281-b951-d872f2087c98

The main use of the settings app is to switch profiles in the app
when you are signed out. For this to be useful it is important that the
sign in enforcement does not happen for the settings app.

BUG=347025

Review URL: https://codereview.chromium.org/190143003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255881 0039d316-1c4b-4281-b951-d872f2087c98

Removed the title to make the tabs start at the very top of the dialog.

Has 3 tabs: Summary, Permissions and Manage
- The Summary tab displays the app's icon, name, version and description.
- The Permissions tab displays the app's permissions as a scrollable list
- The Manage tab is currently empty.

BUG=266739

Review URL: https://codereview.chromium.org/180723010

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255880 0039d316-1c4b-4281-b951-d872f2087c98

[IME] Removes the duplicated IMEs in chrome://settings/languages, and support async component IMEs loading in oobe network screen, and fix the wrong indicator issue.

BUG=345604,349829
TEST=None
TBR=nona@chromium.org

Review URL: https://codereview.chromium.org/190033005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255879 0039d316-1c4b-4281-b951-d872f2087c98

HeaderPainter::GetWindowBoundsForClientBounds() shifts the Y
coordinate of the window bounds to ensure it is not negative.
This causes NativeAppWindowViews::GetFrameInsets() to compute
the wrong insets.

Therefore we should leave the Y coordinate of the window bounds
negative in HeaderPainter::GetWindowBoundsForClientBounds().

BUG=349220
TEST=browser_tests (AppWindowBrowserTest.*)

Review URL: https://codereview.chromium.org/180803013

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255878 0039d316-1c4b-4281-b951-d872f2087c98

Code in content always gets it now from ContentClient::GetUserAgent. In Chrome, there's a GetUserAgent function which returns it.

BUG=338338
R=isherman@chromium.org, pauljensen@chromium.org, scottmg@chromium.org, tfarina@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=255858

Review URL: https://codereview.chromium.org/191093002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255877 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255873 0039d316-1c4b-4281-b951-d872f2087c98

There are some browser_tests failures on the buildbots that don't reproduce locally. Reverting while I investigate.

> Simplify the user agent code some more since after r255534 it's not affected by the site's URL.
> 
> Code in content always gets it now from ContentClient::GetUserAgent. In Chrome, there's a GetUserAgent function which returns it.
> 
> BUG=338338
> R=isherman@chromium.org, pauljensen@chromium.org, scottmg@chromium.org, tfarina@chromium.org
> 
> Review URL: https://codereview.chromium.org/191093002

TBR=jam@chromium.org

Review URL: https://codereview.chromium.org/192283002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255867 0039d316-1c4b-4281-b951-d872f2087c98

Convert ContentMain to take a struct instead of parameters that vary depending on the platform. This helps reduce ifdef mess, and makes it easier to add extra optional parameters. In a followup cl, I'll move the ui_task parameter from MainFunctionParams to ContentMainParams.

BUG=350550
R=sky@chromium.org

Review URL: https://codereview.chromium.org/190853004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255866 0039d316-1c4b-4281-b951-d872f2087c98

Changing the UsersPerSession UMA metric to count relative user amount changes for sessions which can do multi profile

The old absolute UMA counter was stored upon shutdown. Unfortunately only one in 33 users is shutting down the system properly. As such only a fraction of sessions were accounted for => the values were useless. Furthermore we have decided to only count sessions which could be multi profile sessions.

The new values are recording state changes like e.g. going from one user to two in a single session. As such you might get a resulting stat counter list of:

1: 320 => 320 - 15 - 4 - 1 = 300 single user sessions
2: 15  =>       15 - 4 - 1 = 10  two user sessions
3: 4   =>            4 - 1 = 3   three user sessions
4: 1   =>                    1   four user session

Note that it is not possible for a single user to leave a multi profile session - so the counter will always count up.

BUG=349055
TEST=none

Review URL: https://codereview.chromium.org/180243025

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255865 0039d316-1c4b-4281-b951-d872f2087c98

BUG=350421

Review URL: https://codereview.chromium.org/191003002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255864 0039d316-1c4b-4281-b951-d872f2087c98

This is part of the "always maximized" feature. Windows which cannot be maximized - or cannot be made to cover the entire screen should have a backdrop behind them which covers the desktop.

Tried various ways to implement this and this seems to be the best solution.

BUG=337567, 337563

Review URL: https://codereview.chromium.org/169643005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255863 0039d316-1c4b-4281-b951-d872f2087c98