GitLab

This CL moves the generic Chrome OS intent picker navigation throttling
behaviour from ArcNavigationThrottle to AppsNavigationThrottle.
AppsNavigationThrottle::MaybeCreate now returns an instance of
AppsNavigationThrottle, and ArcNavigationThrottle now handles showing
the intent picker UI and querying ARC++ for apps. This CL should have no
functional changes.

Follow-up CLs will migrate the showing the intent picker UI to
AppsNavigationThrottle, and rename ArcNavigationThrottle. The renaming
was not done in this CL for ease of review. Strictly speaking,
ArcNavigationThrottle is still a semantically correct name; the main
reason for renaming is to avoid confusion with subclasses of
content::NavigationThrottle.

BUG=824598

Change-Id: I82c6e48cf7929701ea9f59cf811c4b7de70fd49a
Reviewed-on: https://chromium-review.googlesource.com/974622
Commit-Queue: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: David Jacobo <djacobo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547875}

This cuts down on the number of copies and fixes some other bits:

- Add a fuzzer.

- Document a place where the original implementation did not match the
  specification. (The final record's size is a little iffy. We probably
  want a small spec tweak.)

- Use a streaming SHA-256 implementation, rather than making a copy to
  stick the 0 or 1 in the hash.

- If there is no more room in the output (the consumer may be issuing
  smaller reads), stop processing input. There is no need to make a copy
  of the entire input. MerkleIntegeritySourceStream only needs to buffer
  at most one record. (Ideally we wouldn't even do and instead
  coordinate with the base class's read buffer, but that would require
  tweaking the FilteredSourceStream interface. This CL addresses the
  easy stuff.)

- Fix O(N^2) behavior if the caller issues tiny reads in the buffered
  output.

- If the record is entirely in the input buffer (common case), don't
  make a copy to extract it.

- If the output fits entirely in the output buffer (common case), don't
  make a copy to return it.

- Flesh out missing tests, based on code coverage tools and important
  security checks (notably truncation).

  (For others trying to repeat the coverage bits: this file was
  unfortunately placed in //content rather than //net, so I wasn't able
  to get the coverage tools to work without hacking it into
  net_unittests locally. It seems the X server dependency is
  problematic for tools/code_coverage?? Also content_unittests is huge.)

- s/MI-256/MI-SHA256/. There are other 256-bit hashes.

Bug: 814591
Change-Id: If927d3f49085a5bec31939846c9a55f8903da34a
Reviewed-on: https://chromium-review.googlesource.com/981798Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547874}

On versions where the API is deprecated. The desired behavior of
essentially inverting the mask can be done with clipOutPath on O or
above, and by Op.DIFFERENCE for below.

Bug: 828195
Change-Id: I08f262018f1596fd79556667961ed80a97221768
Reviewed-on: https://chromium-review.googlesource.com/994257Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547873}

This call is necessary to set the color space property on the backing
IOSurface.

It may be that we should change this API to require specifying a color
space a GpuMemoryBuffer creation time. That would be an artifical
constraint, but would make bugs of this sort less likely.

This needs a merge to M66, so I'm not considering it in this patch.

Bug: 827670
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: If5ecdc5a8efcefcf1fcbc9c8a230cd716005ac2e
Reviewed-on: https://chromium-review.googlesource.com/988826Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547872}

views::Widget::InitParams::context is not required on Chrome OS. Remove
places that set it unnecessarily in //ash.

Make ash_unittests provide a default context in ViewsDelegate, just
like Chrome does in ChromeViewsDelegate.

Clean up some CreateTestWindow / CreateTestWidget functions.

Clean up a couple cases where windows were being reparented
unnecessarily in tests.

Bug: 826569
Test: ash_unittests
Change-Id: I5d3cfa4501a826357615e5a42564ac2b5e9a2a19
Reviewed-on: https://chromium-review.googlesource.com/988939
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547871}

Bug: None
Change-Id: I3b3d0070dcfcf9b76aa4fd273570bbbdea7f7953
Reviewed-on: https://chromium-review.googlesource.com/992878Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547870}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/87c1c3dbea9a..ec8d7a766a7e

$ git log 87c1c3dbe..ec8d7a766 --date=short --no-merges --format='%ad %ae %s'
2018-03-01 achuith [chrome_committer]: Split out chrome_committer.
2018-03-08 ahassani paygen: Log all chroot operations in the log file
2018-03-08 ahassani paygen: Check for the correct metadata size in the verify section

Created with:
  roll-dep src/third_party/chromite
BUG=chromium:814910,chromium:808495,chromium:820243


The AutoRoll server is located here: https://chromite-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.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I2dc84a4feb54038e73df54f3f123e7cf8e6d3ae0
Reviewed-on: https://chromium-review.googlesource.com/993704Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#547869}

R=cmasso@chromium.org

Change-Id: If07343315017d2ce2cede6a0b7e3a643136f7e16
Reviewed-on: https://chromium-review.googlesource.com/994386Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547868}

Improve bootstrap for Windows and allow bootstrap to work in specified
target directory. Additionally, some fixes made to project generation,
and for Linux.

R=dpranke@chromium.org

Change-Id: Ied7f99d3cb83559fbde597cb707b46fcb3e98dc4
Reviewed-on: https://chromium-review.googlesource.com/941214
Commit-Queue: Yngve Pettersen <yngve@vivaldi.com>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547867}

Show an Android Alert Dialog when Window.confirm is called in javascript
in webview test shells.

Bug: 826056
Change-Id: Ic5e279e26719a3b73fa8cc88393344111e33baeb
Reviewed-on: https://chromium-review.googlesource.com/981201Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Changwan Ryu <changwan@chromium.org>
Commit-Queue: James Wallace-Lee <jamwalla@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547866}

It was removed before, but I didn't cleanup one line.

TBR=vadimsh@chromium.org

No-Try: True
Change-Id: I84fe015052ea7a679d38e37d41b61ac64e8f4089
Reviewed-on: https://chromium-review.googlesource.com/994379
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547865}

Bug: 790378,790311,790308
Change-Id: I74ed3df2fa4d1100747aff1e1ddb84401ebfbdd1
Reviewed-on: https://chromium-review.googlesource.com/989112Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547864}

This fixes a crashing test (with DCHECK enabled) caused by the IO thread
having a different ID for each test. This conflicted with the constraint of
the NSSInitSingleton that its methods be called with thread-affinity (on
the same thread ID).

R=khorimoto@chromium.org

Bug: 828538
Test: EasyUnlockTpmKeyManagerTest.*
Change-Id: I7936ed9ad09884a47a898344a99977d3d5d013ac
Reviewed-on: https://chromium-review.googlesource.com/994071Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547863}

Before this patch, calling `new PaymentRequest(https://foo.com).show()`
without a user gesture could skip the payment sheet and go directly into
the payment handler for https://foo.com, i.e., the skip-UI flow.

This patch passes the user gesture flag from the renderer to the browser
and prevents the skip-UI flow for the cases when show() was called
without a user gesture.

After this patch, calling `new PaymentRequest(https://foo.com).show()`
without a user gesture will show the payment sheet, so the user will
have to explicitly provide the user gesture by tapping the "Pay" button
in the payment sheet before invoking the payment app.

Bug: 828427
Change-Id: Iaea5fe3ede1bbd4b68f2c06f63bde4bd36a38e43
Reviewed-on: https://chromium-review.googlesource.com/993412Reviewed-by: Chris Palmer <palmer@chromium.org>
Reviewed-by: anthonyvd <anthonyvd@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547862}

The tests were fixed in
https://github.com/w3c/web-platform-tests/pull/10286 and the output is
no longer flaky. Rebaselined.

TBR=foolip

Change-Id: I66e9ea8b8b169d9a3c30b4e80dd1a49c68f454a9
Reviewed-on: https://chromium-review.googlesource.com/994155Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547861}

Polymer2 does not support HTML element extensions, so all such elements need to
be converted to wrappers.

 - Introduced a new --cr-dialog-native CSS mixin, such that users of <cr-dialog>
   can still style the inner native <dialog>. Before, this was not necessary,
   since <cr-dialog> itself was a <dialog>, and not a wrapper. Update all such
   cases to use the mixin.
 - Introduced a public getNative() method to expose the internal <dialog>, which
   is necessary in a few cases (both tests and prod).
 - Mirrored <dialog>'s |open| attribute such  that it updates synchronously as soon
   a dialog is opened or closed. This matches the internal <dialog>'s behavior.
 - Updated tests as necessary (and did a significant amount of manual sanity
   checking).

Bug: 818279
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I4fb35237d3ea3fa3dbb8ef4602036a4783f1e896
Reviewed-on: https://chromium-review.googlesource.com/976394Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Scott Chen <scottchen@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547860}

This patch starts re-rendering StylePropertyTreeElement instances
if their computed value gets changed after edit.

R=dgozman

Change-Id: I5528238e3eeeafa1e71fb3e3543d1d600a46f9f1
Reviewed-on: https://chromium-review.googlesource.com/991598Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547859}

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

Bug: 790378,790311,790308
Change-Id: Idfbe439e45d56de46846abfe12694a1da14503d1
Reviewed-on: https://chromium-review.googlesource.com/989116Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547857}

In draw occlusion algorithm, the total area of drawing is calculated to
measure the effectiveness of draw occlusion. However, the integer
multiplication in the area calculation has caused the integer overflow
crash with huge draw quads. In this patch, I used GetCheckedArea() to
check for the resulting area before assigning.

Bug: 826727

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I667b458ca6f7d477ba13036868536dd842e59068
Reviewed-on: https://chromium-review.googlesource.com/991121
Commit-Queue: Yi Xu <yiyix@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547856}

The UNW_INDEX table has 2 columns: address and index. This table is
represented column wise so that binary search uses lesser number of
pages and it is easier to represent the memory map as arrays of
primitive types.

BUG=819888

Change-Id: I7f3245cfc1526425aed414fe89ee01661b914a40
Reviewed-on: https://chromium-review.googlesource.com/985151
Commit-Queue: Siddhartha S <ssid@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547855}

Bug: 826005
Change-Id: I237dbf4ae50b02a225110fa72dc0bb0c0127535f
Reviewed-on: https://chromium-review.googlesource.com/993755
Commit-Queue: Min Chen <minch@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547854}

As request by khmel@ After we add new content to Arc opt-in flow, we
should at least make legacy code not broken or crashed as long as we
have not removed it.
Note: Do not merge to M66. Legacy code is not running in product.

Bug: b/73452374
Bug: 826927
Test: Manual
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I1a1431c8afd11898cdd7e4b21dfe1ca6bfc09aad
Reviewed-on: https://chromium-review.googlesource.com/993708Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Long Cheng <lgcheng@google.com>
Cr-Commit-Position: refs/heads/master@{#547853}

* transform_feedback/switching-objects.html - Mac/NVIDIA
* transform_feedback/switching-objects.html - Linux/AMD
* clipping-wide-points - Win/NVIDIA (ANGLE GL backend)

TBR=kbr@chromium.org
NOTRY=true

Bug: 828572, 828579
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I6e62daa01635fe00f94e7943d5c7647c5d1a7bc6
Reviewed-on: https://chromium-review.googlesource.com/994185
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547852}

Adds a new OWNERS file for the shared preference file directory.
The files in here are simple, test-only config files, so it's set to
allow any commiter to provide a rubber stamp.

Change-Id: Ib858380befc6103a615cb84259bcc1dbc813bda3
Reviewed-on: https://chromium-review.googlesource.com/994143Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547851}

The recent Jinja2 update from 2.8 to 2.10 included a change to the
indent filter which introduced a large number of newlines to the
generated bindings files. This CL returns the templates to roughly the
old behaviour, by trimming the leading and trailing whitespace from
template variables before indenting them.

Change-Id: I5c24bc9441f96752a74914f1c2cac896a55e4edf
Reviewed-on: https://chromium-review.googlesource.com/992752Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547850}

https://pdfium.googlesource.com/pdfium.git/+log/232b918d1f0f..4c22dd5690cd

$ git log 232b918d1..4c22dd569 --date=short --no-merges --format='%ad %ae %s'
2018-04-03 dsinclair Use Optional to determine if appearance stream as font

Created with:
  roll-dep src/third_party/pdfium
BUG=chromium:827430


The AutoRoll server is located here: https://pdfium-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.


TBR=dsinclair@chromium.org

Change-Id: I30faeebc027568db41b6c9bf5e4d7240cec7dc0d
Reviewed-on: https://chromium-review.googlesource.com/993697
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#547849}

Currently in the DeviceOrientation and DeviceMotion unit tests and
browser tests, each fake sensor creates a new shared memory handle.
While in the production code, only one shared memory handle is created
and all sensors share it, and write data to that shared memory using
different offset. This CL updates the FakeSensor and FakeSensorProvider
to match the behavior of production code.

Bug: 824591
Change-Id: I545d73b0d864a3b7093a387d007cab26fb912d91
Reviewed-on: https://chromium-review.googlesource.com/978856
Commit-Queue: Jun Cai <juncai@chromium.org>
Reviewed-by: Tim Volodine <timvolodine@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547848}

This test does not pass because of a typo in the ref file.

Change-Id: I2673137789267359544a50e126d3ba16b728770b
Reviewed-on: https://chromium-review.googlesource.com/989455
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547847}

The method is used for ContentView only. Moved the logic to
ContentView, and deleted the interface from InternalAccessDelegate.

Bug: 598880
Change-Id: Ic07e2545b070e11d5653fd135d7396c65721cf71
Reviewed-on: https://chromium-review.googlesource.com/991620Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547846}

Remove the code rounding nacl input event to integers.

BUG=chromium:828486

Change-Id: Icd60c7c8e133e8bd0143712a779feb24059ac62d
Reviewed-on: https://chromium-review.googlesource.com/993152
Commit-Queue: Jingkui Wang <jkwang@google.com>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547845}

Per PM's request, disable splitscreen on M66 stable channel.
This CL will be merged back to M66 and then reverted later on tot.

TBR=xiyuan@chromium.org

Bug: 827322
Change-Id: I0040d7a8e98841fee1808fe3a0589dd3c8b384ef
Reviewed-on: https://chromium-review.googlesource.com/993472Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547844}

This moves the new isolated-script-based installer test to run on
Win10 as an experiment, rather than running locally on Win Fast
Ring (also fixing the gtest misconfiguration).

No-Try: true
Bug: 827546

Change-Id: I687a763d81c7095c88a6c879156ff2043336a863
Reviewed-on: https://chromium-review.googlesource.com/988260Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547843}

This makes sure that no race conditions exist between navigating to a
blob URL and revoking it. Currently only implemented for the network
service code path.

Also add one more navigation-then-revoke WPT test, as the existing tests
didn't cover the NavigationScheduler code-path.

Design doc: https://docs.google.com/document/d/1DqVcTWE9Qb_3KpIRH2bFV-6hWEr8S92c4ppY67YL1KI/edit#heading=h.n4fzuc6mgziv

Further navigation cases are handled in https://chromium-review.googlesource.com/c/chromium/src/+/899508.

Bug: 800901
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Icf9a4725526b4329a2841626977292802ad2fa7a
Reviewed-on: https://chromium-review.googlesource.com/898009Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547842}

Bug: 823569
Change-Id: If226bd56a981e78aa2fe9da89e144b930a064502
Reviewed-on: https://chromium-review.googlesource.com/991074Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Robert Ogden <robertogden@google.com>
Cr-Commit-Position: refs/heads/master@{#547841}

Signals in the TileManager are somewhat muddled.  Prior to this patch:

* PrepareTiles resets the signals.
* When a task set completes (draw/activate/all), it sets the signal
  and then schedules CheckAndIssueSignals
* CheckAndIssueSignals unconditionally calls CheckPendingGpuWorKTiles
* CPGWT clobbers the value of ready to draw and ready to activate
  based on whether or not there is pending gpu work.
* If not in smoothness mode, then there are no pending gpu work tiles
  and so finishing activate tiles calling CheckAndIssueSignals will
  also set ready to draw, but the THIRD IsReadyToDraw check will fail
  and so it never does anything.
* Sending a signal to the client also unsets ready to draw / activate / etc.

This patch separates out tile task completion from gpu work completion,
which means that no values are ever unset except for PrepareTiles and
we only do ready to draw/activate checks when both the tile work and
the gpu work is done.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I77db37729761d99daa7ce747a4b3809a6d033363
Reviewed-on: https://chromium-review.googlesource.com/993157Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547840}

For future reference, the correct "order" of monitors in X11
is the one given by xrandr --listmonitors

Bug: 822068
Change-Id: I6ceedc8db1d381ab3955af584fd365a764910ea7
Reviewed-on: https://chromium-review.googlesource.com/972547
Commit-Queue: Fredrik Hubinette <hubbe@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547839}

If the trusted CDN publisher is not available, fall back to parsing the URL.

Bug: 814365
Change-Id: I8c51cf33f015ba251de492d336bdc50cdc6cd822
Reviewed-on: https://chromium-review.googlesource.com/983413Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547838}

This patch makes it possible to request a copy output before the first
frame has been submitted. These requests are queued and are processed
when the frame is received. Also, this ensures to read the surface id
which is at or greater than the requested surface id.

This patch is a part of the work to make OOPIF pixel dumps work in
layout tests. Specifically, we're transitioning from using non-production
code that synchronously composites and reads back the surface to using
the copy output / readback from surface code. However, because of the
sensitive timing, it is likely that the layout test driver would issue
a request before the latest frame has been processed.

R=fsamuel@chromium.org

Bug: 667551
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: Ibc1a79cf38db54b34853e41e19d6721475371220
Reviewed-on: https://chromium-review.googlesource.com/978870
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547837}

Browser needs information about selection to be able to show selection
touch handles. When Viz display compositor is enabled, browser does not
receive CompositorFrameMetadata which contains this info and it needs to
be added to RenderFrameMetadata.

BUG=777882
TEST= content_browsertests:
       - TouchSelectionControllerClientAuraScaleFactorTest.*
       - TouchSelectionControllerClientAuraTest.*
      cc_unittests:
       - LayerTreeHostImplTest.SelectionBoundsPassedToRenderFrameMetadata

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I8d1d03efb22d308048bfa8939af57658cee28b15
Reviewed-on: https://chromium-review.googlesource.com/980583Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Mohsen Izadi <mohsen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547836}