GitLab

This is an automated CL created by the recipe roller. This CL rolls recipe
changes from upstream projects (e.g. depot_tools) into downstream projects
(e.g. tools/build).

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug
(or complain)

build:
  https://crrev.com/b7b68b4c0396453d775c7fb924d45bbfdff6f349 Updating perf recipe for disabled chartjson data. (eyaich@chromium.org)

TBR=martiniss@chromium.org,phajdan.jr@chromium.org
BUG=chromium:647714

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Review-Url: https://codereview.chromium.org/2373793002
Cr-Commit-Position: refs/heads/master@{#421192}

Reverted in
https://codereview.chromium.org/2349253002

Reason for revert:
Tests are failing on Mac ASAN builder. See details here:
https://uberchromegw.corp.google.com/i/chromium.memory/builders/Mac%20ASan%2064%20Tests%20(1)

BUG=633136

Review-Url: https://codereview.chromium.org/2353333002
Cr-Commit-Position: refs/heads/master@{#421191}

With this CL, a FileDescriptorWatcher is instantiated on every
base::Thread that runs a MessageLoopForIO. This allows
FileDescriptorWatcher::WatchReadable/WatchWritable to be used
on these threads.

BUG=645114

Review-Url: https://codereview.chromium.org/2372583002
Cr-Commit-Position: refs/heads/master@{#421190}

When the payment request is updated using updateWith,
the PaymentDetails can contain a message in the error field
that will be displayed to the user.

https://w3c.github.io/browser-payment-api/#paymentdetails-dictionary
https://github.com/w3c/browser-payment-api/pull/257

BUG=648240

Review-Url: https://codereview.chromium.org/2355463002
Cr-Commit-Position: refs/heads/master@{#421189}

This function was doing the wrong thing on Mac, so it has been removed and
the default implementation simply inlined into LabelButton.

BUG=649367

Review-Url: https://codereview.chromium.org/2358913006
Cr-Commit-Position: refs/heads/master@{#421188}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/c1f1fe14..c47acc29

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,littledan@chromium.org,vogelheim@chromium.org

Review-Url: https://codereview.chromium.org/2372883003
Cr-Commit-Position: refs/heads/master@{#421187}

This will be used to provide custom-styled text fields for use in UI.

BUG=None

Review-Url: https://codereview.chromium.org/2372703002
Cr-Commit-Position: refs/heads/master@{#421186}

Protected by FLAGS_chromium_http2_flag_log_compressed_size.

This CL lands server change 133714721 by yasong.

BUG=488484

Review-Url: https://codereview.chromium.org/2367973002
Cr-Commit-Position: refs/heads/master@{#421185}

On Android, navigations for interstitials go through the network stack.
Not having a NavigationHandle for them prevents us from enforcing that
every navigation has a NavigationHandle. This CL fixes and adds this
requirement.

BUG=621856
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2364943002
Cr-Commit-Position: refs/heads/master@{#421184}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/333ad9c490dd..6c8709c0cc9d

$ git log 333ad9c49..6c8709c0c --date=short --no-merges --format='%ad %ae %s'
2016-09-27 hjd Makes tracing favicons less pixelated

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2372143003
Cr-Commit-Position: refs/heads/master@{#421183}

As defined in https://w3c.github.io/webappsec-csp/embedded/#dom-htmliframeelement-csp.

BUG=647588

Review-Url: https://codereview.chromium.org/2370783002
Cr-Commit-Position: refs/heads/master@{#421182}

Right now these two tests:
fast/canvas/webgl/offscreenCanvas-transferToImageBitmap.html
fast/canvas/webgl/offscreenCanvas-transferToImageBitmap-in-worker.html
are not working properly on Mac if we drag them to the browser. And the
reason is that DrawingBuffer()'s transferToStaticImage() returns a
StaticBitmapImage that is always black because the WebGLImageChromium
flag is enabled.

This CL disable this flag when creating a DrawingBuffer() inside the
WebGLRenderingContextBase's constructor, if the creation is requested
by a offscreenCanvas.

This change will also fix the failure of gpu pixel test for commit() on
Mac because commit() method depends on DrawingBuffer()'s transferToStaticImage()
as well.

Moreover, since the layout test doesn't really compare the composited
result, we should probably turn the above two layout tests into pixel
tests.

BUG=649668
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2365653005
Cr-Commit-Position: refs/heads/master@{#421181}

This patch converts "editing/selection/document-mutation.html" to use w3c test
harness to simplify test case for improving code health.

BUG=n/a
TEST=n/a; no behavior changes

Review-Url: https://codereview.chromium.org/2368263003
Cr-Commit-Position: refs/heads/master@{#421180}

```yaml
This is a reland of https://codereview.chromium.org/2125763003 which
was reverted because it broke the Win10 builder. It should not break
anything now that TestSimpleTaskRunner is thread-safe
(https://codereview.chromium.org/2296923003)
```

Why? The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads are migrated to
base/task_scheduler, tasks will no longer have access to a MessageLoop
but they will be able to get the current ThreadTaskRunnerHandle.

Before this CL, ObjectWatcher implemented
WillDestroyCurrentMessageLoop() to stop the watch when the
MessageLoop responsible for running the callback was destroyed.
This prevented the watch callback from being sent to a destroyed
MessageLoop.

Now that ObjectWatcher keeps a reference to a TaskRunner, this is
no longer required. The TaskRunner can't be deleted while there are
references to it. If the underlying MessageLoop has been deleted
when the watch callback is posted, the callback will simply not run.

Note that the watch will still be stopped when the ObjectWatcher is
deleted.

TBR=ben@chromium.org
BUG=650318

Review-Url: https://codereview.chromium.org/2365423003
Cr-Commit-Position: refs/heads/master@{#421179}

This CL enables tab discarding by default and keeps the existing feature only as a kill switch.

BUG=551995

Review-Url: https://codereview.chromium.org/2373653002
Cr-Commit-Position: refs/heads/master@{#421178}

HTMLTreeBuilderSimulator needs to line up with HTML parsing. r403630
tried to bring them closer together, but this regressed some existing
sites. This should be relanded but it needs to make the parser and
simulator more reliably consistent.

BUG=542803,639541

Review-Url: https://codereview.chromium.org/2366203006
Cr-Commit-Position: refs/heads/master@{#421177}

Use modified Read and delegate methods from the following
CL - https://codereview.chromium.org/2262653003/

BUG=423484

Review-Url: https://codereview.chromium.org/2309793002
Cr-Commit-Position: refs/heads/master@{#421176}

That achieves the following:
 - It makes sure the task doesn't run (significantly) before its initial period has elapsed. In practice, the scheduler seems to behave like that anyway, but it doesn't guarantee that, so we shouldn't rely on it.
 - It gives the scheduler a bit of room to optimize for battery life.

BUG=646842

Review-Url: https://codereview.chromium.org/2366813003
Cr-Commit-Position: refs/heads/master@{#421175}

https://chromium.googlesource.com/skia.git/+log/6a259bfcc80a..a99b66d95b4d

$ git log 6a259bfcc..a99b66d95 --date=short --no-merges --format='%ad %ae %s'
2016-09-27 brianosman Remove outdated comments about pre-sk_sp semantics
2016-09-27 jvanverth Clamp Vulkan caps to INT_MAX
2016-09-26 reed Revert "Revert "replace Arithmetic xfermode with imagefilter""
2016-09-26 mtklein Focus -Wno-over-aligned to just 32-bit x86 Android.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
TBR=fmalita@google.com

Review-Url: https://codereview.chromium.org/2372813003
Cr-Commit-Position: refs/heads/master@{#421174}

I ran clang-tidy (https://chromium.googlesource.com/chromium/src/+/master/docs/clang_tidy.md) on components/ntp_snippets/ and fixed a bunch of the non-false-positives :)

BUG=none

Review-Url: https://codereview.chromium.org/2368583002
Cr-Commit-Position: refs/heads/master@{#421173}

Wires in postmortem report collection, which harvests unclean shutdown
debug information to a protocol buffer, wraps this proto inside a
barebone minidump and registers the minidump with CrashPad for upload.
Reports are collected as part of the metrics service client
initialization task chain. Stability file naming is revised so a unique
file name is used every time.

Notes:
- This is experimental work that currently only targets the windows canary
channel (using an experiment).
- CrashPad handles consent checking/uploading/throttling.
- Manufacturing the minidump is a temporary approach. Longer term, Crashpad
should handle it.
- This first version also collects reports for crashes. Longer term, the
reports pertaining to crashes will be bundled with the crash reports.

TEST
- launch chrome with the stability instrumentation (--enable-features=StabilityDebugging)
- crash chrome by visiting chrome://chrome://inducebrowsercrashforrealz
- Validate the existence of a stability file in <user-data-dir>/Stability
- start chrome again
- validate "ActivityTracker.Collect.*" metrics chrome://histograms/ActivityTracker
- validate the presence of a new crash at chrome://crashes

BUG=620813

Review-Url: https://codereview.chromium.org/2344343002
Cr-Commit-Position: refs/heads/master@{#421172}

This CL adds a new way do dispatch tasks at the beginning of the application.
Before the tasks were run after an arbitrary delay. Now the tasks can be run
sequentially with a small delay between each.
It also deprecate the previous method.

BUG=227553

Review-Url: https://codereview.chromium.org/2217083002
Cr-Commit-Position: refs/heads/master@{#421171}

This CL implements BlobBytesConsumer which will replace
FetchBlobDataConsumerHandle.

BUG=610195

Review-Url: https://codereview.chromium.org/2287323002
Cr-Commit-Position: refs/heads/master@{#421170}

As of https://codereview.chromium.org/2103243002/, PowerSaveBlockerAndroid
accesses the ViewAndroid pointer it is passed only at a time when that
ViewAndroid pointer is guaranteed to be valid.  This CL moves
PowerSaveBlockerAndroid away from consuming the ViewAndroid pointer as a
WeakPtr. The concrete motivation is to eliminate WakeLockServiceContext needing
to listen for WebContentsObserver::WebContentsDestroyed() as part of decoupling
the wake lock service from //content.

BUG=612346

Review-Url: https://codereview.chromium.org/2371723002
Cr-Commit-Position: refs/heads/master@{#421169}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/1518c0d9..c1f1fe14

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,littledan@chromium.org,vogelheim@chromium.org

Review-Url: https://codereview.chromium.org/2369013005
Cr-Commit-Position: refs/heads/master@{#421168}

BUG=643545

Review-Url: https://codereview.chromium.org/2365363002
Cr-Commit-Position: refs/heads/master@{#421167}

This patch speeds up the creation of new execution contexts, by not requiring V8 objects to be already instantiated in order to attach origin-trial-controlled attributes. Instead, any attributes which need to be bound are attached to the interface and prototype when the constructor for the object is first accessed.

BUG=327148

Review-Url: https://codereview.chromium.org/2260113002
Cr-Commit-Position: refs/heads/master@{#421166}

SuggestionsSource's lifetime is tied to the NewTabPage meaning that if objects
take local copies of SuggestionsSource they are unable to determine if it has
been destroyed.

BUG=649299

Review-Url: https://codereview.chromium.org/2366443005
Cr-Commit-Position: refs/heads/master@{#421165}

This patch also drive-by eliminates a |createVisiblePositionDeprecated|
in |CompositeEditCommand::prepareWhitespaceAtPositionForSplit|.

BUG=648949

Review-Url: https://codereview.chromium.org/2368903002
Cr-Commit-Position: refs/heads/master@{#421164}

TEST=unit_tests passed
BUG=643085

Review-Url: https://codereview.chromium.org/2348813002
Cr-Commit-Position: refs/heads/master@{#421163}

Luckily both implementers of AccountSigninView.Delegate already implement
getFragmentManager() methods, so this change really is minimal.

BUG=646978

Review-Url: https://codereview.chromium.org/2360783004
Cr-Commit-Position: refs/heads/master@{#421162}

Makes FooAttribute{G,S}etter{,Callback} a little more readable.

BUG=

Review-Url: https://codereview.chromium.org/2342053002
Cr-Commit-Position: refs/heads/master@{#421161}

This CL prevents timing attributes to be set if a navigation has not
navigated yet. There is such a navigation, because the FrameLoader
create at least 2 DocumentLoader :
- init()      -> A fake navigation to an empty url.
- startLoad() -> The real navigation.

TEST=TracingBrowserTest.TestBackgroundMemoryInfra
     with --enable-browser-side-navigation

BUG=576261

Review-Url: https://codereview.chromium.org/2359723007
Cr-Commit-Position: refs/heads/master@{#421160}

layer position in PaintLayerCompositor and GraphicsLayer.

It makes more sense to use the area's scrollOrigin() instead of the
minimumScrollPosition(), as the minimumScrollPosition may be
overridden by users of the area (see e.g.
https://codereview.chromium.org/2096633002/).

BUG=625084
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

Review-Url: https://codereview.chromium.org/2169483002
Cr-Commit-Position: refs/heads/master@{#421159}

Instead, store the currently-scheduled intervals in prefs, and only reschedule when something changed.

BUG=646842

Review-Url: https://codereview.chromium.org/2363753002
Cr-Commit-Position: refs/heads/master@{#421158}

WaylandScreen is used to keep track of the current outputs
(display) that are available to Wayland clients.

This is a part of upstream work for the ozone-wayland project:
https://github.com/01org/ozone-wayland

BUG=578890
TEST=WaylandDisplayTest.Output

Review-Url: https://codereview.chromium.org/2042503002
Cr-Commit-Position: refs/heads/master@{#421157}

We don't need this anymore.
Keep SnippetsBridge.rescheduleFetching() though - we'll need this to re-schedule tasks from the Java side after an application upgrade (which clears them all).

BUG=646842

Review-Url: https://codereview.chromium.org/2357163004
Cr-Commit-Position: refs/heads/master@{#421156}

navigator.credentials is backed by MockCredentialManagerClient when
running layout tests. If two tests are run in sequence on the same
content_shell, the earlier test's configuration affects the following
one. Actually, passwordcredential-fetch.html is consistently failing.

Fix this by adding clean up logic to user of the mock configuration
API.

R=mkwst@chromium.org
BUG=650561

Review-Url: https://codereview.chromium.org/2373503003
Cr-Commit-Position: refs/heads/master@{#421155}

We need to support sequence as IntersectionObserverCallback uses
a sequence.

BUG=648486

Review-Url: https://codereview.chromium.org/2350813005
Cr-Commit-Position: refs/heads/master@{#421154}

Also drop creation and destruction of the JSONReader object because the fuzzed
method is static anyways.

BUG=none

Review-Url: https://codereview.chromium.org/2348053002
Cr-Commit-Position: refs/heads/master@{#421153}