GitLab

Allow ranges for font-stretch in @font-face, compare
https://drafts.csswg.org/css-fonts-4/#font-prop-desc

Bug: 749091
Change-Id: I79cafc1f7c496617bfb4eca21e28b4b451bdfae5
Reviewed-on: https://chromium-review.googlesource.com/582862
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: meade_UTC10 <meade@chromium.org>
Reviewed-by: Bugs Nash <bugsnash@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491697}

This reverts commit 01f38b46.

Reason for revert: Sorry, this broke compilation on 3 bots:
- https://build.chromium.org/p/chromium.android/builders/Android%20x86%20Builder%20%28dbg%29
- https://build.chromium.org/p/chromium.android/builders/Android%20x64%20Builder%20%28dbg%29
- https://build.chromium.org/p/chromium.android/builders/Android%20MIPS%20Builder%20%28dbg%29

With the following linker error:

obj/ui/message_center/message_center/notification.o: In function `message_center::Notification::CreateSystemNotification(...)':
../../ui/message_center/notification.cc:182: undefined reference to `gfx::kNoneIcon'
obj/ui/message_center/message_center/notification.o: In function `message_center::Notification::CreateSystemNotification(...)':
../../ui/message_center/notification.cc:232: undefined reference to `gfx::CreateVectorIcon(gfx::VectorIcon const&, unsigned int)'


Original change's description:
> Add first-party notification styling in MD notification.
> 
> In new-style notification, first-party notification should have
> different styling compared to general web notifications.
> To do this, all system notifications should be created by
> new CreateSystemNotification. (Previously, it was not a requirement.)
> 
> By using the function,
> * the display source defaults to string "ChromeOS system".
> * the notification has single accent color based on
>   SystemNotificationWarningLevel.
> * gfx::VectorIcon will be passed as small_image instead of gfx::Image
>   to perform icon coloring on CreateSystemNotification side.
> 
> TEST=out/Debug/message_center_unittests
> BUG=738779,726241,740807,740813
> 
> Change-Id: I9e85b3f1de33b6499297f060b5305d0b02157eef
> Reviewed-on: https://chromium-review.googlesource.com/566765
> Reviewed-by: James Cook <jamescook@chromium.org>
> Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
> Reviewed-by: Peter Beverloo <peter@chromium.org>
> Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491592}

TBR=jamescook@chromium.org,yoshiki@chromium.org,peter@chromium.org,fukino@chromium.org,tetsui@chromium.org

Change-Id: I10fe30dbdad6012fbafe32c17a439065f4d816d3
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 738779, 726241, 740807, 740813
Reviewed-on: https://chromium-review.googlesource.com/600067Reviewed-by: John Mellor <johnme@chromium.org>
Commit-Queue: John Mellor <johnme@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491696}

This reverts commit 9869d2f1.

Reason for revert: Suspect of making console tests to fail consistently on WebKit Win7 (dbg) (stats) bot.

See
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7%20%28dbg%29/builds/10448


Unexpected Failures:
* http/tests/devtools/console/console-correct-suggestions.js
* virtual/mojo-loading/http/tests/devtools/console/console-correct-suggestions.js



Original change's description:
> DevTools: transform console tests (part 2)
> 
> F/u from https://chromium-review.googlesource.com/c/595238
> 
> Bug: 667560
> Change-Id: I4e387fae79ab4de0965f84a045c4fd04631b9e7d
> Reviewed-on: https://chromium-review.googlesource.com/597312
> Commit-Queue: Will Chen <chenwilliam@chromium.org>
> Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491501}

TBR=dgozman@chromium.org,chenwilliam@chromium.org

Change-Id: Ib2d71bb01073eedd692d2416c688c2985b16b3c3
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 667560
Reviewed-on: https://chromium-review.googlesource.com/599828Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491695}

This flag was present in chrome, but ignored in headless.
This commit makes headless behave as expected.

R=eseckler@chromium.org

Bug: 714287
Change-Id: I2b06c345c1f29eb4390e7853537af9cf5d809bb8
Reviewed-on: https://chromium-review.googlesource.com/599809Reviewed-by: Eric Seckler <eseckler@chromium.org>
Commit-Queue: Luca Versari <veluca@google.com>
Cr-Commit-Position: refs/heads/master@{#491694}

In addition the CL changes some tests to use ScopedTaskEnvironment where appropriate instead of MessageLoop.

Bug: 741660
Change-Id: I9993eaba6bd92e30dfe4a39a5fb89518d5ba4a3d
Reviewed-on: https://chromium-review.googlesource.com/584908
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Christos Froussios <cfroussios@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491693}

This is a reland of aecc33fc

Added test files for the bookmark appp. Without these tests fail in release
builds.


Original change's description:
> desktop-pwas: Open Bookmark app when link is within scope
> 
> The DesktopPWAWindowing feature must be on in order for this to work.
> 
> Makes it so that, once a user has installed a Bookmark App for a website, all
> navigations to that website will open the installed Bookmark App. This includes
> typing the address in the omnibox, clicking any links to an in-scope url, and
> opening any links to an in-scope url from the context menu. Future patches
> will change some of these so that the result is more intuitive.
> 
> For example, if the user has installed https://www.foo.com through
> "Add to shelf" and the site's manifest defines scope as "/scope" and then the
> user visits https://www.foo.com/scope/test.html, a new app window to
> https://www.foo.com/scope/test.html will open. If the user
> navigated to https://www.foo.com/index.html, we would not open a new app
> window since the address is not in-scope as defined by the site's manifest.
> 
> Three changes:
> 
> 1. Use 'scope' in the site's manifest to create a url handler for
>    the bookmark app.
> 2. Allow Hosted Apps that are Bookmark apps to use url handlers.
>    This means that any non-bookmark hosted app that has url handlers
>    will fail to load.
> 3. When handling a url that a Bookmark app could handle open the
>    the bookmark app with the specified url.
> 
> Bug: 740783
> Change-Id: Iac69b13dc33be9ecd7336f24ae9021d5dd0161d0
> Reviewed-on: https://chromium-review.googlesource.com/566199
> Reviewed-by: Jochen Eisinger <jochen@chromium.org>
> Reviewed-by: Ben Wells <benwells@chromium.org>
> Reviewed-by: Sky Malice <skym@chromium.org>
> Reviewed-by: Matt Giuca <mgiuca@chromium.org>
> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491644}

TBR=benwells@chromium.org,mgiuca@chromium.org,skym@chromium.org,jochen@chromium.org

Bug: 740783
Change-Id: I6fe97df85507d1e5fbb209ea0877c4345a8e03ab
Reviewed-on: https://chromium-review.googlesource.com/599647
Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491692}

While we are still compiling the report from the field trial, disable prerender
to be on the safer side in M61.

Bug: 678332, 735153, 520275
Change-Id: I30a2169533d30cbb85f53291223897caceddeb89
Reviewed-on: https://chromium-review.googlesource.com/584871
Commit-Queue: Egor Pasko <pasko@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491691}

Bug: 715998
Change-Id: I0066c9f3e87c2e3327ece2d1b357de1c4bd9c191
Reviewed-on: https://chromium-review.googlesource.com/595981
Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491690}

When the user opens a Reading List page, it should not be taken into
account for the computation of the Most Visited tiles.

Bug: 734067
Change-Id: Iec28e8086051777ab4c43a2e53778c7bab3d54b1
Reviewed-on: https://chromium-review.googlesource.com/596367
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Eric Noyau <noyau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491689}

For marker property, CSSPropertyInvalid was used as the 
"current_shorthand" in the old/non-API parsing method 
because it's not used. In its API, we use 
CSSPropertyMarker just to avoid confusion.  There is no 
real difference.

Bug: 668012
Change-Id: I528f7da64d6dc6537a248e8b6a08b3940c0f3b90
Reviewed-on: https://chromium-review.googlesource.com/597092
Commit-Queue: Jia Meng <jiameng@chromium.org>
Reviewed-by: Bugs Nash <bugsnash@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491688}

Follow up to https://chromium-review.googlesource.com/c/589927

Bug: 738881
Change-Id: I8234c93e7557fea982cf6f98fce45a5a6e2bf5c4
Reviewed-on: https://chromium-review.googlesource.com/593649
Commit-Queue: Jean-François Geyelin <jif@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491687}

Change-Id: If1e1ad4b48d3b97a209c8fe3727d885c64fdc8bd
Reviewed-on: https://chromium-review.googlesource.com/599136
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491686}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/43bd6d3f..19f1033a

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: Ib0623cadd4349df94d0d1743d11c8e75df73a288
Reviewed-on: https://chromium-review.googlesource.com/599375Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491685}

Sorry, I reverted wrong cl.

BUG: 751948
TBR=bcwhite@chromium.org,holte@chromium.org,olivierrobin@chromium.org

This is a reland of 433d6917
Original change's description:
> Make MetricsLog not need a PrefService.
> 
> Move system profile persistence to MetricsService.
> 
> Bug: 
> Change-Id: I5c31dc53de267dd9699a83af926f8a575bab18a0
> Reviewed-on: https://chromium-review.googlesource.com/592689
> Commit-Queue: Steven Holte <holte@chromium.org>
> Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
> Reviewed-by: Brian White <bcwhite@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491573}

Change-Id: Iea3ebc29e92f3e12fc56f7b7ba767c531f216041
Reviewed-on: https://chromium-review.googlesource.com/598759
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491684}

This reverts commit 44e59041.

Reason for revert: Caused LayoutTest failures on ASAN bot.
BUG:752013

Original change's description:
> Introduce SelectionForUndoStep
> 
> This patch introduces |SelectionForUndoStep| to hold selection for undo/redo
> instead of |VisibleSelection| and avoid dirty |VisibleSelection|[1] for
> improving code health.
> 
> Before this patch, we hold selection as |VisibleSelection| in |UndoStep| and
> recompute "visible selection" by |CorrectedSelectionAfterCommand()| at undo/redo
> time, DOM tree can be different when we save |VisibleSelection| in |UndoStep|.
> 
> After this patch, we use |SelectionForUndoStep| to hold selection at command
> execution and change |EndingVisibleSelection()| to compute visible selection
> before we used.
> 
> This patch looks large, but most of them are replacing
> |EndingVisibleSelection()| to |EndingSelection()| to use |SelectionInUndoStep|
> instead of updated |VisibleSelection|.
> 
> Essential part of this change is
>  * "CompositeEditCommand.{cpp,h}": holding starting and ending selection in
>    |SelectionInUndoStep|
> 
>  * "TypginCommand.{cpp,h}": Computing |SelectionInUndoStep| other than
>    |FrameSelection|.
>  * "SelectionInUndoStep.{cpp.h}": The implementation
>  * "UndoStep.{cpp,h}": holding staring and ending seleciton in
>  |SelectionInUndoStep|
> 
> Just for reference, there is another attempt in the patch:
> - http://crrev.com/2457523004: Introduce SelectionForUndoStep
> - http://crrev.com/c/582724 Introduce SelectionForUndoStep
> 
> [1] Dirty VisibleSelection: |VisibleSelection| holds canonicalized base and
> extent positions by using layout tree. Once layout tree is updated, e.g. by
> DOM change or style change, |VisibleSelection| may not be canonicalized. In
> other words, once we get |VisibleSelection|, it is valid only until layout tree
> updated.
> 
> Bug: 747795
> Change-Id: I2da864e03fbd2e06f5150072eafe133430dcbfcb
> Reviewed-on: https://chromium-review.googlesource.com/588874
> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491667}

TBR=yosin@chromium.org,yoichio@chromium.org,xiaochengh@chromium.org

Change-Id: I84188673f225161fc65da6ad1693a1721d2d8f5a
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 747795
Reviewed-on: https://chromium-review.googlesource.com/599667Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491683}

As the benchmark page_cycler_v2 is located under
src/tools/perf/contrib/cros_benchmarks, the patch fixes the failure
of deps searching for page_cycler_v2.typical_25 by adding the
benchmarks directory 'src/tools/perf/contrib' into search path.

BUG=728973
TEST=python src/tools/perf/fetch_benchmark_deps.py
  page_cycler_v2.typical_25 --platform=cros
Signed-off-by: Chung-yih Wang <cywang@chromium.org>
Change-Id: Id9e31488cba07bb433551b768ddaaa99e70a2b9d
Reviewed-on: https://chromium-review.googlesource.com/598127Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#491682}

See "Print Is A Function".

Bug: 742592
Change-Id: Ic2744a01a4149a466dab9a7c1208d36238206008
Reviewed-on: https://chromium-review.googlesource.com/599567Reviewed-by: Alice Boxhall <aboxhall@chromium.org>
Commit-Queue: Doug Turner <dougt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491681}

Add a section to chrome://snippets-internals to allow
testing and fetching contextual suggestions.
The section is only shown when flag
ContextualSuggestionsCarousel is on.

Bug: 749988
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I9cd371973c6871f93996515a1ac0eab5d3067343
Reviewed-on: https://chromium-review.googlesource.com/595974
Commit-Queue: Andre Gaschler <gaschler@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491680}

https://skia.googlesource.com/skia.git/+log/255607f094da..fba26ea9b7fc

$ git log 255607f09..fba26ea9b --date=short --no-merges --format='%ad %ae %s'
2017-08-03 mtklein exclude SkJumper_stages_8bit.cpp from Google3 build

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

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

The next CL will use the real data to update the UI. See screenshots
linked below for what it looks like with this CL and test data.

https://drive.google.com/a/chromium.org/file/d/0BxrfNSu8yqJqZG9reWl3T0FCclE/view?usp=sharing
https://drive.google.com/a/chromium.org/file/d/0BxrfNSu8yqJqUkNUVlFlYW5Uckk/view?usp=sharing

Bug: 622743
Change-Id: Icf8072513c202f9a0909d246c1476e2e2a55a705
Reviewed-on: https://chromium-review.googlesource.com/594052
Commit-Queue: Elodie Banel <lod@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491678}

TBR: hanxi
Bug: 751907
Change-Id: I231934d8e83384687d837e140f25e9d553c774ab
Reviewed-on: https://chromium-review.googlesource.com/599249Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491677}

https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/38bdf22bfe68..7e50824288fa

$ git log 38bdf22bf..7e5082428 --date=short --no-merges --format='%ad %ae %s'
2017-08-01 wl * src/truetype/ttgxvar.c (TT_Get_MM_Var): Fix thinko.
2017-08-01 wl Update CHANGES file.
2017-08-01 behdad [truetype] Fix loading of named instances.
2017-08-01 wl [sfnt, truetype] Minor adjustments for OpenType 1.8.2.
2017-07-26 wl [cff] Integer overflow.

Created with:
  roll-dep src/third_party/freetype/src
R=wangxianzhu@chromium.org,michaelbai@chromium.org,bungeman@chromium.org,drott@chromium.org

BUG=chromium:738343

Change-Id: If5ac9de7dce76fdf808cfb1d7c95125784831708
Reviewed-on: https://chromium-review.googlesource.com/598118
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491676}

This test doesn't timeout anymore. It fails reliably. Add an expected file for
it.

As this was the final test linking to bug 658997, we can finally close the
bug.

TBR=shimazu

Bug: 658997, 751959
Change-Id: I8acb6812a9c9c7824aa14d606a63ffbf7478f23e
Reviewed-on: https://chromium-review.googlesource.com/598661Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491675}

Delete the empty and unused files in web/.

Bug: 712963
Change-Id: If0b2f20834e2474ae8ebf23259079045a85601ec
Reviewed-on: https://chromium-review.googlesource.com/599139
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491674}

This reverts commit 293a6765.

Reason for revert:  I think this CL caused telemetry_unittests failures.

BUG:751967

Original change's description:
> Roll SwiftShader 4d3efed..8aa0768
> 
> https://swiftshader.googlesource.com/SwiftShader.git/+log/4d3efed..8aa0768
> 
> BUG=
> 
> TBR=kbr@chromium.org
> 
> TEST=bots
> 
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel,linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel
> 
> Change-Id: I1f88e9213f4387e38b4b9d1059d7ee9a419d755f
> Reviewed-on: https://chromium-review.googlesource.com/599015
> Reviewed-by: Alexis Hétu <sugoi@chromium.org>
> Commit-Queue: Alexis Hétu <sugoi@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491572}

TBR=sugoi@chromium.org,kbr@chromium.org

Change-Id: If0463d4bc1a2036feb1317a04c910dc33891755a
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Cq-Include-Trybots: master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel, linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Reviewed-on: https://chromium-review.googlesource.com/599174Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491673}

The GPU cache expects an unref for an empty decode as well (returned in
the case of a decode failure).

Bug: 751444
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ie3875f20a5d5126ae0277520bb032f22eb4e0779
Reviewed-on: https://chromium-review.googlesource.com/598488Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491672}

If the requesting renderer is not allowed access to the given origin,
browser reports GenerateStream and OpenDevice failures to the renderer.

This CL also adds a OnDeviceOpenFailed() method MediaStreamDispatcher
mojom interface, equivalent to legacy MediaStreamMsg_DeviceOpenFailed
IPC message.

Bug: 742682
Change-Id: I6ff2516dd22281cf4c1fad40b56257352f2bdec7
Reviewed-on: https://chromium-review.googlesource.com/597475
Commit-Queue: Chandan Padhi <c.padhi@samsung.com>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491671}

This reverts commit dd536442.

Reason for revert: prevents Chrome to start on ChromeOS/Eve, as evidenced by git bisect.

Original change's description:
> Remove unnecessary SetUpContext usage
> 
> It's no longer necessary to use SetUpContext to compensate for
> individual field accessors being called twice, as they are no
> longer called twice.
> 
> This removes all such uses of SetUpContext/TearDownContext.
> 
> BUG=None
> 
> Change-Id: I1162f095bc40fd73b2f06323c4f78ed5025e0ee6
> Reviewed-on: https://chromium-review.googlesource.com/596497
> Reviewed-by: Scott Violet <sky@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Commit-Queue: Ken Rockot <rockot@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491488}

TBR=sky@chromium.org,dcheng@chromium.org,jam@chromium.org,rockot@chromium.org

Change-Id: I98675b0de0477babfb46ab568c9e20fd127a9365
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: None
Reviewed-on: https://chromium-review.googlesource.com/598760Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491670}

This reverts commit 3553b1fe.

Reason for revert: Caused browser_tests failures.
* ProcessMemoryMetricsEmitterTest.FetchDuringTrace
* ProcessMemoryMetricsEmitterTest.FetchAndEmitMetrics
* ProcessMemoryMetricsEmitterTest.FetchThreeTimes

Bug:751948

Original change's description:
> Enable Finch Trial Test for MacV2Sandbox.
> 
> Bug: 749839
> Change-Id: Ie95fc3c6574377e278474c1709b7270847016b44
> Reviewed-on: https://chromium-review.googlesource.com/596422
> Reviewed-by: Jesse Doherty <jwd@chromium.org>
> Commit-Queue: Greg Kerr <kerrnel@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491576}

TBR=jwd@chromium.org,kerrnel@chromium.org

Change-Id: I6e96580d4e0cd7f2d810187a9f4864748e9997d4
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 749839
Reviewed-on: https://chromium-review.googlesource.com/599173Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491669}

In https://codereview.chromium.org/2969393002 per-file OWNERS were added
for PermissionContextBase subclasses, as they would benefit from
approval by permissions owners.

In https://codereview.chromium.org/2791623004/#msg148 jochen raised the
concern that set no-parent would interfere with large-scale
refactorings. Remove set no-parent declarations for now until we figure
out what the best way forward is.

Change-Id: I13b0fdec6b259e5db3bebf9dda425497b885af6f
Tbr: jochen@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/598662
Commit-Queue: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Timothy Loh <timloh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491668}

This patch introduces |SelectionForUndoStep| to hold selection for undo/redo
instead of |VisibleSelection| and avoid dirty |VisibleSelection|[1] for
improving code health.

Before this patch, we hold selection as |VisibleSelection| in |UndoStep| and
recompute "visible selection" by |CorrectedSelectionAfterCommand()| at undo/redo
time, DOM tree can be different when we save |VisibleSelection| in |UndoStep|.

After this patch, we use |SelectionForUndoStep| to hold selection at command
execution and change |EndingVisibleSelection()| to compute visible selection
before we used.

This patch looks large, but most of them are replacing
|EndingVisibleSelection()| to |EndingSelection()| to use |SelectionInUndoStep|
instead of updated |VisibleSelection|.

Essential part of this change is
 * "CompositeEditCommand.{cpp,h}": holding starting and ending selection in
   |SelectionInUndoStep|

 * "TypginCommand.{cpp,h}": Computing |SelectionInUndoStep| other than
   |FrameSelection|.
 * "SelectionInUndoStep.{cpp.h}": The implementation
 * "UndoStep.{cpp,h}": holding staring and ending seleciton in
 |SelectionInUndoStep|

Just for reference, there is another attempt in the patch:
- http://crrev.com/2457523004: Introduce SelectionForUndoStep
- http://crrev.com/c/582724 Introduce SelectionForUndoStep

[1] Dirty VisibleSelection: |VisibleSelection| holds canonicalized base and
extent positions by using layout tree. Once layout tree is updated, e.g. by
DOM change or style change, |VisibleSelection| may not be canonicalized. In
other words, once we get |VisibleSelection|, it is valid only until layout tree
updated.

Bug: 747795
Change-Id: I2da864e03fbd2e06f5150072eafe133430dcbfcb
Reviewed-on: https://chromium-review.googlesource.com/588874
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491667}

Change-Id: I7725654a919fa77f2a83199775cba2efeb1dcbb3
Reviewed-on: https://chromium-review.googlesource.com/599172Reviewed-by: Raymes Khoury <raymes@chromium.org>
Commit-Queue: Timothy Loh <timloh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491666}

Bug: 705566
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I664ac7f84cf422e7a1947566b6fe23a47c576bb1
Reviewed-on: https://chromium-review.googlesource.com/598509Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491665}

This reverts commit 24f0eb87.

Reason for revert: net_unittests fails on msan bot

NtlmClientTest.Type2MessageWithTargetName
NtlmClientTest.NoTargetNameOverflowFromLength

https://uberchromegw.corp.google.com/i/chromium.memory/builders/Linux%20MSan%20Tests/builds/3002

Original change's description:
> Add a functionally equivalent NTLMv1 implementation.
> 
> - Replacement NTLMv1 implementation.
> - In preparation for new NTLMv2 implementation.
> - Passes all unit tests and has the same behavior.
> - Adds fuzzer for NtlmClient.
> - Code is still not live.
> 
> BUG=chromium:22532
> TEST=All unit tests pass.
> 
> Change-Id: Idae533312805d21d49943fd634d54af3a93a7c00
> Reviewed-on: https://chromium-review.googlesource.com/598307
> Commit-Queue: Zentaro Kavanagh <zentaro@google.com>
> Reviewed-by: Asanka Herath <asanka@chromium.org>
> Reviewed-by: Matt Menke <mmenke@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491611}

TBR=rsleevi@chromium.org,mmenke@chromium.org,zentaro@google.com,asanka@chromium.org

Change-Id: I21057e6a0cc43aca6249153debe47e3630df82c7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: chromium:22532
Reviewed-on: https://chromium-review.googlesource.com/599140Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491664}

Bug: 714717
Change-Id: If707c50a569b1c9ebbed6568c2a6631e55bc1e95
Reviewed-on: https://chromium-review.googlesource.com/584632
Commit-Queue: Xiangjun Zhang <xjz@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Anton Vayvod <avayvod@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491663}

This reverts commit aecc33fc.

Reason for revert: BookmarkAppUrlRedirectorBrowserTest.InAppNavigation fails

BUG:751958

Original change's description:
> desktop-pwas: Open Bookmark app when link is within scope
> 
> The DesktopPWAWindowing feature must be on in order for this to work.
> 
> Makes it so that, once a user has installed a Bookmark App for a website, all
> navigations to that website will open the installed Bookmark App. This includes
> typing the address in the omnibox, clicking any links to an in-scope url, and
> opening any links to an in-scope url from the context menu. Future patches
> will change some of these so that the result is more intuitive.
> 
> For example, if the user has installed https://www.foo.com through
> "Add to shelf" and the site's manifest defines scope as "/scope" and then the
> user visits https://www.foo.com/scope/test.html, a new app window to
> https://www.foo.com/scope/test.html will open. If the user
> navigated to https://www.foo.com/index.html, we would not open a new app
> window since the address is not in-scope as defined by the site's manifest.
> 
> Three changes:
> 
> 1. Use 'scope' in the site's manifest to create a url handler for
>    the bookmark app.
> 2. Allow Hosted Apps that are Bookmark apps to use url handlers.
>    This means that any non-bookmark hosted app that has url handlers
>    will fail to load.
> 3. When handling a url that a Bookmark app could handle open the
>    the bookmark app with the specified url.
> 
> Bug: 740783
> Change-Id: Iac69b13dc33be9ecd7336f24ae9021d5dd0161d0
> Reviewed-on: https://chromium-review.googlesource.com/566199
> Reviewed-by: Jochen Eisinger <jochen@chromium.org>
> Reviewed-by: Ben Wells <benwells@chromium.org>
> Reviewed-by: Sky Malice <skym@chromium.org>
> Reviewed-by: Matt Giuca <mgiuca@chromium.org>
> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#491644}

TBR=benwells@chromium.org,calamity@chromium.org,mgiuca@chromium.org,ortuno@chromium.org,skym@chromium.org,jochen@chromium.org

Change-Id: I5e4bf4899d56fd2ffc1755b6cd5db0aa9c0c02d6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 740783
Reviewed-on: https://chromium-review.googlesource.com/599090Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491662}

https://pdfium.googlesource.com/pdfium.git/+log/b4fee4d5d471..d1a8458e6390

$ git log b4fee4d5d..d1a8458e6 --date=short --no-merges --format='%ad %ae %s'
2017-08-02 thestig Avoid a redundant header offset check in CPDF_Parser.
2017-08-02 hnakashima Replace CFX_ByteTextBuf with ostringstream in cfx_psrenderer.cpp.
2017-08-02 hnakashima Replace CFX_ByteTextBuf from cpdf_security_handler.cpp with std::vector
2017-08-02 rharrison Remove unused FromUnicode method
2017-08-02 art-snake Unify parsing of cross refs v4
2017-08-02 rharrison Remove parameter from GetID
2017-08-02 rharrison Remove support for out of bounds params in Delete

Created with:
  roll-dep src/third_party/pdfium


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


TBR=dsinclair@chromium.org

Change-Id: I633fc2cb7101cc1fcb0f8dc57be00c8f54f3c55c
Reviewed-on: https://chromium-review.googlesource.com/599392
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491661}

This patch moves |is_handle_visible_| to |FrameSelection| from |SelectionTemplate|
since handle visibility is used only for setting |FrameSelection|, hence it is
a redundant member variable of |SelectionTemplate|.

Bug: 742093
Change-Id: I3add4da3844fb40be34dcb4d4b46b5fa6fed1d7e
Reviewed-on: https://chromium-review.googlesource.com/595389
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491660}

Bug: 751906
Change-Id: I7f43cc71da5557ebf396280cf295f76ed04e9e91
TBR: chenwilliam@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/599138Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491659}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/45ad6a02..43bd6d3f

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: Ia552de41f9306dcbeefc8beb04a48252db18df00
Reviewed-on: https://chromium-review.googlesource.com/599157Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491658}