GitLab

If the token service has already a refresh token for the authenticated
account before this account is signed in to Chrome, then |OnRefreshToken|
notification will not be called after |GoogleSigninSucceeded|.

This CL changes the UserPolicySigninService to handle the case when the
refresh token is already present when |GoogleSigninSucceeded| is fired.

See bug for the link to the design document.

Bug: 733226
Change-Id: I17e3ef8285b4012e125951c5a38e1851a09c9c9a
Reviewed-on: https://chromium-review.googlesource.com/559538
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486008}

AudioParamMap is a map-like container owned by AudioWorkletNode object.
It associates the name of a parameter to the actual AudioParam object.

Spec: https://webaudio.github.io/web-audio-api/#idl-def-AudioParamMap

Bug: 736781
Change-Id: I063add4281954036b90442dc5c4a6e9c50145e41
Reviewed-on: https://chromium-review.googlesource.com/548239
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486007}

Previously segments were always pulled from the back of the vector
and only the last value was checked before deciding to create a
new segment.  This allows small buffers on the end to repeatedly
result in shmem creation. 

Instead switch to a first fit algorithm where segments are kept in
sorted order by size. Also switch to choosing the minimum segment
size based on the resolution and clear between flushes.

Since we may be allocating a few more buffers now, the code will
expire unused ones if they haven't been used after 1024 frames.

tl;dr: reductions in memory of ~42% at 360p or below, ~8% at 480p,
~10% at 720p, equivalent at 1080p, ~38% at 2160p. So this should
save us 10s to 100s of KBs on the most common media.

Old results:
360p, dec: 1228217, alloc: 409600 (4), d/a: 2.99858, size: 102400
480p, dec: 3170779, alloc: 536946 (5), d/a: 5.90521, size: 102400
720p, dec: 9402525, alloc: 1191936 (8), d/a: 7.88845, size: 102400
1080p, dec: 16676052, alloc: 2052082 (9), d/a: 8.12641, size: 102400
2160p, dec: 63319373, alloc: 3051283 (18), d/a: 20.7517, size: 102400

New results:
360p, dec: 1228217, alloc: 237568 (6), d/a: 5.16996, size: 32768
480p, dec: 3170779, alloc: 495616 (7), d/a: 6.39765, size: 49152
720p, dec: 9402525, alloc: 1077248 (8), d/a: 8.72828, size: 73728
1080p, dec: 16676052, alloc: 2043904 (9), d/a: 8.15892, size: 98304
2160p, dec: 63319373, alloc: 1888256 (7), d/a: 33.5333, size: 196608

BUG=none
TEST=manual playback of clips with varying resolutions.

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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

Change-Id: I6df3dd41320dcc70dfd23224767b107806b0942e
Reviewed-on: https://chromium-review.googlesource.com/565007
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486006}

The client side of the command buffer handles emulation of the
GL_PACK_ROW_LENGTH parameter.

TEST=conformance2/reading/read-pixels-pack-parameters.html

BUG=602688

Change-Id: Id3415d56c565504b423f2a32d91d865274667037
Reviewed-on: https://chromium-review.googlesource.com/567430
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486005}

This includes a change to the compiler that removes the ability to
suppress availability warnings by redeclaring functions. The new way
to suppress warnings is to enclose the function reference in an
"if (@available)" block.

Previous CLs have cleaned up the code base to use the new way of
suppressing warnings (see bug).

Bug: 735328
Change-Id: I340ac5c16df837d13fa5b8885e9f5a8e7bcf8e0c
Reviewed-on: https://chromium-review.googlesource.com/566280
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486004}

Adds horizontal scrolling to the VR browser scrolling test, so now both
vertical and horizontal scrolling using the Daydream controller are
tested.

This should hopefully be good enough to remove the need to manually test
basic scroll functionality.

Bug: 728779
Change-Id: I882755999485b6610fcd865953cb1b06ca47edd5
Reviewed-on: https://chromium-review.googlesource.com/567033Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486003}

There are two reasons for this CL:
1. This layout test times out on virtual/gpu/ test suite.
2. The layout test is uses testharness, but it has an expected file.

The reason for #1 is that when the test creates a canvas, it uses the
canvas's default width and height which is 300*150, and call getImageData
and putImageData on the entire canvas with the same color. We really don't
need that, this CL sets the width and height to be 5 and should test the
same thing.

The reason for #2 is that this layout test has several small tests, the
name for each small tests are the same, and testharness apparently
doesn't like that.

This CL removes a line in the expectation file, and some -expected.txt

Bug: 709009
Change-Id: I14935f4bf84a8cabb5a9aa56dc502b5d02768b77
Reviewed-on: https://chromium-review.googlesource.com/568079Reviewed-by: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486002}

This CL removes the DB thread reference from IOSChromePasswordStoreFactory and
replaces it with an appropriate CreateSequencedTaskRunnerWithTraits call.

Bug: 689520
Change-Id: I19c7a6473f7d26ce192005e25b297c878716bee5
Reviewed-on: https://chromium-review.googlesource.com/567984Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Commit-Queue: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486001}

Some files excluded from jumbo compilation seems to compile just
fine in jumbo so this patch removes their special treatment.

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

Automatically generated ARCMigrate commit
Notable issues:None
BUG=624363
TEST=None

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

Store all client hints as enum values. This makes client hints
more structured. As a bonus, it reduces the chances of bugs by
adding compile-time checks, and makes it easier to introduce
new client hint values.

In forthcoming CLs, this structured list of client hints would be
persisted on the disk on the browser side.

Bug: 735518
Change-Id: I5e743398ed1c3484def527543fabcfad99a0f14a
Reviewed-on: https://chromium-review.googlesource.com/563555
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485998}

This reverts commit fd8b83c8.

Reason for revert: This CL breaks password_settings_eg_test, we might need to update the tests so they use the new A11y labels. Though I'm not sure if there's more than that. 

Original change's description:
> Password settings on iOS: use Title Case
> 
> Most of setting headers in the passwords seciton on iOS already use Title Case,
> except for the headers of the saved and blacklisted lists of passwords.
> 
> This CL fixes that by creating new strings for iOS settings inside
> ios/chrome/app/strings/ios_strings.grd. Previously the code used shared strings
> from the password_manager component (components/password_manager_strings.grdp).
> That string was also used by the old (non-MD) desktop settings, which have
> already been deprecated. The MD settings on desktop use the Title Case as iOS
> should as well, but the MD settings strings are consistently saved in
> chrome/app/settings_strings.grdp, where they cannot be shared with iOS.
> 
> The CL creates the new string instead of sharing the one from MD settings,
> because sharing has no benefit (on no build both strings are included, so no
> storage spared) and has the drawback of binding the style of both strings
> forever together.
> 
> The CL does not remove the component string yet. The old desktop settings code
> is still in the codebase, and the shared string (used only by the old settings)
> should be deleted once those old settings are deleted.
> 
> The CL was approved in https://chromium-review.googlesource.com/c/567181. This
> is a verbatim copy of that CL, but re-uploaded after Gerrit issues prevented me
> to actually land the original one. Hence I'm TBR-in lpromero@ who approved the
> original.
> TBR=lpromero@chromium.org
> 
> Bug: 740952
> Change-Id: I455b8f2a5edd1089916a7b87f20eddc3b274a2b7
> Reviewed-on: https://chromium-review.googlesource.com/567930
> Reviewed-by: Vaclav Brozek <vabr@chromium.org>
> Commit-Queue: Vaclav Brozek <vabr@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#485912}

TBR=vabr@chromium.org,lpromero@chromium.org

Change-Id: I41a5e01b086a1643a6f72f3934d5cfea6ceb57b6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 740952
Reviewed-on: https://chromium-review.googlesource.com/568387Reviewed-by: Sergio Collazos <sczs@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485997}

This CL implements IAccessibleTable, IAccessibleTable2 and
IAccessibleTableCell on AXPlatformNodeWin. It forwards calls on
BrowserAccessibilityWin to this implementation.

BUG=703369

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

TBR=yzshen@chromium.org

Bug: 
Change-Id: I3bb44ece86db7599af6d92ef2ec89012dd4846dc
Reviewed-on: https://chromium-review.googlesource.com/568535Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485995}

These were found as part of the effort to re-enable android unused
resources lint checks. The actual lint checks will be re-enabled once
platform-tools is rolled to version 26+.

Bug: 731159
Change-Id: I6c977371acac62b4301fe71def8e0f0313238a73
Reviewed-on: https://chromium-review.googlesource.com/566893Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485994}

This reverts commit 05d4aefd.

Reason for revert: https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Builder%20%28dbg%29/builds/89457

Original change's description:
> Roll src/third_party/skia/ c4176a2fa..46b654df9 (6 commits)
> 
> https://skia.googlesource.com/skia.git/+log/c4176a2fa5aa..46b654df9e70
> 
> $ git log c4176a2fa..46b654df9 --date=short --no-merges --format='%ad %ae %s'
> 2017-07-11 ethannicholas converted GrSimpleTextureEffect to sksl
> 2017-07-12 reed remove unreachable perspective code for imageshader
> 2017-07-11 liyuqian Always enable Analytic AA for rects
> 2017-07-11 bsalomon Make SmallPathOp a non-legacy GrMeshDrawOp
> 2017-07-12 robertphillips Address ASAN complaint
> 2017-07-11 robertphillips Plumb raw GrMipLevel* down instead of SkTArray<GrMipLevel> in GrGpu
> 
> Created with:
>   roll-dep src/third_party/skia
> 
> 
> 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;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
> TBR=ethannicholas@chromium.org
> 
> Change-Id: Iaa9f8d51a32084c0449c65b80ca70b9c7e9635f5
> Reviewed-on: https://chromium-review.googlesource.com/568220
> Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
> Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#485962}

TBR=skia-deps-roller@chromium.org,ethannicholas@chromium.org

Change-Id: I5f8e6f95396c3e8f5258c23deb3edf076ae4e352
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
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;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Reviewed-on: https://chromium-review.googlesource.com/568439Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485993}

There are two implementation of AddStringToDigestor. Beyond being
one more than needed, they also conflict in jumbo builds.

This patch merges the two AddStringToDigestor and removes the
conflicting files from the jumbo exclusion list.

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

Server previews recently stopped working with introduction of
CL 544586 when previews_to_allow is 0 or UNSPECIFIED. This CL
adds a check to guards its use if UNSPECIFIED.

The chromedriver lite.py integration tests failed prior to these fix
but succeed with it patched in.

Bug: 741067
Change-Id: If206200688fac4fabca6df7186f4981623276487
Reviewed-on: https://chromium-review.googlesource.com/567559Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Commit-Queue: Doug Arnett <dougarnett@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485991}

Add a browsertest for the navigation handle getting lost when doing rapid navigations after a session restore.

BUG=738177

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

This CL cleans the Keyboard Accessory View (KAV) situation for the
web toolbar to support InputAssistantItems on iPad (1).
In particular, this CL:
- Removes keyboard_accessory_view.*.
  Now only new_keyboard_accessory_view.* is used.
- Removes HardwareKeyboardWatcher because it only works when there is
  a KAV (crbug.com/740898).
- Removes |-locationBarChanged| because it would only be used to
  record MobileFirstTextInOmnibox (crbug.com/740611).
- Removes the |_keyboardAccessoryView| ivar. It was used when the KAV
  was not laid out with auto layout and had multiple modes.

(1) https://docs.google.com/document/d/1pWfwHEeCNeWgkDjawJiDoEf93gkDV9usINcYDyXvwcY/edit#heading=h.sku52p315l4d

Bug: 738106, 708341, 740611
Change-Id: If6e509de3e6d57f0347b3e355b91af16bd055adb
Reviewed-on: https://chromium-review.googlesource.com/567087Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Jean-François Geyelin <jif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485989}

Bug: 738593
Change-Id: Iafbe191294f825b9d1446c3a51c3f7ce527b9831
Reviewed-on: https://chromium-review.googlesource.com/564279Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485988}

Change-Id: If4e7534748cd2149916dad57b21d875666aa5b71
Reviewed-on: https://chromium-review.googlesource.com/567026Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Commit-Queue: Scott Nichols <nicholss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485987}

When a refresh token was replaced by a new one, it was not revoked, and
essentially leaking.

OnRefreshTokenRevoked() is not called because it is used to signal that
the associated account no longer has a valid token. This is not the case
here, since the token is immediately replaced by a new one.

Bug: 735898
Change-Id: If0f9777543d574a00084d7dd6b67209aeacf150c
Reviewed-on: https://chromium-review.googlesource.com/568303Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485986}

post initial load."

This time, land behind a command line flag (the same one that controls
the stop/reload icon toggles). Also, it was noted that this change could
make certain actions feel sluggish, such as pressing "Save Changes" in
monorail, because the throbber feedback was no longer immediate. To
address this, only suppress switches to the throbber that occur right
after the throbber has stopped showing. That way, as long as you press
"Save Changes" a few seconds after the page has finished loading, the
throbber feedback will be immediate, but we'll still get the suppression
of flicker at the end of a page load (visible, for example, on yahoo.com,
cyclingnews.com, or when navigating to an extension/app/etc. in the
Chrome Web Store).

Bug: 734104
Change-Id: I5a59fc16785e3a5f30b40a72f03c5c6a67e66337
Reviewed-on: https://chromium-review.googlesource.com/567800Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485985}

BUG=chromium:717394

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

The |cursor_view| in Textfield uses the default construction of view, 
where the cursor is always initialized as visible. It was showing in some 
default location before landing fix of bug crbug.com/734988. It now shows 
in the beginning of the Textfield instead. As a result, an unwanted text 
cursor is displayed to users. In this change, after calling  
UpdateCursorViewLocation, UpdateCursorVisibility is added to adjust the 
visibility.  

Bug: 739607
Change-Id: I3243857173c9c30cb0da11eae31f030e26771bd7
Reviewed-on: https://chromium-review.googlesource.com/564019Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Yi Xu <yiyix@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485983}

"cancelPendingPrintRequest" does not actually exist. Remove the call to
this function from the PrintPreviewUI.

BUG=740264

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

When the bottom sheet is opened, make it focusable and give it content.
description. If none of its child views are focused, requestFocus()
on the bottom sheet. When the sheet is closed, make it unfocusable
and clear the content description.

BUG=740689

Change-Id: I1149367acb13c477aca8c409e49ef6c2a6f8c2da
Reviewed-on: https://chromium-review.googlesource.com/567485Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485981}

This replaces hugely hacky behaviour where we assumed Chrome would start
up within 500ms because we couldn't figure out how to cancel the
activity animation, with only moderately hacky behaviour where we start
a noDisplay activity in order to cancel the animation.

The duration of the stay_hidden animation has been increased to the max
duration of 10s, giving chrome ample time to start up while hidden and
then cancel the animation.

Bug: 740004
Change-Id: I0f2c8daac7b0f692f0ed5a9bbfefe29a925811e6
Reviewed-on: https://chromium-review.googlesource.com/567336
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Yash Malik <ymalik@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485980}

Move include to correct include block in hpack_varint_decoder_test.cc,
following up on https://crrev.com/c/561756.

Remove unused FLAGS_chromium_http2_flag_log_compressed_size definition,
following up on https://crrev.com/2869963002.

BUG=488484

Change-Id: I2b3c4d43b0e0a2ee58643be42df62040e81b3b6c
Reviewed-on: https://chromium-review.googlesource.com/568102Reviewed-by: Helen Li <xunjieli@chromium.org>
Commit-Queue: Bence Béky <bnc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485979}

These calls are no longer needed after r485461
(https://crrev.com/2478803003) which has made the
domAutomationController.setAutomationId call a no-op.

BUG=662543
This CL was uploaded by git cl split.

R=thakis@chromium.org

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

MobileSignInPromo.SettingsManager.ImpressionsTilDismiss histogram should
be send in |settingsWillBeDismissed| instead of |dealloc|.

Bug: 709286
Change-Id: I11a4299ab1cdf911c63a2ca7e0a097954a7f513e
Reviewed-on: https://chromium-review.googlesource.com/568304Reviewed-by: Louis Romero <lpromero@chromium.org>
Commit-Queue: Louis Romero <lpromero@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485977}

Using wpt-import in Chromium f8059bbc.

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
dom-dev@chromium.org:
  external/wpt/dom
  external/wpt/html
  external/wpt/shadow-dom
jsbell@chromium.org:
  external/wpt/WebIDL
rouslan@chromium.org, mathp@chromium.org:
  external/wpt/payment-request
style-dev@chromium.org:
  external/wpt/cssom-view
  external/wpt/cssom

TBR: qyearsley@chromium.org
No-Export: true
Change-Id: I48e40a1c5afe28538f475d6932280b3689c18043
Reviewed-on: https://chromium-review.googlesource.com/568031
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485976}

This reverts commit f0110e71.

Reason for revert: https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Builder%20%28dbg%29/builds/89456

Original change's description:
> [AdsPageLoadMetrics] Clean up the histogram tests
> 
> The tests were a bit lengthy, and with more tests upcoming it makes sense to
> clean them up by making a histogram-checking function.
> 
> BUG=741026
> 
> Change-Id: Ifb7812d95409ba83d8b07682a4906479ded75c1b
> Reviewed-on: https://chromium-review.googlesource.com/567270
> Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
> Commit-Queue: Josh Karlin <jkarlin@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#485957}

TBR=jkarlin@chromium.org,bmcquade@chromium.org

Change-Id: Ia090584ac4025584165f7eb32f5b08f95b9d417f
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 741026
Reviewed-on: https://chromium-review.googlesource.com/568438Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485975}

Reverting as has caused a couple of regressions. Latest is opening
links from external applications doesn't work.

BUG=708873,739200
TEST=verify 739200 is fixed, 708873 will be broke again

Change-Id: I5275694888bcead75deb44450e7e6e1192c17adf
Reviewed-on: https://chromium-review.googlesource.com/567562Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485974}

Also removes two method calls from AddAutofillPaymentInstrument() and
AddAutofillProfile() methods for more efficiency.

Bug: 602666
Change-Id: Ia8fb22bc74ea8226f921981ff88febe7253beccf
Reviewed-on: https://chromium-review.googlesource.com/568260Reviewed-by: Marc-Antoine Courteau <macourteau@chromium.org>
Commit-Queue: Marc-Antoine Courteau <macourteau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485973}

This code previously lived in an android-specific directory, so it was
inappropriate to include it on other platforms. Now that we've moved
platform-agnostic code to chrome/browser/vr, the tab helper can also
be relocated, removing a number of unfortunate ifdefs.

Bug: 728421
Change-Id: I2b3f5e6b7369a751ed1e947f7882b2a8dd75e38e
Reviewed-on: https://chromium-review.googlesource.com/567327Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485972}

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

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

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org

Change-Id: I5dd4fc9b5edbd249fe3acb815efe2a940c774613
Reviewed-on: https://chromium-review.googlesource.com/568081Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485971}

kDescription is the name of two constants in editing unit_tests and
in jumbo builds those collides. This renames one of them
kTestDescription to make both constants have unique names.

R=fs@opera.com

Bug: 
Change-Id: I7fcb2fde1a6841ef92fe7d55a7b363da7c2c7fa0
Reviewed-on: https://chromium-review.googlesource.com/568146Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: bratell at Opera <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#485970}

- Stop BackgroundFetchDataManager::CreateRegistration from invoking its
  callback with an initial_requests vector that then has to be passed
  around everywhere; instead have BackgroundFetchJobController directly
  get the initial requests from BackgroundFetchDataManager using a
  PopNextRequest method as it already does for subsequent requests.

- Rename BackgroundFetchDataManager::RegistrationData::GetPendingRequest
  to PopNextPendingRequest since it also removes the request from the
  pending queue.

- Split up the MarkRequestAsCompleteAndGetNextRequest method of
  BackgroundFetchJobController so it re-uses PopNextRequest rather than
  duplicating it.

- Remove BackgroundFetchJobController's brittle tracking of
  pending_completed_file_acknowledgements_ since if/when multiple
  requests are run in parallel, it would incorrectly report the job to
  be complete as soon as the pending requests queue is exhausted, even
  if other requests are still being downloaded. Instead just get an
  accurate value for has_pending_or_active_requests from the
  BackgroundFetchDataManager when marking requests complete.

BUG=none

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