- 22 Oct, 2019 40 commits
-
-
Rakina Zata Amni authored
This is a reland of 2000b5b1 Got reverted because of MSAN failure didn't run the msan bot one last time before submitting yesterday after I changed some things to use skip-viewport-activation, oops. The MSAN failure is because we never initialize the enum ax::mojom::NameFrom in InspectorAccessibilityAgent::FillCoreProperties when the ax object is a display:none node within a locked subtree, so I set a default value for it, and it doesn't fail now! Original change's description: > DL: Fix flaky getFullAXTree & wrongly updated accessibility tests > > A devtoools display locking a11y test was marked as failing in MSAN bots > and is also flaky when tested locally, this CL updates that test and > fixes the cause of the failure (getFullAXTree might be called when > style/layout is dirty, which caused failing DCHECKs). > > Some other display locking a11y tests were not updated correctly, and is > updated in this CL as well. > > Bug: 996625 > Change-Id: I32eac1385c54eb07b1e6dab800620a2485158437 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846618 > Commit-Queue: Rakina Zata Amni <rakina@chromium.org> > Reviewed-by: vmpstr <vmpstr@chromium.org> > Reviewed-by: Alice Boxhall <aboxhall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#706834} Bug: 996625 Change-Id: I168e40614ab600d1bd11f5cf97c166fa95400213 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866338Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#708131}
-
Andreas Haas authored
With recent changes in V8 it is not necessary anymore to call {AdjustAmountOfExternalAllocatedMemory} for memory of ArrayBuffers. V8 get this information now from ArrayBuffer objects on the heap. R=ulan@chromium.org, haraken@chromium.org Bug: chromium:1008840 Change-Id: I886b391e1655835ade39dc43027a392490d30cad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871876Reviewed-by:Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#708130}
-
Yuri Wiitala authored
Fixes a DCHECK crash related to the cursor device scale factor setting. It seems that sometimes this is left unset, and the default value of zero causes problems. Instead, just force it to 1X whenever it's less than 1X, since that's going to generate the best results for cursor rendering on screen captured content. Change-Id: I042da7ae8591a5e18ae79dbd32da19357069764e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872731Reviewed-by:
Takumi Fujimoto <takumif@chromium.org> Commit-Queue: Yuri Wiitala <miu@chromium.org> Cr-Commit-Position: refs/heads/master@{#708129}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/03882834cb55..9df4d22529ce git log 03882834cb55..9df4d22529ce --date=short --no-merges --format='%ad %ae %s' 2019-10-22 perezju@chromium.org [Telemetry] Remove support for chartjson output format Created with: gclient setdep -r src/third_party/catapult@9df4d22529ce If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC rmhasan@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md 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;luci.chromium.try:win_optional_gpu_tests_rel TBR=rmhasan@google.com Bug: chromium:921000 Change-Id: Idcf79b2661f4c238284f009604d12b9813947c7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873585Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#708128}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/4a152d340f06..f3f8ac37e468 git log 4a152d340f06..f3f8ac37e468 --date=short --no-merges --format='%ad %ae %s' 2019-10-22 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 4a80ba25e67b..5335faaece2a (2 commits) Created with: gclient setdep -r src/third_party/skia@f3f8ac37e468 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC michaelludwig@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=michaelludwig@google.com Bug: chromium:None Change-Id: Ia7cf260e051533b4b55248d981904fd3449ec5f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873586Reviewed-by:
-
Joel Hockey authored
Bug: 1016202 Change-Id: I820a076ed53960fcb4cc74a5ff1909ccf354453a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870153 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#708126}
-
Lindsay Pasricha authored
and add back iPhone7 bot coverage to fyi and main. Test cases: testNameOnCardFieldIsPresent testCardNumberFieldIsPresent testMonthOfExpiryFieldIsPresent testYearOfExpiryFieldIsPresent testUseCameraButtonIsPresent Bug: 1015953,1016353,1013462 Change-Id: I02c5a3d5b73b6e788f9001f65665f186fddf7aee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872559 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#708125}
-
Colin Blundell authored
Change-Id: I55de2281b96b1a141ac43d75b84677ec16ce7d67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1856967Reviewed-by:
Darin Fisher <darin@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#708124}
-
Yang Guo authored
https://chromium.googlesource.com/devtools/devtools-frontend/+log/032591d692..acb77af66d TBR=bmeurer@chromium.org Change-Id: Ifc684ee59db2247143aa5f048e31a75e0ce757f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871595Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#708123}
-
Peter Kotwicz authored
Currently WebAPKs force the toolbar to be shown when the page has a bad certificates but TWAs do not. This CL ports the functionality to TWAs This CL introduces TrustedWebActivityBrowserControlsVisibilityManager which manages the browser control visibility state. BUG=991079 Change-Id: I5bbd40356d33b40c79a6291abdd3ab239484c575 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871083 Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Cr-Commit-Position: refs/heads/master@{#708122}
-
Jinsuk Kim authored
BottomSheet triggers onSheetOpened event when the sheet offset goes beyond the height of the minimum swipable state which depends on |swipeToDissmissEnabled|. The method is mainly used for the transition from open to closed state. When transitioning from hidden to open, the minimum swipable state needs to take |isPeekStateEnabled| since even dismissable sheet can have the peek state when opening. Bug: 1014730 Change-Id: I46f4f8edaf7693d9ae4b6fe00a23d635baaa4d4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868211 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#708121}
-
Mario Sanchez Prada authored
Convert the remaining bits in both the implementation and clients from the browser and renderer processes for the FrameSinkVideoCapturer interface, and adapt unit tests. Bug: 955171, 978694 Change-Id: I87d6d2758d45f44554a1bd6c88fa0358d0709a0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863091 Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
enne <enne@chromium.org> Reviewed-by:
Yuri Wiitala <miu@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#708120}
-
Fredrik Söderquist authored
And its companion SVGAnimationElement::CalculateValuesAnimation(). Bug: 998526 Change-Id: I3895dc070d319f1cefa489e061a598b18a88cf98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871509 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#708119}
-
Roman Sorokin [CET] authored
This reverts commit 64014850. Reason for revert: The issue should've been fixed with CL:1868769 Original change's description: > Disable test flaky FingerprintSetupTest.FingerprintSetupCancel > > FingerprintSetupTest.FingerprintSetupCancel is very flaky on ChromeOS > since 2019/10/16. > > https://analysis.chromium.org/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyTQsSBUZsYWtlIkJjaHJvbWl1bUBicm93c2VyX3Rlc3RzQEZpbmdlcnByaW50U2V0dXBUZXN0LkZpbmdlcnByaW50U2V0dXBDYW5jZWwM&show_all_occurrences=1 > > TBR=tbarzic@chromium.org > > Bug: 1015014 > Change-Id: Id4210e6317067a5716212a12937ee079f562b4e9 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867198 > Reviewed-by: Lan Wei <lanwei@chromium.org> > Commit-Queue: Lan Wei <lanwei@chromium.org> > Cr-Commit-Position: refs/heads/master@{#707041} TBR=lanwei@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1015014 Change-Id: Ic75f35608fccd86db16e7c4f1e75dd626d237272 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871696Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#708118}
-
Roman Sorokin [CET] authored
This reverts commit cff91b98. Reason for revert: The issue should've been fixed with CL:1868769 Original change's description: > Disable test flaky RecommendAppsScreenTest.ParseError > > RecommendAppsScreenTest.ParseError is very flaky on ChromeOS > since 2019/10/16. > > https://analysis.chromium.org/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSBUZsYWtlIjljaHJvbWl1bUBicm93c2VyX3Rlc3RzQFJlY29tbWVuZEFwcHNTY3JlZW5UZXN0LlBhcnNlRXJyb3IM&show_all_occurrences=1 > > TBR=tbarzic@chromium.org > > Bug: 1015013 > Change-Id: Ia93fcd4624b6c35fae4e53c740e415e3a28f9b41 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867469 > Reviewed-by: Lan Wei <lanwei@chromium.org> > Commit-Queue: Lan Wei <lanwei@chromium.org> > Cr-Commit-Position: refs/heads/master@{#707140} TBR=lanwei@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1015013 Change-Id: I88411768f64de6b92e2bdcba74459dd55f736040 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872584Reviewed-by:
-
Roman Sorokin [CET] authored
This reverts commit 0e80dc08. Reason for revert: The issue should've been fixed with CL:1868769 Original change's description: > Reland "Disable WelcomeScreenBrowserTest.WelcomeScreenNext." > > This reverts commit 60f3e975. > > Reason for revert: > WelcomeScreenBrowserTest.WelcomeScreenNext is still flaky on ChromeOS, > https://analysis.chromium.org/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyTAsSBUZsYWtlIkFjaHJvbWl1bUBicm93c2VyX3Rlc3RzQFdlbGNvbWVTY3JlZW5Ccm93c2VyVGVzdC5XZWxjb21lU2NyZWVuTmV4dAw > > Original change's description: > > Revert "Disable WelcomeScreenBrowserTest.WelcomeScreenNext." > > > > This reverts commit 2aa5da39. > > > > Reason for revert: reenabling given crrev.com/1864618 > > > > Original change's description: > > > Disable WelcomeScreenBrowserTest.WelcomeScreenNext. > > > > > > Bug: 1014952 > > > Change-Id: I1df1941c2a0a92d243cb4e4624ae920b150c7694 > > > Tbr: achuith@chromium.org > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865351 > > > Reviewed-by: John Budorick <jbudorick@chromium.org> > > > Commit-Queue: John Budorick <jbudorick@chromium.org> > > > Cr-Commit-Position: refs/heads/master@{#706500} > > > > TBR=achuith@chromium.org,jbudorick@chromium.org > > > > Change-Id: I86cba6fe329f52b5bdcd7b07d04d1dfb40fa65cf > > No-Presubmit: true > > No-Tree-Checks: true > > No-Try: true > > Bug: 1014952 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866407 > > Reviewed-by: John Budorick <jbudorick@chromium.org> > > Commit-Queue: John Budorick <jbudorick@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#706891} > > TBR=achuith@chromium.org,jbudorick@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 1014952 > Change-Id: I57bebd90ee517d2c2d729fc91dcef9667ea3ebe0 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869073 > Reviewed-by: Lan Wei <lanwei@chromium.org> > Reviewed-by: John Budorick <jbudorick@chromium.org> > Commit-Queue: Lan Wei <lanwei@chromium.org> > Cr-Commit-Position: refs/heads/master@{#707486} TBR=achuith@chromium.org,lanwei@chromium.org,jbudorick@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1014952 Change-Id: I1684b0b73c3b4a16ff154906b148b96ed7d35ba9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872582Reviewed-by:
-
Roman Sorokin [CET] authored
This reverts commit 028ae484. Reason for revert: The issue should've been fixed with CL:1868769 Original change's description: > Disable HIDDetectionScreenTest.BluetoothDeviceConnected. > > Bug: 1014951 > Change-Id: I0212752e770b5d995b81e1c98447f3ff4a9d116c > Tbr: achuith@chromium.org > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866789 > Reviewed-by: John Budorick <jbudorick@chromium.org> > Commit-Queue: John Budorick <jbudorick@chromium.org> > Cr-Commit-Position: refs/heads/master@{#706924} TBR=achuith@chromium.org,jbudorick@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1014951 Change-Id: I59f7cfd9f9dcfe2b2cb6e9fe63a518a2de33cab0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872583Reviewed-by:
-
Mario Sanchez Prada authored
While migrating viz::mojom::FrameSinkVideoConsumerFrameCallbacks to the new Mojo types[1], we migrated the InterfacePtr inside the FramePinner struct passed as context SkBitmap::installPixels() as |context| to a mojo::Remote, causing a crash when such struct gets released since that will happen in a different thread than the one the mojo::Remote was originally bound from. Since the purpose of this struct is just to keep some shared memory from being released before the pixels passed to SkBitmap::installPixels stop being referenced (and not to use the mojo::Remote<> in any other way), we can instead make FramePinner::releaser a mojo::PendingRemote<> and just pass the result of calling |callback_remote.Unbind()| when constructing the FramePinner struct, ensuring that the remote gets unbound in the right thread. [1] https://crrev.com/c/1860534 Bug: 955171, 978694, 1016005 Change-Id: I3df1f8e983fe8d8ead17cf627e0e69847a2e6b3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871514Reviewed-by:
Dana Fried <dfried@chromium.org> Reviewed-by:
-
Mostyn Bramley-Moore authored
BUG=1015750 Change-Id: Id277dc2a8a63dc1e15520cad324245fa3187aee5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871429Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: Mostyn Bramley-Moore <mostynb@vewd.com> Cr-Commit-Position: refs/heads/master@{#708113}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/f57feff78678..5e634c8999e6 git log f57feff78678..5e634c8999e6 --date=short --no-merges --format='%ad %ae %s' 2019-10-22 47668180+tsuoranta@users.noreply.github.com Enable generation of compile_commands.json (#1938) Created with: gclient setdep -r src/third_party/glslang/src@5e634c8999e6 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,jonahr@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=radial-bots+chrome-roll@google.com,jonahr@google.com Bug: None Change-Id: I3312dd3ee714619b1180b2c6665a88a861e7b062 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873100Reviewed-by:
-
Peter Kasting authored
Bug: 82078 Change-Id: Ie7c619084a2b70ff5e4c377bc525d663c2c2b1bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872727Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#708111}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/618d7e7febd0..4a152d340f06 git log 618d7e7febd0..4a152d340f06 --date=short --no-merges --format='%ad %ae %s' 2019-10-22 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update Go deps Created with: gclient setdep -r src/third_party/skia@4a152d340f06 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC michaelludwig@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=michaelludwig@google.com Bug: None Change-Id: I3582f4673231c064e975998d860c6b634116c25d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873099Reviewed-by:
-
Michael Achenbach authored
This adds build configs for a devtools release trybot for running blink layout tests. TBR=jbudorick@chromium.org Bug: 1016290 Change-Id: Ieb73cdd6786545a1216165b5cc701c8628182a56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872092Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#708109}
-
Juan Antonio Navarro Perez authored
This CL migrates the final few press benchmarks (dromaeo and speedometer2) which were still directly writing histograms to use the measurements system instead. Also, stop calling PopulateHistogramSet. This is no longer needed since the measurements to histograms translation is now handled by results processor. Bug: 999484 Change-Id: Ieb7b88aedddae731c029eb9954119479a783d2c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869008Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#708108}
-
Leon Han authored
This is the 1st CL to support access to the id field of ndef records. The plan is: 1. Introduces NDEFRecord{Init}#id and supports reading. 2. Supports writing. 3. Introduces NFCScanOptions#id and filters records by it when scanning. 4. Removes NDEFMessage{Init}#url and old impl of the author record. BUG=520391 Change-Id: Id80fc22d8c0535e60edc3f1e16a2a1135c623458 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1861574 Commit-Queue: Leon Han <leon.han@intel.com> Reviewed-by:Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#708107}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/834ee546f93d..f57feff78678 git log 834ee546f93d..f57feff78678 --date=short --no-merges --format='%ad %ae %s' 2019-10-22 dexcelstraun7@gmail.com Fix the exports of glslang-default-resource-limits (#1942) 2019-10-22 johnkslang@users.noreply.github.com Merge pull request #1941 from ehsannas/bazel_build Created with: gclient setdep -r src/third_party/glslang/src@f57feff78678 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,jonahr@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=radial-bots+chrome-roll@google.com,jonahr@google.com Bug: None Change-Id: Iddebe75b3d5b086e8cd400ebde8e6386c9abaf98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873097Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/81e8d3b29662..618d7e7febd0 git log 81e8d3b29662..618d7e7febd0 --date=short --no-merges --format='%ad %ae %s' 2019-10-22 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 26c6c4a5eb83..23f9c25f60ee (2 commits) Created with: gclient setdep -r src/third_party/skia@618d7e7febd0 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC michaelludwig@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=michaelludwig@google.com Bug: chromium:None Change-Id: I35ecfad6a99d89dbbf56e09d0758e79d530920dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873096Reviewed-by:
-
Ian Clelland authored
With this CL, items parsed from structured headers are tagged with the data type they were parsed as, which can be used to detect invalid headers, and preserves information which will be needed in order to serialize header values in the future. The existing uses of parsed structured headers are updated to take advantage of this information. Bug: 1011101 Change-Id: Ie42a08f562799626c0d4eb42c6bf4061a16b9786 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866617Reviewed-by:
Tsuyoshi Horo <horo@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#708104}
-
Lukasz Anforowicz authored
The default state of the UsePdfCompositorServiceName has no impact on the condition that refers to this feature in CreateCompositeClientIfNeeded in //components/printing/browser/print_manager_utils.cc: - On desktop, the feature is always enabled, but this is not important since ShouldPdfCompositorBeEnabledForOopifs will return true on desktop because of UseDedicatedProcessesForAllSites. - On Android the feature is always disabled, so there is no point in consulting the feature from ShouldPdfCompositorBeEnabledForOopifs. Bug: 824867 Change-Id: I15790906a0c124571dba79e2c02f1c6a68aff935 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864010Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Mark Pearson <mpearson@chromium.org> Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#708103}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ea7ed55c01a4..27f6d3d34924 Created with: gclient setdep -r src-internal@27f6d3d34924 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: Icc61f5333d2a4f37b364b306754055769e00c19e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873093Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#708102}
-
Jon Flatley authored
Extends the enable-experimental-kernel-vm-support flag lifetime until M82. Bug: none Change-Id: Ia66b829cc3bf47bc8d9f2017c6bf0db589cd96c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860530Reviewed-by:
Nicholas Verne <nverne@chromium.org> Commit-Queue: Nicholas Verne <nverne@chromium.org> Cr-Commit-Position: refs/heads/master@{#708101}
-
Hans Wennborg authored
https://chromium.googlesource.com/libyuv/libyuv.git/+log/f9aacffa029f..53b529e362cc $ git log f9aacffa0..53b529e36 --date=short --no-merges --format='%ad %ae %s' 2019-10-21 hans Remove #pragma clang loop vectorize_width 2019-10-14 fbarchard RAWToRGBA for 3 channel OCR 2019-10-07 efoo Add "# COMPONENT" to libyuv OWNERS file 2019-10-07 fbarchard ARGBToY use 8 bit precision instead of 7 bit. 2019-09-06 mbonadei Allowing C++14 in libyuv. 2019-09-17 mbonadei Re-enable optimize_max to fix UBSan. 2019-09-11 fbarchard MMI Optimized functions I422ToARGB for 1080p video 2019-09-11 libyuv-ci-autoroll-builder Roll chromium_revision 08ed8f83..30ccb0cb (693151:695606) 2019-09-04 libyuv-ci-autoroll-builder Roll chromium_revision 8d7ec560..08ed8f83 (691142:693151) 2019-08-29 mbonadei Update android_sdk/public/build-tools and third_party/android_deps. 2019-08-15 fbarchard Disable tests via macro that refer to row.h 2019-08-10 libyuv-ci-autoroll-builder Roll chromium_revision 2ab7c191..8f1ff9df (683574:685863) 2019-08-06 fbarchard AVX2 versions of ABGRToNV12 and ABGRToNV21 2019-08-06 fbarchard Add ABGRToNV21 and ABGRToNV12 Fix ARGBToUVJRow_AVX2 constants for win32 2019-08-02 libyuv-ci-autoroll-builder Roll chromium_revision bc5b06fa..2ab7c191 (681273:683574) 2019-07-20 fbarchard SwapUV AVX2 and SSSE3 2019-07-26 libyuv-ci-autoroll-builder Roll chromium_revision e02114c8..bc5b06fa (678980:681273) 2019-07-19 oprypin Roll chromium_revision 4476bd69..e02114c8 2019-07-18 mbonadei Fix chromium autoroller to parse new clang revision format. 2019-07-17 fbarchard NV21 unittest and benchmark Created with: roll-dep src/third_party/libyuv R=fbarchard@chromium.org Bug: 1015665 Change-Id: I378cf62e7b1cf8fa758cd7f9f27d3ff042a46ee6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872097 Auto-Submit: Hans Wennborg <hans@chromium.org> Commit-Queue: Frank Barchard <fbarchard@chromium.org> Reviewed-by:
Frank Barchard <fbarchard@chromium.org> Cr-Commit-Position: refs/heads/master@{#708100}
-
Christopher Thompson authored
This adds support code for collecting user behavior metrics for the legacy TLS deprecation UI. Bug: 1016105 Change-Id: Ia8ebde562fbd882055b285866d6351c4d30860c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872296 Commit-Queue: Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#708099}
-
Haoming Chen authored
With the new Widevine CDM, support for encrypted VP9 profile 2 has been added. So change the supports_vp9_profile2 capability to true for ChromeOS. Other OSes will get the VP9 profile 2 support from the Widevine CDM manifest. This changes also updates the browser tests expected result to SUCCESS for VP9 profile 2. Bug: 707128 Change-Id: Idfedd94c726afa22b538870eb103b1fdb6d51209 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866011 Commit-Queue: Haoming Chen <hmchen@chromium.org> Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
John Rummell <jrummell@chromium.org> Cr-Commit-Position: refs/heads/master@{#708098}
-
Yi Gu authored
There will not be such specialized subclass with root-layer-scrolling. Bug: None Change-Id: I7deba376df09673e7da5c91b65a7c4386dabe3c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872925 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#708097}
-
Eric Willigers authored
The implementation of ShouldShowCustomTabBar is moved up from HostedAppBrowserController to AppBrowserController, with dependencies on extensions removed. The CustomTabBarViewBrowserTest tests now pass with BMO. TBR=bsep@chromium.org Bug: 966290 Change-Id: I541964d2deb5d30e231bdd79d199c14b26321040 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871154 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Alan Cutter <alancutter@chromium.org> Cr-Commit-Position: refs/heads/master@{#708096}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/ead0ec9a2017..b9014fb4bb68 git log ead0ec9a2017..b9014fb4bb68 --date=short --no-merges --format='%ad %ae %s' 2019-10-22 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision b528279c..9b6351c7 (707828:708073) Created with: gclient setdep -r src/third_party/webrtc@b9014fb4bb68 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=webrtc-chromium-sheriffs-robots@google.com Bug: chromium:None Change-Id: I2393b0bc97e25f977be58985734e9eb26e93e3ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873095Reviewed-by:
-
Jakob Gruber authored
The V8 natives blob (natives_blob.bin) is unused and will shortly be removed in V8. This CL removes all related infrastructure in chromium. Specifically, this means that natives_blob.bin is no longer 1. generated during the build process, 2. installed on the target system, 3. loaded by chrome at runtime, and 4. passed to V8. Tbr: oksamyt@chromium.org Bug: v8:7624 Change-Id: I535d4308a8aa539c354a212174d47ade411bc89d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847217Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Greg Thompson <grt@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#708094}
-
Mirko Bonadei authored
No-Try: True Bug: 1006238 Change-Id: I20bc6b5ccb3d2d76bca741b4e4edc43a91f8a692 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872730Reviewed-by:
-
Lei Zhang authored
Also enforce modern Bind/Callback in device/udev_linux/. Also fix lint errors. Bug: 714018 Change-Id: Ic312e3a1df3ec63a4d2bc8bb5f2f52e7728f1006 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869286Reviewed-by:
-
![Roman Sorokin [CET]'s avatar](https://secure.gravatar.com/avatar/7b28a287700b8b8659a03c33a38be1a8?s=80&d=identicon "Roman Sorokin [CET]")
