GitLab

BUG=785341

Change-Id: I23c09aba5b81386c6ebefacd4a51b9e4fc3c4f30
Reviewed-on: https://chromium-review.googlesource.com/774902Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517168}

This test became flaky after migrating it to the new test framework. Looks
like there's some sort of the race with the base tag. Will unflake this soon.

TBR=dgozman@chromium.org

Bug: 667560
Change-Id: Idbc7c298a0e9f45703586d66aff39a45c92b76cd
Reviewed-on: https://chromium-review.googlesource.com/773490
Commit-Queue: Will Chen <chenwilliam@chromium.org>
Reviewed-by: Will Chen <chenwilliam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517167}

Bug: webrtc:8529
Change-Id: I78ae0de9078c128a7b44b12bc93aba7b9fa49a5d
Reviewed-on: https://chromium-review.googlesource.com/772918
Commit-Queue: Fredrik Solenberg <solenberg@chromium.org>
Reviewed-by: Tommi <tommi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517166}

Swipes left and right on the toolbar are very easily triggered in the
ToolbarSwipeHandler. This causes an issue for the bottom sheet when it
is using the velocity swipe model; the page would shudder because the
toolbar swipe layout would be triggered.

This change only detects directional swipes if the initial direction
is within 25 degrees or left, right, or down. This makes accidentally
triggering a different layout more difficult.

BUG=779615

Change-Id: Ied417f3e71e79431168410d4e305fa29a2f57b9b
Reviewed-on: https://chromium-review.googlesource.com/772830
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517165}

SMS messages, notified by chromeos::NetworkSmsHandler, are encoded in
UTF-8. ash::SmsObserver incorrectly treats the received SMS messages as
ASCII, which causes incorrect characters to be shown in the notification
window.

      correctly in the notification.

Bug: 785583
Test: Verify that SMS messages with Unicode characters are shown
Change-Id: I6a4f90d4e3c01b537f8b103e8038f7ad423b7621
Reviewed-on: https://chromium-review.googlesource.com/773620Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Ben Chan <benchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517164}

https://chromium.googlesource.com/catapult.git/+log/a708a70f7608..a6ed3f9aee51

$ git log a708a70f7..a6ed3f9ae --date=short --no-merges --format='%ad %ae %s'
2017-11-16 dproy Add limited cpu time metric

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I5ea6984634a7bbced092eab32fd9714cb33d47ec
Reviewed-on: https://chromium-review.googlesource.com/775027
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517163}

Change-Id: Ibab32e3da920f0fb643efcd1e3807630fd62a849
Reviewed-on: https://chromium-review.googlesource.com/775180Reviewed-by: Kevin Bailey <krb@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517162}

Add a couple small optimizations too.

Change-Id: Ifaafc6486cbeb543c22348819ad71dcc736c5cc4
Reviewed-on: https://chromium-review.googlesource.com/775018Reviewed-by: Bill Budge <bbudge@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517161}

The underlying bug was fixed and it's stable on the FYI bot.

Bug: 781391
Change-Id: I291f5b1ec376c27801c03c6217de65b9b98fd664
Reviewed-on: https://chromium-review.googlesource.com/772873
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517160}

Current rationalization logic of phone numbers runs in fields detection
phase, where the fields' is_focusable state might be obselete. The
rationalization use this state to determine if the logic will run.

Some form have phone fields initally non-focusable, then present them
dynamically, the rationalization will skip those fields. Moving the logic
to filling phase should address this issue.

Bug: 784935
Change-Id: I579a3dab6efad3c2f09a72562b8ae7ab4c376311
Reviewed-on: https://chromium-review.googlesource.com/768295Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Hui Wu <wuandy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517159}

BUG=646113

Change-Id: I0f4591d38064ca0e8f27a514fbcb633ab2c52348
Reviewed-on: https://chromium-review.googlesource.com/764955
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Brett Wilson <brettw@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517158}

Sending renderer debug URLs to the network stack will result in trying
to commit an error page, which is when the debug URL will actually be
handled. This causing issues when trying to block them.

This CL also ensures that debug URLs will never commit.

BUG=776528,760732

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: Iaae35029e5fcd0b66c470468a8f90ca9736fff3e
Reviewed-on: https://chromium-review.googlesource.com/731083
Commit-Queue: Charlie Reis <creis@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517157}

... by posting a weak pointer as is rather than dereferencing it
on a wrong thread.

Change-Id: I12c66a0143b2e980bff989965454def2c29092d8
Reviewed-on: https://chromium-review.googlesource.com/774018Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517156}

Clean up of stuff I missed from:
https://chromium-review.googlesource.com/c/chromium/src/+/762036

BUG=780139

Change-Id: Icc79f75e49dd9c8e2327ffee22e53cafe81bec41
Reviewed-on: https://chromium-review.googlesource.com/773503Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517155}

This CL migrates socket_dispatcher_host.h to use NetworkChangeObserver.
More details are in the following bug

Bug: 780470
Change-Id: If48f749c81272d32bfcee84ea5f5b5639157f5a0
Reviewed-on: https://chromium-review.googlesource.com/754765Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Helen Li <xunjieli@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517154}

This CL updates the following parameters.
  Position of the buttons
  Background color
  Buttons colors
  The gap between the text and the icon
  Position of the audio prompt

Bug: 
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: I9fe0f6037333c1fb3c19111157999c151faffec4
Reviewed-on: https://chromium-review.googlesource.com/772403Reviewed-by: Biao She <bshe@chromium.org>
Commit-Queue: Amirhossein Simjour <asimjour@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517153}

Control Flow Integrity [1] indirect call (cfi-icall) checking can not
verify that dynamically resolved function pointers call their intended
function. Instead we place the LibcFunctions pointers in
ProtectedMemory, a wrapper for keeping variables in read-only memory
except for when they are initialized.  After setting the pointers in
protected memory we can use the UnsanitizedCfiCall wrapper to disable
cfi-icall checking when calling them since we know they can not be
tampered with.

[1] https://www.chromium.org/developers/testing/control-flow-integrity

Bug: 771365
Change-Id: Ib74faff066e1107293b67d11f2a1a054bbff08b5
Reviewed-on: https://chromium-review.googlesource.com/769853Reviewed-by: Chris Palmer <palmer@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517152}

The ExtensionFrameHelper already has logic to find extension frames
matching certain criteria, which is used by custom bindings to return
the global objects for those frames. Move the logic to get the v8
global objects from the custom bindings to the ExtensionFrameHelper in
order to allow re-use with other bindings.

Bug: 653596

Change-Id: Ibb7d57e90bdb83cd574a95eb80db222456dd3e79
Reviewed-on: https://chromium-review.googlesource.com/763572
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517151}

https://webrtc.googlesource.com/src.git/+log/8b64fd8a85c1..8d9c5406c7ba

$ git log 8b64fd8a8..8d9c5406c --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc


The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I69affadf2b7890f11fdc4995249ec2bb97637d64
Reviewed-on: https://chromium-review.googlesource.com/775318Reviewed-by: WebRTC Roll Bot <webrtc-autoroll@chromium.org>
Commit-Queue: WebRTC Roll Bot <webrtc-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517150}

Bug: 771028
Change-Id: I323d63f4f7b845a4d2588b385c18e673c47257e3
Reviewed-on: https://chromium-review.googlesource.com/767656Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Nathan Parker <nparker@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517149}

Expanded the existing model of calling NoNotify methods, and changed
some sync only methods to return a bool representing whether a change
was made to the local data or not. RemoveNoNotify does not currently
expose if a change was actually made, so we assume that one was, fixing
this was out of scope. This allowed the sync methods (apply and merge)
to track if any changes were made, and invoke a single NotifyObservers
after all local changes had been applied.

As made evident by the unit tests, there's some complexity around
changing the default search engine that may still result in more than
one notification call.

Bug: 775049
Change-Id: Ie0b3080a60852f6cc09704feb4de8f850386353b
Reviewed-on: https://chromium-review.googlesource.com/745521Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517148}

This CL does some micro cleanups in VaapiVideoDecodeAccelerator:

- removes the member |num_input_buffers_|, which is use for TRACEing
only, and uses instead |input_buffers.size()|.  This is a change in
behaviour, since now we would also count the Flush-type InputBuffers,
but I think the change is justified since it's just for TRACEing
and they are, after all, InputBuffers as well.

  With the same logic s/Stream buffers at decoder/Input buffers/
at the TRACE_COUNTER1 statements.

- Rewrites the logic in GetInputBuffer_Locked() to avoid deep
condition layers, using instead early return.

- Rewrites Reset() to have less lines.

- Removes one of two consecutive empty lines.

- Simplifies CreateSurface() return statement.

Except for the |num_input_buffers_|, **there should be no new code**.

Nonetheless:
TEST=compiled-ran video_decode_accelerator_unittests on soraka,
all passing w/ same perf numbers. Ran standard VP9 playback,
all good as on ToT.

Bug: 717265
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: Id96d63f3245c04008927f94daf3ae05d48be9bbd
Reviewed-on: https://chromium-review.googlesource.com/774998
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517147}

Chrome security is trending away from showing the URL scheme, to an
icon-based representation. To support that, we should return to showing
the info icon if there is no other state (either secure or dangerous).

BUG=778411
R=bshe

Change-Id: Ic6ec0af9ff628bcacab55484a7e584339e59528f
Reviewed-on: https://chromium-review.googlesource.com/773119Reviewed-by: Biao She <bshe@chromium.org>
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517146}

Test incorrectly called beRejected with an argument.  It should have
used beRejectedWith.  But the error was also incorrectly set to
TypeError when it should have been DataCloneError according to the
spec.

Bug: 785359
Test: decodeAudioData/decode-audio-data-neuter.html
Change-Id: I31be85867c2e792d1b79ec63105aadcf8f98dea7
Reviewed-on: https://chromium-review.googlesource.com/772353Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517145}

https://skia.googlesource.com/skia.git/+log/24f9c19172e1..5627d65146cb

$ git log 24f9c1917..5627d6514 --date=short --no-merges --format='%ad %ae %s'
2017-11-16 bsalomon Add method to sk_gpu_test::TestContext to automatically restore the previous context.
2017-11-15 reed remove legacy Create from SkTextBlob

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


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=brianosman@chromium.org

Change-Id: Ib7ef715dab844f58982e7b08bde43d30e70330cd
Reviewed-on: https://chromium-review.googlesource.com/775046Reviewed-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@{#517144}

Bug: 637172
Change-Id: I1f700efd223ed7e8fe61067b1ac581723f7dbd59
Reviewed-on: https://chromium-review.googlesource.com/774458Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517143}

There are two problems with ImeTest that seem to be caused by scrolling (caused
by calling methods in DOMUtils, such as clickNode(), on various elements):

- Various test cases in ImeTest are intermittently failing in startup
  (crbug.com/781174). I am unable to reproduce the problem or determine what's
  happening. Test output and screenshots taken upon failure seem to indicate
  that focus is somehow getting moved to the <textarea> element in the HTML file
  immediately after the first <input> element, instead of remaining on the
  <input>. I am hopeful that avoiding scrolling resolves this problem. At the
  very least, it will rule out a potential cause of the issue.

- In https://chromium-review.googlesource.com/c/chromium/src/+/740373, I
  attempted to land a change to the HTML file used by ImeTest to support a few
  new tests. The change made the webpage longer so more scrolling happens. In
  particular, a test failure results because single taps on two different
  elements are getting counted as a double tap, because scrolling is bringing
  the second element to the location of the first element (so the taps are now
  in the same location on screen, whereas before they were in different
  locations, and hence the taps weren't eligible to be interpreted as a
  double-tap.

  This issue *does* reproduce locally, and I have confirmed that avoiding
  scrolling fixes the issue.

This CL avoids scrolling in ImeTest by making the whole webpage fit on-screen.

Moving the elements closer together seems to make a click in
testKeyboardAppFinishesCompositionOnUnexpectedSelectionChange() get counted as a
double-click in some test runs (I had to compile a release build to test this),
so I'm also adding a call to Thread.sleep() in that test to avoid this problem.

Bug: 781174
Change-Id: I4982be105846b954e7495fee682fcfe988dd2155
Reviewed-on: https://chromium-review.googlesource.com/773105Reviewed-by: Changwan Ryu <changwan@chromium.org>
Commit-Queue: Ryan Landay <rlanday@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517142}

This runs a given gtest binary 2 tests at a time (with
--gtest_shuffle and --gtest_repeat to try to encourage both
orderings of the test), and reports on any pairs that fail.

Change-Id: I9f4f8698aa97988a18290a4a5e5561975aac9aad
Reviewed-on: https://chromium-review.googlesource.com/646851Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Scott Graham <scottmg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517141}

The CSS Containment spec explicitly states that containment has no
effect on elements with display:contents element for paint, layout and
others. Not stated for contain:style.

Check for style containment for counters even when LayoutObject is null.

Note that due to the bug reported in 766650, the added test passes even
without this code change.

Bug: 766650
Change-Id: I64082f52255d5d810ba803148a418edff5da66c8
Reviewed-on: https://chromium-review.googlesource.com/771830Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517140}

This race should have been more common but it only reproed on iPhone 7
hardware running iOS 11 with a release version of base_unittests.
Setting DCHECK_ALWAYS_ON to true would cause the bug to stop reproing.

Because the test task signalled its WaitableEvent at the beginning of
the task instead of at the end, it was possible for the function
holding |manager_started| to return before the task had a chance to
check it.

The fix here moves the signalling to the end of the task, ensuring that
|manager_started| is alive when it is checked by the test task.

BUG=784051

Change-Id: I1e88395bcc45b5390af0c75be806a0a7301e483e
Reviewed-on: https://chromium-review.googlesource.com/773299
Commit-Queue: Robert Liao <robliao@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517139}

Bug: 785931
Change-Id: Id9a97a37985a9888efe2633d688a0818536b2d66
Reviewed-on: https://chromium-review.googlesource.com/774690
Commit-Queue: Chris Dalton <csmartdalton@chromium.org>
Reviewed-by: Robert Phillips <robertphillips@google.com>
Cr-Commit-Position: refs/heads/master@{#517138}

Even though they're failing on 5X webview and they're disabled on 5X,
there's a bug where 5X webview isn't matching the 5X test condition
(https://github.com/catapult-project/catapult/issues/4045).

TBR=ashleymarie@chromium.org
NOTRY=true

Bug: 784540
Change-Id: I100929183b15c1d84ff4e0cecddb15236644bb84
Reviewed-on: https://chromium-review.googlesource.com/775433Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517137}

Bug: 762018
Change-Id: I51b9890df2ec4cde768bd08f2e6d5ed54eca999a
Reviewed-on: https://chromium-review.googlesource.com/769737Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Biao She <bshe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517136}

This CL removes clean/ view controllers from Showcase.

Bug: 785925, 710662, 772186
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Iebce9f69b7776aa2755e46ec379d7245075a55a7
Reviewed-on: https://chromium-review.googlesource.com/774465
Commit-Queue: Mark Cogan <marq@chromium.org>
Reviewed-by: Louis Romero <lpromero@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517135}

This change fixes two bugs with caching of media sinks and a potential
initialization race that could also affect the cache's performance.

The first fix is to allow network ID changes of network1->network2 to
cache sinks for network1 rather than only caching for
network1->disconnected/unknown.  The cache originally used the latter
logic because net::NetworkChangeNotifier broadcasts a disconnect between
any two network changes.  However, DiscoveryNetworkMonitor doesn't
necessarily forward this behavior to its observers because it actually
calculates the current network ID on every net::NetworkChangeNotifier
notification.  Not caching in the former case could account for some of
the cache's low utilization currently seen in metrics.

The second fix is to add CastMediaSinkServiceImpl as a
DiscoveryNetworkMonitor::Observer from the correct sequence so it
receives notifications on the correct sequence.  This in turn
exacerbates a race between the first network ID update and
CastMediaSinkServiceImpl's AddObserver call.  The race was therefore
also addressed in this change.

Bug: 782788, 782859
Change-Id: I064bd184508e66f1806e55dc5afe1eea907836ea
Reviewed-on: https://chromium-review.googlesource.com/760667
Commit-Queue: Brandon Tolsch <btolsch@chromium.org>
Reviewed-by: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517134}

NOTRY=true
TBR=junov@chromium.org

Bug: 785286
Change-Id: Ie6ea11ecb9a5ea4153da9aee124012ed9a5626bc
Reviewed-on: https://chromium-review.googlesource.com/771853
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517133}

Bug: 785435
Change-Id: I783aeedf9d67f4a8280d7770b9b276dbfab68b79
Reviewed-on: https://chromium-review.googlesource.com/772882
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517132}

This CL adds a metric to measure the time spent from URLRequest creation
and when Start() is called on it. The purpose is to measure time spent
in various resource handlers before sending the request out to the net
stack.

Bug: 779914
Change-Id: I8e462a7d9fb541de38589aeb926f81047a735d50
Reviewed-on: https://chromium-review.googlesource.com/771549
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517131}

Convert PrintTabHelper to directly track registration
with the observed WebState instead of relying on the
deprecated code in WebStateObserver.

Bug: 775684
Change-Id: I2788f302863f7f23bf35fab7a98a75ced00b17f1
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Reviewed-on: https://chromium-review.googlesource.com/768719
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517130}

This change is a precursor to a more extensive change where
ExternalAppLauncher API is changed to be asynchronous.

This simpler change is to call the decision handler in the implemention
of WKNavigateDelegate method
webView:decidePolicyForNavigationResponse:decisionHandler:
asynchronously on iOS 11 and up.

iOS 10 (and possible below) has a bug where JavaScript on the page would
not execute if the decision handler is called asynchronously.

This change is to make sure that there are no other unforeseen
issues with calling decision handler asynchronously on iOS 11.

Bug: 774736
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I7a6dfe637cb6be4ce5c7efe5824728b8f06b902a
Reviewed-on: https://chromium-review.googlesource.com/773570
Commit-Queue: Peter Lee <pkl@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517129}