- 15 Nov, 2019 40 commits
-
-
David Tseng authored
This change is mostly mecanical though it does contain some cleanup of ChromeVox Classic logic. It is a prerequisite to modernization of ChromeVox sources. A taste of what the modern ChromeVox looks like is here: https://chromium-review.googlesource.com/c/chromium/src/+/1917948/1 In addition, this will eventually allow for extraction of a shared accessibility module, harvesting useful pieces of ChromeVox for other accessibility component extensions. Bug: none Test: manual and browser_tests. Change-Id: I1fc3198ce9fac8f96d9b7fd0f829cc3be4848bd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918325Reviewed-by:
Anastasia Helfinstein <anastasi@google.com> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#715904}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/77c16a79405b..0db19efecac9 Created with: gclient setdep -r src-internal@0db19efecac9 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: I930144772cd28dc55e028ced76e299fdb4c2ffb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918665Reviewed-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@{#715903}
-
Pavel Yatsuk authored
BUG=1023566 Change-Id: Ie4ea9b81a70f5a383a2b5f486919d9a17cd909c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1917467 Commit-Queue: Pavel Yatsuk <pavely@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Cr-Commit-Position: refs/heads/master@{#715902}
-
Greg Thompson authored
This change introduces RelaunchIgnoreUnloadHandlers and uses it in RelaunchNotificationController when the deadline for a forced relaunch is reached. This new function is to AttemptRelaunch as ExitIgnoreUnloadHandlers is to AttemptExit. This also introduces browser_shutdown::ShouldIgnoreUnloadHandlers(), which is a convenience for code that needs to know whether or not an in-progress shutdown should ignore unload handlers. BUG=958865 Change-Id: I91a9832d745e95b7436b176d78f5e39ed14addd2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1914380 Commit-Queue: Greg Thompson <grt@chromium.org> Auto-Submit: Greg Thompson <grt@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#715901}
-
Manu Cornet authored
The shelf layout manager currently calculates and sets the bounds of all the shelf-related widgets (navigation, hotseat, status area). The bound calculation logic should remain in this class, but the actual setting of the bounds and managing animations can be done by each widget at their leisure without requiring a full relayout of all other widgets. For that to happen, the shelf layout manager can be the central place from which widgets can ask their target bounds, but they can then be responsible for setting them themselves at their own pace. This CL makes the target bounds a field so that other classes can query them at any time (through getters that will be added subsequently as other classes need them). This has no expected user-visible effect. Bug: 1021698 Change-Id: I6214d21315aec42e01d44f9f8ace4b041e970704 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919603Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Commit-Queue: Alex Newcomer <newcomer@chromium.org> Commit-Queue: Manu Cornet <manucornet@chromium.org> Cr-Commit-Position: refs/heads/master@{#715900}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/deae1fce2cc5..e4aa7235b859 git log deae1fce2cc5..e4aa7235b859 --date=short --no-merges --format='%ad %ae %s' 2019-11-15 timvp@google.com Vulkan: Update Expectations with GLES 3.1 Conformance Failures Created with: gclient setdep -r src/third_party/angle@e4aa7235b859 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC cnorthrop@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=cnorthrop@google.com Bug: None Change-Id: I65bc939c82ae31736d7e54fdae77520891bd9e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919576Reviewed-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@{#715899}
-
Chris Lu authored
Creates InfobarManagerAppInterface to allow for retrieval of InfobarManager state. Bug: 987646 Change-Id: Ic518fe7ffaaeec27b08f6a3e4a37a12dc84387fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1914535 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#715898}
-
chrome://flagsAlexander Timin authored
Fix chrome://flags behaviour for bfcache flag forcing caching: - Ensure that all parameters are correctly captured - Rename the mode to "Force caching all pages" to be more clear - Extend timeout to 1 hour for easier testing. R=carlscab@google.com Change-Id: I7df177abccea0fa849a5834c13b75464553c5cfb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919759 Commit-Queue: Alexander Timin <altimin@chromium.org> Reviewed-by:
Carlos Caballero <carlscab@google.com> Cr-Commit-Position: refs/heads/master@{#715897}
-
Anastasia Helfinstein authored
When the accessibility tree changes, events are fired on the automation API. This change updates the Switch Access tree when those events are received. Bug: 1023035 Change-Id: I88e208b8ed9d10653db2395dd4424194c3ef3248 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907550 Commit-Queue: Anastasia Helfinstein <anastasi@google.com> Auto-Submit: Anastasia Helfinstein <anastasi@google.com> Reviewed-by:
Akihiro Ota <akihiroota@chromium.org> Cr-Commit-Position: refs/heads/master@{#715896}
-
Brian Sheedy authored
Switches the win10_intel_hd_630_experimental mixin to trigger tests on driver version 26.20.100.7323. TBR=ynovikov@chromium.org Bug: 1016459 Change-Id: I68059fafe2ffd5b855f51b540ec4653ab40b9e54 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918386Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#715895}
-
Tina Wang authored
Bug: 1025369 Tbr: grt@chromium.org Change-Id: If745b038e44a67c9cd48ad3a3bd361f05e5ea811 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918348Reviewed-by:
Tina Wang <tinazwang@chromium.org> Commit-Queue: Tina Wang <tinazwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#715894}
-
Daniel Hosseinian authored
Place the functionality under the enable-custom-mac-paper-sizes feature flag. Bug: 1020350 Change-Id: Ia577351f33151446ef8864fd99e0301d5d13d5be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898946 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#715893}
-
Martin Kreichgauer authored
This default-enables FIDO2 fingerprint enrollment UI in chrome://settings/securityKeys Bug: 974046 Change-Id: I2c707943a10c588798b6704aa1416e246fe6d3e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1895310 Auto-Submit: Martin Kreichgauer <martinkr@google.com> Commit-Queue: Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/heads/master@{#715892}
-
Matt Wolenetz authored
Already disabled on WIN/MAC/CHROMEOS, these tests have been heavily flaky on various linux bots. This change fully disables these tests (a subset of the PreviewsLitePageRedirectServerTimeoutBrowserTests). TBR=tbansal@chromium.org BUG=1024824 Change-Id: I686c928b085677c267fc8298e6f9e756ad32bcff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919802Reviewed-by:
Matthew Wolenetz <wolenetz@chromium.org> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#715891}
-
Brian Sheedy authored
Marks monochrome_public_bundle_fake_modules_smoke_test as experimental since it currently does not work properly on component builds, which is blocking some CLs. Bug: 1025316 Change-Id: Ica40093e3b6134871a9aa04695343ed2344f20b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918271Reviewed-by:
Ben Pastene <bpastene@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#715890}
-
Kaan Alsan authored
Removing a snap container (i.e. making it unscrollable) should reassign its snap areas to the next scrollable ancestor. Bug: 1007456 Change-Id: Ic3ebea990a25a36020d278a33fb3c67dea708db6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899189Reviewed-by:
David Bokan <bokan@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Kaan Alsan <alsan@google.com> Cr-Commit-Position: refs/heads/master@{#715889}
-
Hitoshi Yoshida authored
We didn't have non readonly attributes that have [CachedAttribute], and unfortunately, generated code for that have problems. This CL fixes the compile errors found in non readonly [CachedAttribute] attributes. Bug: 715418, 1025322 Change-Id: I5cd42c94adaa552521bc1f734d5afcbc832a122a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919521 Auto-Submit: Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#715888}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/90c88f097366..46689b09c559 git log 90c88f097366..46689b09c559 --date=short --no-merges --format='%ad %ae %s' 2019-11-15 apolito@google.com Fix CMDUploadTestCase in presubmit Created with: gclient setdep -r src/third_party/depot_tools@46689b09c559 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@chromium.org 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=agable@chromium.org Bug: chromium:1025293 Change-Id: I6b3fa6ec46adc2674efa7a08d899672eb5fda77a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919701Reviewed-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@{#715887}
-
Ahmed Mehfooz authored
Bug: 1025313 Change-Id: I87631cc98eb6bb4e5dd11ba1a66bd3868c55865e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918269Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org> Cr-Commit-Position: refs/heads/master@{#715886}
-
Demetrios Papadopoulos authored
Most of these have been fixed automatically with ESLint's --fix flag. This is in preparation of turning on presubmit checks for no-var and prefer-const for components/. Bug: 792774,720034 Change-Id: I482ed8577bf260a6190fb646891194f8d533debc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1914496 Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#715885}
-
Kevin Marshall authored
Update README.md how-to docs to use the new `--fuchsia-out-dir` flag. Update the debugging how-to in README.md to incorporate improvements with Chromium package/symbol installation and the "fx debug" entrypoint. Change-Id: I95f99c37c5afedb06db5229eae820d06353b45cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913573 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by:
David Dorwin <ddorwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#715884}
-
Xiaoqian Dai authored
When dragging a window quickly up into the drag-to-snap split area, the overview windows are getting relayouted and while the animations are still going on, fling the window to homescreen. So OverviewItem::OnItemBoundsAnimationEnded() can be called when overview is in shutting down process, which should not happen. Bug: 1025267, 997885 Change-Id: Ia40f3fce589554672f2134f78ac4ddd8147d0910 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918834 Commit-Queue: Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#715883}
-
Sasha McIntosh authored
Add field trial entry for decoding JPEG 4:2:0 images to YUV. Bug: 919627 Change-Id: Ie8dc6378cccf27527da9ea05d060ba218fb69bdf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898548Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Sasha McIntosh <sashamcintosh@chromium.org> Cr-Commit-Position: refs/heads/master@{#715882}
-
Tina Wang authored
Bug: 1025291 Tbr: yangguo@chromium.org Change-Id: I5edde51c20744d4b0f69cd8b9fb31ab2ff604b98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918278 Commit-Queue: Tina Wang <tinazwang@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Tina Wang <tinazwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#715881}
-
Matt Wolenetz authored
BUG=1024850 TBR=adithyas@chromium.org,agrieve@chromium.org Change-Id: Ib99f9a64f4bea821efc5bab831233aa9e8928680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919726Reviewed-by:
Matthew Wolenetz <wolenetz@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#715880}
-
Jordy Greenblatt authored
The cr-link-row element is currently described by ChromeVox as a 'link' despite the fact when it is used as a subpage route, it stays in the current tab instead of opening a new one like the other links in settings. The alternative aria-roledescription 'subpage button' preferred by the a11y team remove that ambiguity. Examples: https://drive.google.com/open?id=1su58VJ_AksPs44HFoNWambjqcSLIQPdv Bug: 1012104 Change-Id: I7d591bb74b8b5828ca44e7270d7edf6ab61755c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1881816Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Commit-Queue: Jordy Greenblatt <jordynass@chromium.org> Cr-Commit-Position: refs/heads/master@{#715879}
-
Fabrice de Gans-Riberi authored
* Modify CastRunner to handle a CastAgent disconnection without crashing. * Add tests for this scenario. Bug: 1020736 Change-Id: If94cecc4a47a2aaf88d73b35df4e696f679a424e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1917981 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#715878}
-
Victor Hsieh authored
On device initialized before M74 (when boot lockbox was first introduced), it requires a powerwash first to use boot lockbox. In such case, disable the toggle and show sublabel to explain the situation. 1) still see login screen warning indicator 2) see settings toggle disabled, with a sublabel Test: Force to return NEED_POWERWASH from session_manager Test: No change if not forced Bug: chromium:893332 Change-Id: Idf75884404769ff724be0225aa9a674e03d978ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918335 Commit-Queue: Victor Hsieh <victorhsieh@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#715877}
-
Anastasia Helfinstein authored
TBR=dtseng@chromium.org Bug: 1025339 Change-Id: I2e9b14e9bd2b58f8c349081181c0b3ec1793f980 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919574Reviewed-by:
Anastasia Helfinstein <anastasi@google.com> Commit-Queue: Anastasia Helfinstein <anastasi@google.com> Cr-Commit-Position: refs/heads/master@{#715876}
-
Wez authored
StackTrace has a bug preventing it from capturing any stack frames in Fuchsia Official builds, so disable those checks for now. TBR=ajwong Bug: 1025329, 1025288 Change-Id: I2b24c7f903c345518835edc3226b15355ea1bf9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919735Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Commit-Queue: Wez <wez@chromium.org> Auto-Submit: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#715875}
-
Joon Ahn authored
Utilize gaia::IsGoogleInternalAccountEmail() instead of one off string checks. Bug: n/a Change-Id: I772ae92dbe31ca0c1bccc3c0e2fb666fa50972e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899843 Commit-Queue: Joon Ahn <joonbug@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#715874}
-
Tina Wang authored
Bug: 1025346 Tbr: afakhry@chromium.org Change-Id: I17616eb89ff17de0ad1839e5cb95f9d319281cc7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918384Reviewed-by:
Tina Wang <tinazwang@chromium.org> Commit-Queue: Tina Wang <tinazwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#715873}
-
Matt Menke authored
All calls are test-only, but there's a presubmit check for it that triggers even when it's used in tests. In its place, use base::NumberToString. BUG=None Change-Id: I617815c2d4fb254e52edf3c92c236c335ab73a26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919720Reviewed-by:
Asanka Herath <asanka@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#715872}
-
Xianzhu Wang authored
During device emulation, the chrome WebThemeEngine implementation may not be the mobile theme which can provide overlay scrollbar styles. In the case we should fallback to default styles. Bug: 1025183 Change-Id: I32b45d401e09374bf1da1967d2328867474b6cdd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919424Reviewed-by:
David Bokan <bokan@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#715871}
-
Andrew Xu authored
To solve the issue 1012772, we need to implement an interface to scroll the shelf view to show the icon for a given app id. This CL provides the following helper functions: (1) Calculates the offset distance of scrolling Shelf to the previous/next page. (2) Calculates the layout strategy for the given scroll distance. (3) Calculates the first/last tappable app indices for the given layout strategy and scroll offset. No UI changes should be introduced by this CL. Bug: 1012772 Change-Id: I3aa27d0fa035f9a9a3186bbe9963065afe465f89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762558Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Andrew Xu <andrewxu@chromium.org> Cr-Commit-Position: refs/heads/master@{#715870}
-
Fabrice de Gans-Riberi authored
* Remove no-longer implemented method definition in CastComponent * Remove the old API to register MessagePorts in CastRunner. * Remove integration and browser tests using former APIs. * Adapt integration and browser tests to use the new API. Bug: 953958 Change-Id: I192cd8453c3c730cb8ecab504884d46af5ad100b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1917327 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#715869}
-
Mikel Astiz authored
The test suite already instantiates a FieldTrialList as per https://chromium-review.googlesource.com/c/chromium/src/+/1883567 so it's no longer necessary to do so explicitly in tests. This patch addresses unit tests under: /chrome/browser/ui/search This CL was uploaded by git cl split. R=gayane@chromium.org Bug: 1018667 Change-Id: Icb63ab7435f32f6613a9dd06b551d6ebab960303 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1917508 Auto-Submit: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Gayane Petrosyan <gayane@chromium.org> Commit-Queue: Gayane Petrosyan <gayane@chromium.org> Cr-Commit-Position: refs/heads/master@{#715868}
-
Alex Ilin authored
This CL removes code that shares base::SharedMemoryHandle with remote. This code is no longer used because base::SharedMemoryHandle is deprecated and replaced with base::*SharedMemoryRegion. Bug: 795291 Change-Id: I5974bd77b6e40bee662dc2fb4092b7a61f725afb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1916827Reviewed-by:
Raymes Khoury <raymes@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: John Abd-El-Malek <jam@chromium.org> Auto-Submit: Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#715867}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 37619ed5. With Chromium commits locally applied on WPT: 788a3004 "Fix failing Fetch Metadata WPT" b16db925 "[Trusted Types] Add test for duplicate names in non-enforcing mode." e83dd93c "Limit backtracking on regexp called from blink." 6e3e930c "Change `sec-fetch-mode` from `no-cors` to `navigate` for <embed> / <object>." c8b6e1ce "Chromedriver] Fix PerformAction to support multi touch points cases" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=foolip No-Export: true Change-Id: If34822af50898fd25599053eaaf13d00506c6a04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1917049Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#715866}
-
Wez authored
DiscardableSharedMemory::Purge() attempts to proactively de-commit pages once the instance is unused, to free it quickly even if the peer is slow to unmap it. However, the DiscardableSharedMemoryManager (typically in the browser) maps instances but then closes their handles - Purge() must therefore be implemented without reference to the handle. Bug: 1023693 Change-Id: Ic645232c0b24d85acb64e915bbef05804b25b001 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912698 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Auto-Submit: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#715865}
-