GitLab

R=ajuma
BUG=672077
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

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

This should greatly mitigate a current bug in the BattOr firmware where
sending the command to start tracing causes the BattOr to reset. In this
case, we now retry the full initialization sequence. Because the error
we're hitting is a timeout, and we allow 4 seconds for a command to
be executed before timing out, this means that initialization will
retry after 4 seconds and then make 20 attempts to initialize the BattOr
100 milliseconds apart from each other, making the whole sequence take
something like 6 additional seconds. We can retry this full sequence
up to 5 times. When added to the five or so seconds that the BattOr
already takes to initialize, this means that this full sequence might
take up to 11 * 5 = 55 seconds before deciding that the BattOr can't
be initialized. In practice, I suspect that almost all initializations
will succeed on either their first or second attempts.

BUG=672631

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

BUG=671768
R=dpranke@chromium.org, martiniss@chromium.org, maruel@chromium.org

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

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

BUG=672783
TBR=dgn@chromium.org

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

ModuleSystem::CallModuleMethod is deprecated (see bug for more info).
Convert some callers to use ModuleSystem::CallModuleMethodSafe.
Some callers need the results from the JS call, so introduce a
callback to the safe versions of CallModuleMethod and CallFunction.

BUG=629431

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

We decide to ship the intervention of 'Uncancelable Touch Events During A Fling',
so enable 'PassiveDocumentEventListeners' feature.

Below is the link to the discussion on blink-dev
https://groups.google.com/a/chromium.org/d/topic/blink-dev/wJGmsdYxwrg/discussion

BUG=595327

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

https://skia.googlesource.com/skia.git/+log/9bbfb657606d..a129dfef2aaa

$ git log 9bbfb6576..a129dfef2 --date=short --no-merges --format='%ad %ae %s'
2016-12-09 reed Revert "remove SK_SUPPORT_LEGACY_CLIP_REGIONOPS"
2016-12-08 herb Add the ability to use different mallocs.
2016-12-08 caryclark fix fuzzers
2016-12-08 reed remove SK_SUPPORT_LEGACY_CLIP_REGIONOPS
2016-12-08 jcgregorio Remove documentation about emboss.
2016-12-08 caryclark simplify bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
TBR=herb@google.com

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

BUG=644626

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

Previously the wall clock was being used but really it should be
the realtime clock.

BUG=625680

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

Previously BlobBytesConsumer expected no other one canceled its loader. But it
was not correct when ExecutionContext is shutting down. This CL fixes the
assumption.

BUG=666756
R=tyoshino@chromium.org

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

Scenario:
In the launcher subtree of the desktop tree, we have:
dialog
...
  web view
    root web area
    ...
   files button

A dialog with mixed web and views content.

When navigating forward, we search downward and get into the web view and find nothing inside, but when unwinding upward, we stop at the root web area because it gets matched by the root predicate.

In the end, we don't end up on the native views next in document order.

TEST=navigate with ChromeVox keys. Ensure we can get to the buttons.
BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

Re-landing https://crrev.com/2498113002 CL which was reverted because
bot's builder didn't build tracing_perftests target.
It has been fixed https://chromium-review.googlesource.com/c/417166 .

BUG=656029,666828

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

Just noticed that it fails sometimes on our (yandex) bots.
transmitted_start can indeed be equal to the lower bound here.

BUG=

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/722a4d56..167cbe51

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_trusty_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/2568463002
Cr-Commit-Position: refs/heads/master@{#437535}

BUG=672774

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

https://codereview.chromium.org/2516353002/ introduces URL list of Response.

This URL list is an internal value which is not exposed to script.
To check the list in the LayoutTest, this CL introduces an internal API
getInternalResponseURLList().

BUG=658249

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

The build number would be added to the version string in UA
only if the major version of Windows is equal or greater than 10.
Nothing would be changed for the old version of Windows.

BUG=664622

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

This updates the code to match the documentation in
service_worker_context.h.

BUG=591427

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

BUG=672527
CQ_INCLUDE_TRYBOTS=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;master.tryserver.chromium.android:android_optional_gpu_tests_rel

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

TBR=dtu@chromium.org

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

Also renames payment_address to shipping address in PaymentRequest to match the specs

BUG=602666

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

We don't assign is_epoll_wait to anything in EpollEvent, and thus it is
unused. So there is no reason to keep it there from now on.

BUG=None
TEST=net_unittests
R=rch@chromium.org

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

TBR=jam@chromium.org
BUG=556939

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

As the downstream code has been updated to use the upstream version
of the resources (and there is no risk of multiple targets creating
the same file in the application bundle), add the dependency to the
:settings_resources upstream.

BUG=672516

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

```--
With PlzNavigate, main frame navigations
don't have a valid (render_process_id, render_frame_id). This CL is a
preliminary refactoring to properly support PlzNavigate.

Details
```

--
To be able to do browser navigations to non yet created frames, we use
webcontents that will always be available. This is preparation work
to be able to use webcontents identification instead of frame ids easily.

At the higher level we are passing a WebContentsGetter and run it on a
UI thread, leading to new dedicated functions in the observer. We then
use a wrapper to initialize the NavigationID part of the request summary.
SummarizeResponse is not responsible for filling in NavigationID any more,
and the behavior has been updated in unit tests.

BUG=631966

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

BUG=348655

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

Suspicious root cause of the last revert was fixed. See crbug.com/670638.
Description from https://crrev.com/dc8303234f47ccfc841185d33c45e4852776b65e:

This CL introduces adaptive webfont display behavior, reducing unnecessary Flash
of Unstyled Text (FOUT) if webfont is already available in disk cache.  This is
available as a experimental Web Platform feature.

In webfont display, fallback font will be used if webfont loading time exceeds
certain timeout values in slow network. However it's observed that disk cache
RTT may also hit the timeout regardless of network speed. In such cases we would
like to block display until disk cache misses and actual network request is
being sent.

BUG=570205
TBR=isherman@chromium.org

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

As discussed in https://codereview.chromium.org/2556743002/,
formatting is strange "because clang-format tries to align
columns, even if there's only one row with aligned columns.
I agree that this looks weird, and it sounds like it will be
fixed."

Removing the "// clang-format off" section as it has a cost
since it requires developer to manually code format the region.

BUG=None

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

This intervention only changes code in CC, so We do not need this flag in Webkit,
removing the flag from Webkit's WebRuntimeFeatures.

BUG=595327

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/72905fa4..722a4d56

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_trusty_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/2564803002
Cr-Commit-Position: refs/heads/master@{#437519}

This only checks the request priority. Next: attempt to reliably intercept cases
when request priority gets upgraded.

Changes prerender::test_utils::CreatePrefetchOnlyInterceptorOnIO(...) to a more
generic prerender::test_utils::InterceptRequestAndCount(..., callback).

BUG=none

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

Now, NavigationController has multiple Reload*() methods to trigger
various kinds of reload operations. But this is confusing because it
takes one boolean argument, and in some contexts, one boolean argument
for reload means a flag to bypass caches.
Also, using one method and calling it with ReloadType flag is more
consistent with other navigation related implementation in Blink.

This is the first patch to introduce new Reload method with ReloadType
argument. Once this patch is submitted, other changes will follow to
call the new Reload from several places, and remove Reload* methods.

BUG=670232
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
TBR=jam@chromium.org

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

INPUT element: Do not use identical ID name for SearchFieldCancelButtonElement and ClearButtonElement.

Using identical ID for different Element subclasses is dangerous.
This CL avoids a runtime CHECK failure.

BUG=669847

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

BUG=668997

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

This patch has no functional change, but will allow subsequent patches
to specify a different target color space depending on their application
(e.g, canvas and WebGL can request sRGB, and raster can request
the output device behavior).

BUG=667420

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

Chrome iOS is moving to Objective-C Automatic Reference Counting. Under
it, arguments are supposed to be autoreleased. This CL adds a new
constructor that can take both a retained and an autoreleased object.
This is a part of a multiple CL setup that will change the Image(UIImage*) constructor from consuming +1 refcount to retaining the argument.

TEST=none
BUG=645125

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

According to the base/files/file.h, the GetLength() method should return
a negative number on failure.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng

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

BUG=chromium:671511
TEST=trybot

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

We used CHECKs to confirm if these checks are valid and can survive
on Canary. Now that we know these are correct, let's make it back
to DCHECKs.

BUG=670638

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