GitLab

TBR=suzhe@chromium.org
BUG=407456
TEST=Verified on linux_chromeos & clapper device.

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

Cr-Commit-Position: refs/heads/master@{#329810}

Previously BatchableRequestBase can be used both as a normal request and as a
child request in BatchUploadRequest. Even when BatchableRequestBase is used as
child request, its lifetime must be managed by RequestSender, and it makes hard
to track the lifetime in BatchUploadRequest.

To simplify lifetime management in BatchUploadRequest, the CL extracts the core
part of BatchableRequestBase into BatchableDelegate, and lets BatchUploadRequest
use the delegate as a child request. Because the delegate is nolonger owned by
RequestSender, BatchUploadRequest can own its child requests without caring
RequestSender.

BUG=451917
TEST=googleapis_unittests

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

Cr-Commit-Position: refs/heads/master@{#329809}

And avoid dispatching onActivate & onDeactivated events to IME
extensions if the profile is not the active profile.

BUG=485835
TEST=Verified on linux_chromeos & clapper device.

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

Cr-Commit-Position: refs/heads/master@{#329808}

MessageLoopProxy is deprecated.
This basically does a search and replace of:

MessageLoopProxy::current() -> ThreadTaskRunnerHandle::Get().

MessageLoopProxy -> SingleThreadTaskRunner

BUG=391045

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

Cr-Commit-Position: refs/heads/master@{#329807}

BUG=487505
TEST=GYP_GENERATORS=ninja tools/gyp/gyp --depth . ui/file_manager/file_manager/background/js/compiled_resources.gyp && ninja -C out/Default

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

Cr-Commit-Position: refs/heads/master@{#329806}

It's been off by default since Chrome 40 with a policy opt-in. The policy was
documented to stop working after Chrome 43, so remove all logic for SSL 3.0.
Chrome will no longer honor a --ssl-version-min=ssl3 flag and the option is
removed from about:flags.

This CL also removes the SSL 3.0 support from the extensions' TLS socket API.

BUG=487730

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

Cr-Commit-Position: refs/heads/master@{#329805}

TEST=Tested manually in open dialog, and standalone Files app.
BUG=487905

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

Cr-Commit-Position: refs/heads/master@{#329804}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/7aa732b..0f5ff62

TBR=alancutter@chromium.org,jsbell@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#329803}

R=mkwst@chromium.org
BUG=478250

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

Cr-Commit-Position: refs/heads/master@{#329802}

The ResourceRecords must contain the ServiceWorker's main script.
So the size of it must be bigger than 1.

If the method returns STATUS_ERROR_CORRUPTED, DeleteAndStartOver() will be executed.

BUG=485900,478732

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

Cr-Commit-Position: refs/heads/master@{#329801}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/88c23fc..c30806f

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=robertphillips@google.com

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

Cr-Commit-Position: refs/heads/master@{#329800}

Previously we would invoke 'gn refs' once for each file modified in
a CL; this was terribly inefficient. Switching to a response file
makes things run much faster. This is a precursor to fixing
the actual problem in bug 487035, because we will be doubling the
number of times we need to call gn refs in the fix.

R=scottmg@chromium.org
BUG=487035
CQ_EXTRA_TRYBOTS=tryserver.chromium.mac:mac_chromium_gn_rel;tryserver.chromium.win:win8_chromium_gn_rel

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

Cr-Commit-Position: refs/heads/master@{#329799}

This is the Chromium side changes to record UMA stats for Gesture Editing on the Virtual Keyboard. A follow up CL will be written on Google3 to populate these stats.

BUG=487323

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

Cr-Commit-Position: refs/heads/master@{#329798}

Changes:
- Show "Retry" button only download is resume-able.
- Open chrome://downloads when user clicks a notification

BUG=477970
TEST=manually tested

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

Cr-Commit-Position: refs/heads/master@{#329797}

TEST=Tested manually with a fake provider extension.
BUG=474146

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

Cr-Commit-Position: refs/heads/master@{#329796}

BUG=487364

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

Cr-Commit-Position: refs/heads/master@{#329795}

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

Cr-Commit-Position: refs/heads/master@{#329794}

Gallery applies viewport both screen size cache, and full resolution image. To
handle the different size of two images, it used to set CSS 'width' and 'height'
style to the full resolution image so that the full resolution image can be
regarded as the same size of screen cache image.

But ImageView.Effect class, which is used for playing edit animation, does not
update the CSS properties. It causes wrong layout during the edit animation.

The CL removes the trick of CSS property, and let ImageView.Effect take into
account of the size of target canvas.

BUG=487129
TEST=Do and undo cropping and rotaiton.

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

Cr-Commit-Position: refs/heads/master@{#329793}

There is no need to limit the FSP API to non-incognito only. Especially, such
limitation was causing crashes in Files app running in incognito, which
assumed the service exists, but it didn't.

With this CL the service is created for both non-incognito and incognito pages.
Both instances are *same*, so mounted providers will be shared between incognito
and non-incognito windows.

TEST=Tested manually by launching with --incognito
BUG=487901

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

Cr-Commit-Position: refs/heads/master@{#329792}

TBR=suzhe@chromium.org
BUG=487914
TEST=Verified on linux_chromeos.

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

Cr-Commit-Position: refs/heads/master@{#329791}

BUG=487674
R=thakis@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#329790}

BUG=485381

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

Cr-Commit-Position: refs/heads/master@{#329789}

Cr-Commit-Position: refs/heads/master@{#329788}

Adds paper-fab, paper-toolbar and polymer/layout, which are required by
the material PDF viewer. Also adds required files from existing
components to polymer_resources.

BUG=482793

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

Cr-Commit-Position: refs/heads/master@{#329787}

During startup, Chrome expects synchronous display configuration, so we
need to present the list of displays before we get a chance to connect
to the GPU process. This patch will populate a list of dummy displays on
startup and the platform will pretend it can configure them until the
connection to the GPU process is established.

BUG=484294

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

Cr-Commit-Position: refs/heads/master@{#329786}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/d7eac4f..7aa732b

TBR=alancutter@chromium.org,jsbell@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#329785}

* Add a <select> element to the dialog allowing the user to choose a category, or "other".
* Disable the OK button and hide the reset options until a category is selected.
* Clean up some duplicated code now that this dialog depends on base.js.

BUG=b/20950552

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

Cr-Commit-Position: refs/heads/master@{#329784}

Noteworthy in this roll is that InterfacePtrs may no longer be
bound-to or passed-as simple pipe handles, but instead as
InterfacePtrInfos. This requires updating several call sites
of InterfacePtr's Bind and PassMessagePipe.

BUG=
TBR=ben@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#329783}

BUG=486187
TEST=covered by test

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

Cr-Commit-Position: refs/heads/master@{#329782}

Prior to this CL, the AutocompleteTextField becomes first responder if the user
left-clicks a decoration. This is a bug that this CL fixes. This also fixes a
bug where ZeroSuggest did not disappear when the user drags the origin chip.

BUG=356887

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

Cr-Commit-Position: refs/heads/master@{#329781}

Previously MessageReader was stopping reading after the first error,
but wasn't notifying the client about the problem. This results in some
errors (e.g. from SSL layer) being ignores while they should terminate
connection.

BUG=487451

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

Cr-Commit-Position: refs/heads/master@{#329780}

TBR=
BUG=

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

Cr-Commit-Position: refs/heads/master@{#329779}

TBR=oshima@chromium.org
BUG=487501

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

Cr-Commit-Position: refs/heads/master@{#329778}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/1ba8cc9..88c23fc

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=robertphillips@google.com

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

Cr-Commit-Position: refs/heads/master@{#329777}

the PLT histograms for LoFi.

This CL adds 2 more boolean parameters to an existing IPC call
that tells us whether the page load happened with LoFi on with
bad network conditions or LoFi off with
bad network  conditions. The methods in the data reduction
proxy code currently return false and would be fixed in the
forthcoming CL.

Auto LoFi status keeps changing (on a page load basis)
depending on the network conditions (e.g., enabled only when network
quality is bad). Just because session is in a field trial does
not guarantee that LoFi would ever be used.  Using a synthetic
trial or only using the field trial will give very
noisy data in this case.

This is a temporary CL for LoFi Android experiment. Eventually,
we want to read the LoFi status using the headers of the
response instead of reading the current LoFi status (which might
be a bit stale) but that requires putting custom
HTTP headers in the response message from data saver proxy.

BUG=485633

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

Cr-Commit-Position: refs/heads/master@{#329776}

For example:
- third_party/ffmpeg/libavcodec/arm/hpeldsp_arm.S
- third_party/ffmpeg/libavcodec/x86/xvididct.asm

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

Cr-Commit-Position: refs/heads/master@{#329775}

When the flag or field trial is set such that non-secure origins will be
marked as dubious/non-secure, use |IsOriginSecure| to determine whether
an origin is non-secure, instead of simply treating http:// and ftp://
as non-secure. This means that http://nytimes.com will be marked as
dubious/non-secure, but not http://localhost (for example).

BUG=487499
TEST=Enable the "Mark non-secure as non-secure" flag in
chrome://flags. Visit http://nytimes.com and observe that the lock icon
is red and crossed out. Visit an http:// URL on localhost and observe
that the lock icon is neutral.

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

Cr-Commit-Position: refs/heads/master@{#329774}

We log picture size in UMA histograms every time we
prepare to draw. In order to make that code faster,
precompute the pile size when it is constructed.

R=jbroman, enne

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

Cr-Commit-Position: refs/heads/master@{#329773}

TBR=oshima@chromium.org
BUG=487706

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

Cr-Commit-Position: refs/heads/master@{#329772}

R=dbeam@chromium.org
BUG=

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

Cr-Commit-Position: refs/heads/master@{#329771}