GitLab

With browser-side-navigation, there are no trace of previous navigation
responses in the redirect chain. This CL forward these informations to
blink for making the Resource Timing API working.

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

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

ServiceWorkers without FetchEvent handlers should not be started up on navigation, see https://crbug.com/616502#c38

BUG=616502,640132

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

BUG=563793

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

https://chromium.googlesource.com/skia.git/+log/ee843b2ae4d7..1818701746e4

$ git log ee843b2ae..181870174 --date=short --no-merges --format='%ad %ae %s'
2016-10-04 borenet Add retries to upload_dm_results

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

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

This CL uploads the browser_test filter for PlzNavigate following the
fix made to the Webrequest API.

BUG=575224
TBR=nasko@chromium.org

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

This CL removes 3 ServiceWorker tests from the exclusion filter for
layout_tests with PlzNavigate enabled. They are now working.

BUG=440463
TBR=nasko@chromium.org

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

BUG=563793

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

For object tracing during heap profiling we still need to create retainment
infos to preserve current behavior.

BUG=chromium:468240,chromium:644213

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

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

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

https://pdfium.googlesource.com/pdfium.git/+log/b73c99335bfb..429a9ffa075b

$ git log b73c99335..429a9ffa0 --date=short --no-merges --format='%ad %ae %s'
2016-10-04 caryclark update skia to latest sources

TBR=dsinclair@chromium.org

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

My patch http://crrev.com/b3b697fc8bcc938e8b9ab32a34fc5933494faaa1 broke
the PingLoader code path for CSP violation reporting by always passing
AllowStoredCredentials by mistake.

The test report-cross-origin-no-cookies.html (now named .php) introduced
by http://crrev.com/a161a28377d8d71b63a02066574fb47f03dd4b3b included a
sync XHR to set a cookie for the remote host, but it has been not
working because:
- its withCredentials is not set to true
- testRunner is not configured to accept third party cookies
- setCookies.cgi emits wildcard Access-Control-Allow-Origin which is
  invalid for credentialled CORS requests
- it has non-CORS-safelisted header SET-COOKIE

So, the test didn't catch this breakage.

This CL fixes it by using a no-cors fetch() to
/security/resources/set-cookie.php which takes arguments via the query
part of a URL.

BUG=646780
R=mkwst@chromium.org

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

BUG=

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

BUG=None

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

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/800795e7ff6b..27cb47f4d76b

$ git log 800795e7f..27cb47f4d --date=short --no-merges --format='%ad %ae %s'
2016-10-04 petrcermak [tracing] Focus tr-ui-b-table upon clicking on an already selected row/cell

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

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

BUG=641413

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

To determine how much an box needs to shink to avoid a float, the code
was only taking into account the first line of the box. This doesn't
work when the float has a shape, as it can make it seem like there is
more space on the line than there actually is. This patch changes the
calculations to take into account the entire height of the box that
needs to be shrunk, and thus computes the correct amount of space
available.

This is a merge of http://trac.webkit.org/changeset/178045 and
http://trac.webkit.org/changeset/178064 by Bem Jones-Bey <bjonesbe@adobe.com>.

BUG=427989

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

Extract the mouse logic to the extent that
GestureManager can use solely MouseEventManager
instead of being friend with EventHandler and use
private functions. Also this refactoring cleaned
up some parameter passing from EventHandler to
MouseEventManager that was going through
PointerEventManager functions.

Initial refactoring

BUG=625844

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

BUG=651526

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

Can see current guide at:
https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/README.md#Revising-Histograms

Largest change is removal of the guide on exact linear histogram, I think it is less important to give guidance now there is an explicit macro.

BUG=

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

BUG=None

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/4e2b1f13..aaa05f8f

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

Notable changes:
 * CRWWebViewProxyImpl now uses synthesized getter and ivar for
property contentView
 * CRWJSPOSTRequestLoader now does not create a retain cycle of
CRWWKScriptMessageRouter objects. The cycle seems to have been harmless,
but it definitely brings no value, and it's better to not have it.

BUG=651830

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

Before this CL, any task posted to a SequencedWorkerPool redirected to
TaskScheduler after
SequencedWorkerPool::Shutdown(int max_new_blocking_tasks_after_shutdown)
returned was ignored.

With this CL, |max_new_blocking_tasks_after_shutdown| BLOCK_SHUTDOWN
tasks are allowed to be posted after SequencedWorkerPool::Shutdown
returns.

BUG=622400

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

The constructor parameters can be provided directly, and after doing so it
fits on one (80-column) line.

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

https://chromium.googlesource.com/skia.git/+log/2ebd0c80a2a9..ee843b2ae4d7

$ git log 2ebd0c80a..ee843b2ae --date=short --no-merges --format='%ad %ae %s'
2016-10-04 robertphillips Revert of Make GrResourceCache dynamically change between LRU and random replacement strategies. (patchset #8 id:140001 of https://codereview.chromium.org/2321563006/ )

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

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

Before this change, the only way to scan all keys was to call LoadEntries() which loads the whole database. In our use case, this means copying a lot of image data which is wasteful.
With LoadKeys(), we still need to iterate the whole database but we don't have to copy out (and parse) the values -- just the keys. LoadKeys() is useful when storing relatively large values and only access to the keys is required.

We'll use LoadKeys() for NTP content suggestions to garbage collect data. We do that at times when we have a list of all still alive elements and need to intersect that with the elements stored in the db.

BUG=649009

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

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

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

It is no longer compiled.

BUG=None

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

Creates FaviconAttributesProvider, FaviconAttributes and FaviconViewNew
classes to present favicons. These classes intend to replace FaviconView
and FaviconViewProvider downstream.

BUG=None

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

This is a follow-up CL to https://codereview.chromium.org/2363183002/.

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

Revert of Automatically copy the DIA DLL in the Syzygy binaries directory. (patchset #11 id:240001 of https://codereview.chromium.org/2365893002/ )

Reason for revert:
Break gclient for the open contributors.

Original issue's description:
> Automatically copy the DIA DLL in the Syzygy binaries directory.
>
> Committed: https://crrev.com/f34c072397b99c313e79cd10a77f5ca397154399
> Cr-Commit-Position: refs/heads/master@{#422655}

TBR=chrisha@chromium.org,siggi@chromium.org,scottmg@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/6b7a634b..4e2b1f13

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

The registered histograms on the native side are exposed
as JSON text from the FeedbackCollector. The histograms are
exposed only if:
(i)  "Include screenshot and logs" is checked when
the feedback was collected, and
(ii) The feedback is submitted from a non-incognito
profile.

In the next CL, these would be attached to the feedback
report.

BUG=651621

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

Otherwise, the overflow menu stays visible while the controls are hidden
which is fairly odd. Hiding the overflow menu would not be a good
experience either because the timer to hide is fairly short.

BUG=None
R=zqzhang@chromium.org

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

Revert of Refactor WebappRegistry into a singleton instance. (patchset #11 id:200001 of https://codereview.chromium.org/2351113005/ )

Reason for revert:
chrome_public_test_apk failed.

https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/36476

Original issue's description:
> Refactor WebappRegistry into a singleton instance.
>
> This CL refactors WebappRegistry and WebappDataStorage to make most of
> the methods synchronous. WebappRegistry is now a singleton instance that
> is instantiated at browser startup. This allows all SharedPreferences files to
> be pre-warmed before the class is used; new web apps open new
> SharedPreferences on a background thread when registered, after which the
> preferences are cached automatically.
>
> Most static methods on WebappRegistry and WebappDataStorage have been
> converted to instance methods or removed. This makes the code much
> cleaner and more efficient; each static method had to independently open
> their SharedPreferences, which minimally performs a stat() on the
> underlying XML file to see if it has changed. Now the singleton
> WebappRegistry caches all WebappDataStorage objects on startup and
> whenever new ones are added. This reduces disk IO overhead.
>
> This CL allows all calls to SharedPreferences.Editor.apply() in
> WebappRegistry and WebappDataStorage to occur on the main thread,
> mostly removing the need for unwieldy callback interfaces and bare
> pointer passing across the JNI.
>
> BUG=633791
>
> Committed: https://crrev.com/78cf6596040662c0a73c0e4038bc84fb2b3c470a
> Cr-Commit-Position: refs/heads/master@{#422703}

TBR=dfalcantara@chromium.org,wnwen@chromium.org,msramek@chromium.org,dominickn@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=633791

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

BUG=388194,649710

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

In order to avoid re-entrancy issues, this CL modifies sensor event
dispatching code and uses postTask to schedule event dispatch.
New test is added to ambient-light-sensor.html that checks if generic
sensor code works correctly when sensor is not supported

BUG=606766

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

It is useless to launch a rename process directly from a system-level
Chrome. That process can't rename the Chrome executables since it isn't
elevated.

BUG=650981

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

Notable changes:none

BUG=651816
TEST=none

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

If-statement prevents a crash in a unittest that would occur if rolling
after the WebRTC change.

The WebRTC change: https://codereview.webrtc.org/2387343002/

BUG=chromium:627816

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