- 20 Dec, 2019 16 commits
-
-
Avery Musbach authored
You shall be able to start dragging a window (not from overview), drag from one display to another, and snap. Also, WorkspaceWindowResizer shall meet the expectation documented in Issue 995413. Fixed: 986870 Bug: 995413 Change-Id: I7835c3762486c73fc9ab04a04f14d693e442f2ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972170 Commit-Queue: Avery Musbach <amusbach@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Cr-Commit-Position: refs/heads/master@{#726619}
-
Lucas Gadani authored
headers in the browser process. Bug: 759184 Change-Id: Iefb33fa8ec2264f3e224d5a3ab92417160848fdf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958692Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Lucas Gadani <lfg@chromium.org> Cr-Commit-Position: refs/heads/master@{#726618}
-
James Cook authored
SplitSettingsSync changes Chrome OS settings to use a new URL for the sync config sub-page (chrome://os-settings/osSync). Change IsOSSettingsSubPage() to return false for "syncSetup", which will allow future CLs to call chrome::ShowSettingsSubpage(kSyncSetupSubPage) to open the browser sync settings. Bug: 1013466 Change-Id: Ica4fd4dc87befe402907f3ecbacb370655414401 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977139Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#726617}
-
Bettina authored
The string had an "and" that wasn't needed and instead needed a "," in between the two domains. Bug: 1035811 Change-Id: Icc7e307389005f9860d1012bec050411c015de65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976853Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Commit-Queue: Bettina Dea <bdea@chromium.org> Cr-Commit-Position: refs/heads/master@{#726616}
-
chrome://extensionsArchana Simha authored
Bug: 986368 Change-Id: I2fe3a93d911bfac94f04ba62863bf80fad830514 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1924724 Commit-Queue: Archana Simha <archanasimha@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#726615}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/750660e15c3c..6d29348ddb7e git log 750660e15c3c..6d29348ddb7e --date=short --first-parent --format='%ad %ae %s' 2019-12-19 sugoi@google.com Enable filtering depth only formats Created with: gclient setdep -r src/third_party/swiftshader@6d29348ddb7e If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@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_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I3d99f51c92eae7094c9c9d06dc1cb8ce2f2ccc29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976918Reviewed-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@{#726614}
-
Jiawei Shao authored
This patch adds all BC formats to Blink so that they can be used when the extension "textureCompressionBC" is enabled. BUG=chromium:996713 Change-Id: Ic35e9b6570d12273d09c8e688718509b4a88999a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975299Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Reviewed-by:
Austin Eng <enga@chromium.org> Commit-Queue: Jiawei Shao <jiawei.shao@intel.com> Cr-Commit-Position: refs/heads/master@{#726613}
-
Alan Cutter authored
Change-Id: Ibf17313912ad4ce5f0b41cb1b9032dc70ec16690 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971291 Auto-Submit: Alan Cutter <alancutter@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Commit-Queue: Alan Cutter <alancutter@chromium.org> Cr-Commit-Position: refs/heads/master@{#726612}
-
Victor Costan authored
Change-Id: I51596508f1db19f83dee2234b14f9f1a52a87b8a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975152 Commit-Queue: Jarryd Goodman <jarrydg@chromium.org> Auto-Submit: Victor Costan <pwnall@chromium.org> Reviewed-by:
Jarryd Goodman <jarrydg@chromium.org> Cr-Commit-Position: refs/heads/master@{#726611}
-
Nate Fischer authored
The WebViewClientTest#testOnSafeBrowsingHit() is flaky due to a subtle timing change when we switched to Network Service. This disables the test for now, while we look for a fix. This test was added in OMR1 (which we don't run CTS tests for in chromium waterfall), so we don't need to do anything for earlier API levels. The flaky part of the test was split out into testOnSafeBrowsingHitBackToSafety in Q, which we're already skipping in the JSON config. Bug: 1006953 Test: android_webview/tools/run_cts.py (on P device) Change-Id: I2c3e197484b1678722573ee052aed83150148417 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975156 Auto-Submit: Nate Fischer <ntfschr@chromium.org> Commit-Queue: Andrew Luo <aluo@chromium.org> Reviewed-by:
Andrew Luo <aluo@chromium.org> Cr-Commit-Position: refs/heads/master@{#726610}
-
Sajjad Mirza authored
Add definitions for tester machines for Windows coverage. Add buildbot definitions so the tryjob can run tests. Bug: 1033753 Change-Id: I3d933b1beaedd24ad206c9e5d2528ed5e4496b67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972753Reviewed-by:
Nodir Turakulov <nodir@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Commit-Queue: Sajjad Mirza <sajjadm@chromium.org> Cr-Commit-Position: refs/heads/master@{#726609}
-
Xiaoqian Dai authored
To be consistent with the name of other WindowResizers. Bug: None Change-Id: I557b3beb6840fe60bd960490e1cf324bc910eeee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977184Reviewed-by:
-
Emily Stark authored
Currently, all cert error decisions (i.e., when a user clicks through a certificate error) are stored in ContentSettings, associated with a Profile. This means that if a user clicks through a certificate error in a <webview> in a Chrome App, that decisions propagates to normal browsing. Persisting decisions within a <webview> is undesirable on its own (because there's no UI to remind the user that they've done so and to allow them to revoke the decision), and it's especially undesirable for that decision to affect normal browsing. Therefore, this CL isolates cert error decisions by storage partition. Decisions made for the default storage partition are remembered in the normal way (ContentSettings for the Profile); decisions for other storage partitions are remembered in memory only. Bug: 639173 Change-Id: If1cca181c80f8d07f5411fbb0d3707cf3755c5a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974698Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/1ba8de1a..7f890a8e Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I334028b5c8bab641c3dd635e429006b3c3bec86b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977279Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#726606}
-
Darwin Huang authored
Bug: 1035371, 1034695 Change-Id: Ia845e059d69417bcccf3f9ad6982d4df94fe5b86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975290Reviewed-by:
Chris Mumford <cmumford@google.com> Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#726605}
-
sczs authored
- Adds verifyFolderExists to BookmarkEarlGrey and its AppInterface. - Adds ScrollToTop to ChromeActions to be used on Bookmark Folder test. - Deletes BookmarkEarlGreyUtils since its no longer used. Change-Id: Ia1eeb07bcfa80f03e263c49d4f89b2592c338903 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976490 Commit-Queue: Sergio Collazos <sczs@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#726604}
-
- 19 Dec, 2019 24 commits
-
-
Miguel Casas authored
This CL adds 4K resolution to the Fake Video Capture Device, a.k.a. the rolling pacman. TEST= unittests and ./out/desktop/chrome --use-fake-device-for-media-stream https://codepen.io/miguelao/full/bGNgOYq Bug: 1010457 Change-Id: Ibcab5e83a8bb09dbf4f1e6866951f1ccb9e41f41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974995 Commit-Queue: Miguel Casas <mcasas@chromium.org> Auto-Submit: Miguel Casas <mcasas@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/master@{#726603}
-
Kai Ninomiya authored
Using the "SafeEjectGPU" tool, we can see that when the "responsible" process (the browser process) has a GPUEjectPolicy of 'wait', any subordinates using the GPU (i.e. the GPU process) get the 'rwait' GPUEjectPolicy: "Eject actions apply to the responsible process, who in turn deals with subordinates to eliminate their ejecting eGPU references." [man 8 SafeEjectGPU] Empirically, the browser does not relaunch. Once the GPU process exits, it appears that the browser process is no longer considered to be using the GPU, so it "succeeds" the "wait". Documentation: https://developer.apple.com/documentation/metal/gpu_selection_in_macos/handling_external_gpu_additions_and_removals Change-Id: Ia44c2ed864d1bdbb52d82ad72e14cbfcb4e32108 Bug: 1035619 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974856Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org> Cr-Commit-Position: refs/heads/master@{#726602}
-
Manas Verma authored
Bug: 949269 Change-Id: I914b20bc5532a4df59120f6954235b1a5daa9013 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977185Reviewed-by:
Jared Saul <jsaul@google.com> Commit-Queue: Manas Verma <manasverma@google.com> Cr-Commit-Position: refs/heads/master@{#726601}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5acad7aa14e2..330a8816909a Created with: gclient setdep -r src-internal@330a8816909a 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 Bug: chromium:1029520,chromium:984162 Tbr: jbudorick@google.com Change-Id: I12e810a1d1e6fb72bf726936dc6ee9b9112b7e15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977080Reviewed-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@{#726600}
-
Alexey Baskakov authored
Observe OnWebAppWillBeUninstalled instead of OnWebAppUninstalled. It's too late to obtain the app pointer from the registrar after a web app uninstall (deletion) happened. Bug: 1029221 Change-Id: I7794ed4fa7ed52ac396949eed88bd4514ed2154a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975473Reviewed-by:
Nancy Wang <nancylingwang@chromium.org> Commit-Queue: Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#726599}
-
David Bokan authored
ScrollBy currently has some logic to check the |current_native_scrolling_element| and use that rather than the CurrentlyScrollingNode. This allows the currently scrolling node to be changed mid-gesture, even though this should never happen. The goal we're aiming for is that every scroll gesture should follow this sequence: ScrollBegin - select the scroller and "latch" it ScrollUpdate - * * * ScrollEnd - release the scroller i.e. "unlatch" it Between begin and end, there should be no modification of the latched scroller. This CL removes the mid-gesture uses of |current_native_scrolling_element|. After this CL, this member of the scroll state is only valid when passed into ScrollBegin where it can be used to specify the scroller that should be scrolled. A future CL will rename this member for clarity. Bug: 1016229 Change-Id: I7a8b24795990623dd27c471f05d06481ff05e147 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1953331 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#726598}
-
behdad authored
The experimental percentage of representative perf tests increased from 25% to 100% Bug: chromium:1000837 Change-Id: I9d86c3358bcfe8a05d29896453dd0e9154c2f45c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976191 Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Reviewed-by:
-
Yuke Liao authored
Due to crbug.com/1034002, linux-code-coverage fails frequently with an infra failure at the step of collecting results for weblayer_browsertests, so this CL removes the offending target for now. Bug: 1016929, 1034002 Change-Id: I41fd82097ff55bf3a84ec9d139e1a3f22894fc3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977021Reviewed-by:
-
Clark DuVall authored
Switches all test to ContentJUnit4ClassRunner since it already has the @CommandLine.Flags parsing bits set up. This also removes a sleep that was added because we couldn't pass command line args before. Change-Id: Ic7e63c31e24d540af0bbf1dda58e800319a1d844 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975075 Commit-Queue: Clark DuVall <cduvall@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#726595}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/e6d31bd0894c..6e6b4dd7d3e2 git log e6d31bd0894c..6e6b4dd7d3e2 --date=short --first-parent --format='%ad %ae %s' 2019-12-19 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2019-12-19 jvanverth@google.com Revert "Generate small path SDFs directly from path." 2019-12-19 jvanverth@google.com Generate small path SDFs directly from path. 2019-12-19 bsalomon@google.com Revert "Revert "Blend functions as SkSL built ins."" 2019-12-19 reed@google.com Revert "temporarily expose postIDiv" 2019-12-19 jvanverth@google.com Add wireframe support to Metal. Created with: gclient setdep -r src/third_party/skia@6e6b4dd7d3e2 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 borenet@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 Bug: None Tbr: borenet@google.com Change-Id: I1ab721b51199c34fb8fd762c1ea77ec936ef729d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976881Reviewed-by:
-
Aga Wronska authored
Detailed app activity information are needed by Per-App Time Limits feature. Bug: 1015656 Change-Id: Ibb0a59067a9d9d01adc5b02a1e6fc59ca8fec681 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970855Reviewed-by:
Henrique Grandinetti <hgrandinetti@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Reviewed-by:
Pavol Marko <pmarko@chromium.org> Commit-Queue: Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#726593}
-
Lu Huang authored
The pwa install icon should not be visible when the user is adding input to the omnibox. http://crrev.com/c/1933852 made this the default behavior for all page action icons. This change adds a specific test for the PwaInstallView icon view. Bug: 969902 Change-Id: I6cd4fa495f70fefaf228771a2d8fd706e88f88e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975155Reviewed-by:
Alan Cutter <alancutter@chromium.org> Reviewed-by:
Lorne Mitchell <lomitch@microsoft.com> Commit-Queue: Lorne Mitchell <lomitch@microsoft.com> Cr-Commit-Position: refs/heads/master@{#726592}
-
Mason Freed authored
In the (corner) case that the <iframe> src attribute is relative to a data URL, the previous behavior was to silently fail. With this CL, there is now a console message indicating what happened. Example: <iframe id="i"></iframe> <script> let html = `<iframe src="resource.html"></iframe>`; i.src = `data:text/html,${encodeURIComponent(html)}` </script> Bug: 1033313 Change-Id: Ie164edaacd2d92ea2bebc89419782e9204cdf410 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972493 Commit-Queue: Mason Freed <masonfreed@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:Kent Tamura <tkent@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#726591}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/5217ad51c521..d28b578b6b09 git log 5217ad51c521..d28b578b6b09 --date=short --first-parent --format='%ad %ae %s' 2019-12-19 yunchao.he@intel.com Disallow storage buffer binding in vertex shader 2019-12-19 enga@chromium.org fuzzing: Add Vulkan backend fuzzer Created with: gclient setdep -r src/third_party/dawn@d28b578b6b09 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: cwallez@google.com Change-Id: I2d4e14e934b49523773b2d9ac8dd85c27eb6e365 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977119Reviewed-by:
-
Clark DuVall authored
This will allow testing WebView/WebLayer behavior when using a bundle, and will help investigate any issues that can happen. Bug: 1033098 Change-Id: Id88c128d5dd555ccb188a172d52dcb49ee373af9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1962899Reviewed-by:
Richard Coles <torne@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#726589}
-
Brian Norris authored
<meme>Why do we even have that lever?</meme> (Maybe just a holdover of the Flimflam API?) Shill never has (and most likely never will do so) managed Bluetooth devices. I plan to drop this (unimplemented) definition from system_api and stop documenting it in the Shill docs (https://crrev.com/c/1976962), so Chrome should stop using it. Bug: none Change-Id: I6c868fb05add97da800e39e7c32add5b8e9a1c14 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977140Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Brian Norris <briannorris@chromium.org> Cr-Commit-Position: refs/heads/master@{#726588}
-
Ilia Samsonov authored
googletest will no longer support empty prefix for parameterized INSTANTIATE_TEST_SUITE_P. Adding "All" prefix to existing empty prefix test suites. This CL was uploaded by git cl split. R=ericorth@chromium.org Bug: 1023677 Change-Id: Ic527ff1a7cb4654e17df53ba36a3da314187de17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1957495 Auto-Submit: Ilia Samsonov <isamsonov@google.com> Reviewed-by:
Eric Orth <ericorth@chromium.org> Commit-Queue: Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#726587}
-
Kramer Ge authored
OS API creates vulkan swapchain images as render targets. Estimate the allocated GPU resource with vkGetImageMemoryRequirements. Bug: 899905 Change-Id: I162ab641c3e13a10fa29e8e8860dee06b2598a79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967552Reviewed-by:
Peng Huang <penghuang@chromium.org> Commit-Queue: Kramer Ge <fangzhoug@chromium.org> Cr-Commit-Position: refs/heads/master@{#726586}
-
Aran Gilman authored
ExecuteJsScript() is used only once in this CL but will be used in new tests added by https://crrev.com/c/1922788. This CL also runs clang-format on pinch_tester.js and modifies it to return a bool instead of a dict. The latter simplifies verification of script execution in the C++ portion of the test. Bug: 1016615 Change-Id: I2c847eb53556a30e991d988fb676c6a3fa5aee8a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971702 Commit-Queue: Aran Gilman <gilmanmh@google.com> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#726585}
-
Michael Thiessen authored
Split off of https://chromium-review.googlesource.com/c/chromium/src/+/1901591 The motivation here is to make get rid of the memcpy and leaked ptr in DoAddSchemeWithType to make the code more readable. Also DCHECKs that schemes aren't locked when calling EnableNonStandardSchemesForAndroidWebView. Bug: 783819 Change-Id: I959d364fd0572a3c09c68ab75e48f46809f8dbc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974759 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
-
Ahmed Mehfooz authored
Bug: 1021133 Change-Id: Ic7cbf25c094006efd970c75dff2b733b31620bc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974599 Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org> Reviewed-by:
Tim Song <tengs@chromium.org> Cr-Commit-Position: refs/heads/master@{#726583}
-
Ella Ge authored
To support replay input events (crrev.com/c/1944333). This CL adds input event's detail information (coordinates, modifiers, button to trace data, when "devtools.timeline.inputs" category is enabled. Change-Id: I73cad86a9922e0a7b494ac0a01f8817e53cf7e26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943179Reviewed-by:
Mathias Bynens <mathias@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#726582}
-
Aaron Leventhal authored
Make sure even if painting returns early, that accessibility focus is still updated. Bug: 820351 Change-Id: I4d712742b9677095cdcf19d486945c892b73a11c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976071 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Reviewed-by:
-
Oksana Zhuravlova authored
This change addresses the crash in TextSuggestionHostMojoImplAndroid::StartSuggestionMenuTimer() if text_suggestion_host_ is null. TextSuggestionHostMojoImplAndroid is now not created if a TextSuggestionHost has not been set for the corresponding RenderWidgetHostViewAndroid. Bug: 1034125 Change-Id: Ia21fba5e6d486637715743d33e65d2fcccc86c43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976829Reviewed-by:
Tom Sepez <tsepez@chromium.org> Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#726580}
-
