- 07 Mar, 2019 40 commits
-
-
Sam Maier authored
Bug: 939148 Change-Id: If82c99bfdf0834589a818591502928212ad35e34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508694 Commit-Queue: Sam Maier <smaier@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Auto-Submit: Sam Maier <smaier@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#638612}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5b257f91fc81..fff41430adb0 Created with: gclient setdep -r src-internal@fff41430adb0 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=hkamila@chromium.org,robliao@chromium.org,etiennep@chromium.org Change-Id: Iff68f0840621d962d57111f3518f089c10c3b932 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508832Reviewed-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@{#638611}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/c0eace27e740..2d4d2a3cf7b9 git log c0eace27e740..2d4d2a3cf7b9 --date=short --no-merges --format='%ad %ae %s' 2019-03-07 treehugger-gerrit@google.com Merge "Fix build." Created with: gclient setdep -r src/third_party/perfetto@2d4d2a3cf7b9 The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll 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=perfetto-bugs@google.com Change-Id: I8fa07e1ec24322b3e41158eedc19af82f3ad01ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508554Reviewed-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@{#638610}
-
Antonio Gomes authored
Bug 933878 is phasing out the use of AsyncFileSystemCallbacks in favor of concrete callback classes. This CL is a follow up of [1] replaces a left over usage and removes a unneeded include. [1] crrev.com/c/1499873 R=jbroman@chromium.org CC=blink-reviews-vendor@chromium.org BUG=933878 Change-Id: Ia46cdc035da04c9c2c8d9c968d9d0163320b0c59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508612 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Auto-Submit: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#638609}
-
Evan Stade authored
Bug: 939191 Change-Id: I0fecec51bb541e3557790b2502df15346d0c5f61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1507275Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#638608}
-
arthursonzogni authored
* Make tryToSetTopLevelFrame() and tryToClearTopLevelFrame() to return void instead. Nobody was using the returned value anyway. * Remove topLoadingFrame(). I was not used externally. No behavior changes here. Bug: 936696 Change-Id: I21c4266140dba897a89f4ae558c2a30dbb44615b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1492339 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#638607}
-
Peter Beverloo authored
Through Finch configuration, the add to homescreen banner can now have one of three values (the first being the default option): - Add <site> to Home screen - Install <site> - Install <site> (no download required) Bug: 937871 Change-Id: Ie519d5e80f345c9ebdfff490659632f8842bddf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1499566 Commit-Queue: Peter Beverloo <peter@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#638606}
-
G. Silva authored
It will be used by the test engine later on to convert goldens to and from the processor-specific structures. Bug: 935711 Change-Id: I84d2ea9f8eb742b1d7f1a062eeea88dfb7f30d23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1492091 Commit-Queue: G. Silva <gfaus@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Reviewed-by:
Henrique Grandinetti <hgrandinetti@chromium.org> Cr-Commit-Position: refs/heads/master@{#638605}
-
Roger Tawa authored
Bug: 938974 Change-Id: I9fa64579b8dcaf5e0434383c6068ff83a607ef65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506393 Commit-Queue: Roger Tawa <rogerta@chromium.org> Reviewed-by:
Tien Mai <tienmai@chromium.org> Cr-Commit-Position: refs/heads/master@{#638604}
-
Peter Kotwicz authored
This CL switches DownloadMediaParserTest from using BaseJUnit4ClassRunner to using ChromeJUnit4ClassRunner. because ChromeJUnit4ClassRunner knows about UiRestriction.RESTRICTION_TYPE_PHONE BUG=939218 Change-Id: Iea95b4c088d9447664e569d1cee616b2c4d89038 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1507396Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Cr-Commit-Position: refs/heads/master@{#638603}
-
Sylvain Defresne authored
Change client code to work as if IdentityManager::GetPrimaryAccount where returning a CoreAccountInfo instead of an AccountInfo. Method will be updated in a followup CL. This CL was uploaded by git cl split. Bug: 926204 Change-Id: I7ed54720bb93c83df6802f83034138f71bb8e479 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1499515 Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Thomas Tangl <tangltom@chromium.org> Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#638602}
-
Xianzhu Wang authored
- Fix DCHECK: is_running_xxx_animation_on_compositor should not be set in non-BGPT mode. The DCHECK is to check if the flag is set, we must have CompositingReason::kActiveXXXAnimation in direct_compositing_reasons (which is not set in non-BGPT). - Add virtual/disable-blink-gen-property-trees/animations to avoid regressions in non-BGPT mode when we make animation changes. The virtual suite is run with --enable-threaded-compositing which is closer to real world. Bug: 836884 Change-Id: I2f88db3423a9938cb55ce91244735b3881d31a7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1507044 Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#638601}
-
Stephane Zermatten authored
This change disallows tab-switching unless the experiment AutofillAssistantChromeEntry is enabled, as Autofill Assistant normally doesn't need it. Before this change, it was possible to take Autofill Assistant out of the Chrome Custom tab by choosing "Open in Chrome". It was possible to have more than one tab open on Chrome Custom Tab without breaking Autofill Assistant. With this change, Autofill Assistant turns itself off when choosing "Open in Chrome" and enters an error when a new tab is opened in Chrome Custom Tab, like M73 does. Bug: 925947, b/125738726 Change-Id: I39fc8aecf4479183d6c115c775b13bb218590f57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1507658 Commit-Queue: Stephane Zermatten <szermatt@chromium.org> Reviewed-by:
Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#638600}
-
Brian White authored
Change-Id: Ibc22fe9f59e7a5cd79b2e4a3a3de08f445c15812 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1489179 Auto-Submit: Brian White <bcwhite@chromium.org> Commit-Queue: Brian White <bcwhite@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#638599}
-
kylechar authored
CompositorOverlayCandidateValidatorOzone took a string that was really a comma separated list of overlay strategies. The string was parsed into a list of callbacks that were later used to create the appropriate strategy objects. This CL changes CompositorOverlayCandidateValidatorOzone to take a list of OverlayStrategy enums instead. The enum already existed for UMA and it contains an entry for each overlay strategy. Use the list of enum values to directly instantiate the strategy objects, saving a layer indirection. Move the enum to //components/viz/common so it can be used with IPC later. Also move the code to parse a string containing a comma separated list of strategies, as this is used by the --enable-hardware-overlays flag. Bug: 930173 Change-Id: Ie5d6d501e3117cf4be0fcf29ac8bdf29744041da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1505839Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#638598}
-
Brian White authored
Bug: 923083 Change-Id: I62679448e96ea016d73b2e7c4d955b3a514d2be6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1496312 Commit-Queue: Brian White <bcwhite@chromium.org> Auto-Submit: Brian White <bcwhite@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#638597}
-
Bruce Dawson authored
This reverts commit d17a7e3c. Reason for revert: Increase in heap corruption (and other?) crashes in the d3dcompiler code path, such as crbug.com/932359. We have run out of time to investigate before branching. Original change's description: > Switch to full 17763 SDK, including new d3dcompiler_47.dll > > The new (10.0.17763.0) version of d3dcompiler_47.dll contains various > bug fixes which we want to ship. We initially avoided upgrading it with > the rest of the SDK because it depends on the universal Windows 10 CRT > (UCRT) which some Windows 7 machines lack. This caused test failures on > some bots and would cause failures on some customer machines. > > This change updates how we package isolates so that they always include > the UCRT, to avoid test failures. It also ships api-ms-win-*.dll and > ucrtbase*.dll in mini_installer.exe so that the UCRT will be shipped to > customers. The size increase to mini_installer.exe for this is about > 400,000 bytes. > > This change also deletes an unused function (_read_configuration_from_gn) > from create_installer_archive.py that sent me down an incorrect path > while investigating fixes. > > The toolchain package is the same as the one used when landing > crrev.com/c/1401403 except that the 17763 version of d3dcompiler_47.dll > was retained. See that CL for full instructions on creating the > toolchain package. > > Bug: 920704 > Change-Id: I9cb7a7ed5cb75d04962fc64869d26b12617c0463 > Reviewed-on: https://chromium-review.googlesource.com/c/1450414 > Reviewed-by: Greg Thompson <grt@chromium.org> > Commit-Queue: Bruce Dawson <brucedawson@chromium.org> > Cr-Commit-Position: refs/heads/master@{#629193} TBR=brucedawson@chromium.org,grt@chromium.org Bug: 920704 Change-Id: Ia986017541e5e80a3cc5f1d96494e0e12a841ed1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1507040Reviewed-by:
Jamie Madill <jmadill@chromium.org> Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#638596}
-
Elly Fong-Jones authored
This change removes the sound-content-setting flag, the backing SoundContentSetting feature, and all logic referencing it. Bug: 896400 Change-Id: I80344ade50309df7c667d86477801106adfd3768 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1503619Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Tommy Steimel <steimel@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#638595}
-
Xiaocheng Hu authored
Our NG TextIterator didn't implement the EmitsSpaceForNbsp behavior. This patch implements it. Change-Id: I76e7531ee013494566c15417658042b012462690 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506972 Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#638594}
-
Dan Elphick authored
Replace deprecatiod Date::DateTimeConfigurationChangeNotification function with Isolate::DateTimeConfigurationChangeNotification. Bug: v8:8834 Change-Id: Iba2008d017d66d2ab27f952fe04b98597c2f86dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1507873 Auto-Submit: Dan Elphick <delphick@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#638593}
-
Devlin Cronin authored
Rather than using ObjectTemplateBuilder::SetProperty() on GinPort, use ObjectTemplateBuilder::SetLazyDataProperty(). This allows author script to reset the properties to be something else, which is more inline with the majority of JS objects exposed to scripts. Add tests for the same. Bug: 927887 Change-Id: I8f983918014d69941992423eece5fd1eed9c58e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506771Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#638592}
-
Daniel McArdle authored
Bug: 936989 Change-Id: I283cbb9f87e912c8094872a70c6abc193659cbe2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497198Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Daniel McArdle <dmcardle@chromium.org> Cr-Commit-Position: refs/heads/master@{#638591}
-
Aaron Tagliaboschi authored
Eventually that callback will have a call to send the blocked cookies to DevTools. For now, it just calls NotifiyHeadersComplete on the last call. I've also created a couple new private variables, including |cs_status_list_| so we can actually use the cookie strings and list when we want to without too much fuss. Bug: 856777 Change-Id: Ic71b1523ea244e4fbfd9cb16c07f716ba14448bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1479299Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Aaron Tagliaboschi <aarontag@chromium.org> Cr-Commit-Position: refs/heads/master@{#638590}
-
Richard Knoll authored
This adds a disabled by default flag for the notification trigger feature. It will be used by crrev.com/c/1477840 to guard the implementation. Bug: 891339 Change-Id: I7a11549b49bfcb56bafd5591de06d301de5c5b2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1505460 Commit-Queue: Richard Knoll <knollr@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Cr-Commit-Position: refs/heads/master@{#638589}
-
Findit authored
This reverts commit f451f9ea. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 638461 as the culprit for flakes in the build cycles as shown on: https://analysis.chromium.org/p/chromium/flake-portal/analysis/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vZjQ1MWY5ZWFmMWI2ZDY3YjYyYmRmZmExODY4MTY4MTQ2ZmVmMGIwYgw Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/11234 Sample Failed Step: browser_tests Sample Flaky Test: MyFiles/FilesAppBrowserTest.Test/myFilesExpandWhenSelected_MyFilesVolume Original change's description: > [Files app] Fix MyFiles expanding when isn't selected > > Fix My files expanding when selecting or expanding entries in other > roots. > > Change-Id: I5c87f371ef500608100b6e07ae118f84e71f0311 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1505744 > Commit-Queue: Luciano Pacheco <lucmult@chromium.org> > Auto-Submit: Luciano Pacheco <lucmult@chromium.org> > Reviewed-by: Alex Danilo <adanilo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#638461} Change-Id: I7458e4afb3b695c42df45fc0dd3a1aa8e214eb1e No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508697 Cr-Commit-Position: refs/heads/master@{#638588}
-
Yuke Liao authored
This reverts commit cdc92f96. Reason for revert: Since the other one was reverted: https://chromium-review.googlesource.com/c/chromium/src/+/1508457 Original change's description: > Reland "Adding an exclusion list to the coverage wrapper script." > > This is a reland of 6b7213a4 > > Original change's description: > > Adding an exclusion list to the coverage wrapper script. > > > > The script now assumes GN adds coverage flags to the cflags for each > > source file. The script removes the flag if the file is in an exclusion > > list, or if `--files-to-instrument` is set it will also remove flags if > > the file is not listed in that argument. > > > > The script supports multiple exclusion lists that can be selected with > > the `--target-os` flag. > > > > It's expected that GN will set these flags correctly and invoke the > > script in all coverage builds. http://crrev.com/c/1496002 does that. > > > > > > Bug: 918215 > > Change-Id: I4454f67067a083581f31a22cfef85368825789f9 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1495994 > > Commit-Queue: Sajjad Mirza <sajjadm@google.com> > > Reviewed-by: Max Moroz <mmoroz@chromium.org> > > Reviewed-by: Yuke Liao <liaoyuke@chromium.org> > > Reviewed-by: Roberto Carrillo <robertocn@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#637892} > > Bug: 918215 > Change-Id: I1254d288ff263ff94c46b46e6be99738e31b9574 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506974 > Reviewed-by: Yuke Liao <liaoyuke@chromium.org> > Reviewed-by: Max Moroz <mmoroz@chromium.org> > Commit-Queue: Sajjad Mirza <sajjadm@google.com> > Cr-Commit-Position: refs/heads/master@{#638362} TBR=stgao@chromium.org,robertocn@chromium.org,mmoroz@chromium.org,liaoyuke@chromium.org,sajjadm@google.com Change-Id: I43834e520ccadd680217e80fc6ca40a210684b3c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 918215 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508597Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#638587}
-
Dave Tapuska authored
Chrome currently fails these tests and it will be enabled in a followup patch. The intent of this change is to add the wpt tests and bring the code closer to the proposed specification. BUG=348877 Change-Id: Ie9894c588b2cfe040be97905617b05c5b49fc4f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1479576 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#638586}
-
Tanja Gornak authored
Currently fcm channel and subscription to topics use same enum in order to track their state. This Cl introduces separate enum for the Subscription channel state tracking. Bug: 801985, 878446 Change-Id: If5a4781fdd2e12b8d94245375a1480e237248321 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1505441Reviewed-by:
Tatiana Gornak <melandory@chromium.org> Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Commit-Queue: Tatiana Gornak <melandory@chromium.org> Cr-Commit-Position: refs/heads/master@{#638585}
-
behdad authored
Bug: chromium:938514 Change-Id: I85231184360c8040f5bd78d0775aa634452de25b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1504044 Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#638584}
-
Monica Salama authored
Log native code's resident pages. Use the data for visualization and analysis. This work will help in assessing code ordering and will give insight on how to improve it. Bug: 933377 Change-Id: If93f7c07f74111e5a5bb50567453cc9b202219df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1482976 Commit-Queue: Monica Salama <msalama@google.com> Reviewed-by:
Hector Dearman <hjd@chromium.org> Reviewed-by:
Benoit L <lizeb@chromium.org> Cr-Commit-Position: refs/heads/master@{#638583}
-
Marc Treib authored
Previously, the auth error handling logic existed twice, depending on whether the initial setup was finished or not. This CL deduplicates the code. This causes two small behavior differences: 1) Before, a TWO_FACTOR auth error was treated as "okay" if first-time setup was incomplete, but treated as an error otherwise. That just seems like an oversight. 2) Before, if there was an auth error while we were also missing the Sync confirmation, we'd show a "missing confirmation" message. Now we'll show "auth error" instead. This CL also relaxes the nullable-restrictions on output params: |status_label|, |link_label| and |action_type| can now all independently be null or not. Bug: 911153 Change-Id: Ic2e5174c2596114725f6816d4f385ebf5c50ece6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1507872 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#638582}
-
Ben Kelly authored
Previously the Response mime type was never set when reading from a Cache. This resulted in empty string blob.type values and could also prevent code cache from being generated if a script Response was put back into a Cache. This CL makes us at least generate a mime type from the current content-type header. This is a partial solution since the mime type should technically be frozen at initial Response construction time even if the content-type header is later changed. To support that we will need to explicitly store a mime type on disk in the cache. This will be done later in crbug.com/938939. Bug: 937963,938939 Change-Id: Iabfe3909ff35957501ef33132af2a0c1f70c5c94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506213 Commit-Queue: Ben Kelly <wanderview@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#638581}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/141e92bdd2cc..5b257f91fc81 Created with: gclient setdep -r src-internal@5b257f91fc81 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome BUG=chromium:939049 TBR=hkamila@chromium.org,robliao@chromium.org,etiennep@chromium.org Change-Id: Iecfb3aaee8590497b26d22ddfce778b75dcab986 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508556Reviewed-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@{#638580}
-
Anna Malova authored
When loading a dynamic module from dex we need to create ClassLoader in advance as part of warmup without loading a module. See also: http://crrev.com/c/1479331 Bug: 924118 Change-Id: Ib7e7250eec8fe9c7f2ce27abe1c031f6dec8d270 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506513 Commit-Queue: Anna Malova <amalova@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Reviewed-by:
Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Cr-Commit-Position: refs/heads/master@{#638579}
-
Tamer Tas authored
This CL creates the src side configuration for a V8 waterfall bot. R=machenbach@chromium.org CC=yangguo@chromium.org,sergiyb@chromium.org No-Try: true Bug: 883629 Change-Id: Ia3afccfd8aff1035d0ac0c5ac425d951f0f20c14 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508514 Commit-Queue: Tamer Tas <tmrts@chromium.org> Auto-Submit: Tamer Tas <tmrts@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#638578}
-
Marc Treib authored
This adds a bit more detail on most model types, and removes comments for deprecated types. Bug: none Change-Id: Ia5434dc89e91a9572a25793ccc9bf8e905723463 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506075 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#638577}
-
Lowell Manners authored
This CL merges OnRequestCompleted's logic into OnTokenRequestCompleted. There wasn't enough logic to warrant a separate method. Bug: 933109 Change-Id: I2074518187f6078ae2d5c22935aa8a4e911837fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1505498 Commit-Queue: Lowell Manners <lowell@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#638576}
-
Sigurdur Asgeirsson authored
As of https://chromium-review.googlesource.com/c/1425042, content/ no longer provides forwarding for the ResourceCoordinator instrumentation interfaces. This was a step in a larger refactoring, but had the effect of orphaning the instrumentation in all but the chrome/browser embedder. This in turn led to a memory regression in the Android WebView. This CL makes the initialization and the usage of the instrumentation interfaces conditional on a runtime flag, which is only set by the ChromeContentRendererClient. This is still an intermediate state in the refactoring, as the interfaces in question will be moved and simplified. Bug: 926426 Change-Id: Ia640f544b536bf86d53e853de6178aeaf9c9b6f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1496303 Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Stephen White <senorblanco@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#638575}
-
dstockwell authored
* Adjusts size/location of icons and focus/hover/active states. * Makes viewer-toolbar-dropdown use a single paper-button to avoid overlapping focus/ripple. * Removes focus when a dropdown is cancelled by pointer events. Spec: go/pdf-icon-states-spec Impl: go/pdf-icon-states-impl Bug: 902646 Change-Id: If3bee9f86c8fa9f50537c8ff3cc4e3a9011172eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508014 Commit-Queue: dstockwell <dstockwell@chromium.org> Commit-Queue: dsinclair <dsinclair@chromium.org> Reviewed-by:
dsinclair <dsinclair@chromium.org> Auto-Submit: dstockwell <dstockwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#638574}
-
Elly Fong-Jones authored
This flag (& the code it guards) will be dead by the end of 2020, so around M88. Bug: None Change-Id: Icece1bf07e1d4c7976f68054a156cc0daf50b50f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1505993 Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#638573}
-