- 23 Jan, 2020 40 commits
-
-
Mohamed Heikal authored
Bug: 1045024 Change-Id: Id5f37e284a97c6bb4a77341203df366f1d36ce32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017643Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Auto-Submit: Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#734639}
-
Avi Drissman authored
This changes expectations based on the macOS SDK used to build Chromium. Chromium has required newer than the 10.12 SDK for years, so remove this. Bug: 1044838 Change-Id: I41deec339d7da73392c410dbdb1439a824c0f81f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015361 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Auto-Submit: Avi Drissman <avi@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#734638}
-
Morten Stenshorne authored
Some tests in these virtual test suites were failing due to the form controls refresh (mostly; one of the failing tests was about a text layout difference between NG and non-NG [1]), but it doesn't seem worthwhile to run them (uninteresting combination of features), so rather than rebaselining, let's skip. [1] virtual/web-components-v0-disabled/fast/dom/HTMLMeterElement/meter-boundary-values.html R=ikilpatrick@chromium.org,masonfreed@chromium.org Change-Id: I499cbb69cf54969d6136b441e2ea95bdf5fcfe2b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016627Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Mason Freed <masonfreed@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#734637}
-
Toni Barzic authored
Fixes the histogram values for in-app hotseat gesture and swipe from home to overview gesture to match the values that are actually recorded: * Results of the in-app hotseat gestures are recorded as Ash.HotseatGesture, not Ash.HotseatInAppGesture as was specified in histograms.xml * Ash.SwipeHomeToOverviewGesture histogram reports an enum value, not a boolean Change-Id: Ie3d64d9727d2288071eb1a3fe52a451212a702be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015554 Commit-Queue: Toni Baržić <tbarzic@chromium.org> Reviewed-by:Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#734636}
-
Aaron Tagliaboschi authored
A fairly long overdue rework of the client hint WPTs. Most of the renaming is on it's own patchsets, so look through each one individually if there's too much to see anything useful. Tests deleted because of other coverage: * accept_ch.tentative.https.html: accept-ch-stickiness/same-origin-navigation.https.html * http_equiv_accept_ch.tentative.https.html: accept-ch-stickiness/http-equiv-same-origin-subresource.https.html * http_equiv_accept_ch.tentative.sub.https.html: accept-ch-change.https.html Bug: 1042828 Change-Id: Ie52abfac485b8e974f4a93a06f3d6d3b845a2010 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003338 Commit-Queue: Aaron Tagliaboschi <aarontag@chromium.org> Reviewed-by:Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#734635}
-
Simeon Anfinrud authored
The "data" list was pointing to a file that did not exist (the path omitted the "resources" prefix). Bug: Internal b/144577042 Test: check that each file from gn desc runtime_deps exists Change-Id: I2eb03db75cf3a8e7608d71446acfbf518074e00d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016907 Auto-Submit: Simeon Anfinrud <sanfin@chromium.org> Commit-Queue: Yuchen Liu <yucliu@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#734634}
-
Nate Chapin authored
This will make it easier to eventually not use SecurityContextInit in Document, and just use it for ExecutionContext/SecurityContext. Bug: 1029822 Change-Id: I6eb6c01756d2a9c3e28fe6e833bdd65e54acedb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015549Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#734633}
-
Brian Salomon authored
This will be used by Skia for async YUV420 readbacks with ES2 ANGLE contexts. Bug: 1040643 Change-Id: Ifcc0bff78efcf75764902e8a2910aea7266bf327 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015645Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: Brian Salomon <bsalomon@google.com> Auto-Submit: Brian Salomon <bsalomon@google.com> Cr-Commit-Position: refs/heads/master@{#734632}
-
Dale Curtis authored
Some loads are done from an in memory cache and won't trigger the typical mixed content warnings, so explicitly tell MixedContentChecker about our loads to ensure the proper notifications are generated. Fixed: 868145 Change-Id: I4df0ac3db1f2584c2ef44b5e3606acff314bc4ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008396 Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#734631}
-
Dominic Mazzoni authored
Android accessibility was using a different code path than other platforms to compute the bounding box of accessibility objects. In particular, we were ignoring the root scroll offset from the accessibility tree and using the offsets from RenderCoordinatesImpl instead. It looks like this is causing problems with ImplicitRootScroller, and furthermore it looks like this code is no longer necessary. Switching back to use the scroll offsets from the accessibility tree seems to fix the problem. A follow-up change will remove UseRootScrollOffsetsWhenComputingBounds entirely. This change is minimal in order to be considered for merging. Bug: 1005121 Change-Id: I82e97f046cee6b8b08238fcd4368228da368b92a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017662Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#734630}
-
Sylvain Defresne authored
The ChromeBrowserState has been moved from the "ios" namespace to the global namespace by http://crrev.com/c/2014913. Fix the uses from ios::ChromeBrowserState to ChromeBrowserState. Also remove includes of chrome_browser_state_forward.h and use a simple forward declaration instead (since the old name is no longer necessary). This CL was uploaded by git cl split. R=jlebel@chromium.org Bug: 1042208 Change-Id: I952ce3ca773ec0d693bd4aa31ff4526e55a29f87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017484 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Jérôme Lebel <jlebel@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#734629}
-
Sylvain Defresne authored
The ChromeBrowserState has been moved from the "ios" namespace to the global namespace by http://crrev.com/c/2014913. Fix the uses from ios::ChromeBrowserState to ChromeBrowserState. Also remove includes of chrome_browser_state_forward.h and use a simple forward declaration instead (since the old name is no longer necessary). This CL was uploaded by git cl split. R=michaeldo@chromium.org Bug: 1042208 Change-Id: I1d4ecec8dc16e169bca7ebd6697e16db57821d49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017482 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Commit-Queue: Mike Dougherty <michaeldo@chromium.org> Cr-Commit-Position: refs/heads/master@{#734628}
-
Aga Wronska authored
This is a reland of c78cd05f Bug: 1044733 Original change's description: > Parse PerAppTimeLimits policy > > Parse PerAppTimeLimits policy received from the server and store > app limits data in AppActivityRegistry. > This will be followed up by processing app limits. > > Bug: 1015654 > Test: AppTimeTest > Change-Id: I29691e0c801762a73f01cce217826423359957eb > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001411 > Reviewed-by: Yilkal Abe <yilkal@chromium.org> > Commit-Queue: Aga Wronska <agawronska@chromium.org> > Cr-Commit-Position: refs/heads/master@{#734123} Bug: 1015654 Change-Id: I5fde631303ca519501220f60d5bd2fdc53759e0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017184 Commit-Queue: Aga Wronska <agawronska@chromium.org> Reviewed-by:
Yilkal Abe <yilkal@chromium.org> Cr-Commit-Position: refs/heads/master@{#734627}
-
Toni Barzic authored
Should prevent animating background from popping up on the lock screen (there is no point in animating shelf for hotseat changes on lock screen given that neither hotseat nor in-app shelf are visible). Change-Id: I2422f94bab1db9e25b775e36b023db5bbc0b26e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016358 Commit-Queue: Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Manu Cornet <manucornet@chromium.org> Cr-Commit-Position: refs/heads/master@{#734626}
-
Mathias Carlen authored
This patch adds unit tests and a integration / UI test for the recently added auto expand/collapse sheet behavior for prompt actions. Note that there are two sides to this, Prompt has a disable_force_expand_sheet option now to prevent prompt from auto expanding when entering that state. The other part is ConfigureBottomSheet, which now has a oneof (expand, collapse) to automatically update the bottom sheet to the expected state. Bug: b/145204744 Change-Id: I857a2be13e090d9e5d663419ead60497102cb897 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007721 Commit-Queue: Mathias Carlen <mcarlen@chromium.org> Reviewed-by:
Sandro Maggi <sandromaggi@google.com> Cr-Commit-Position: refs/heads/master@{#734625}
-
Sylvain Defresne authored
The ChromeBrowserState has been moved from the "ios" namespace to the global namespace by http://crrev.com/c/2014913. Fix the uses from ios::ChromeBrowserState to ChromeBrowserState. Also remove includes of chrome_browser_state_forward.h and use a simple forward declaration instead (since the old name is no longer necessary). This CL was uploaded by git cl split. R=jlebel@chromium.org Bug: 1042208 Change-Id: I5e8b4cd2b7991f40cde7e450a598a835813c3796 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014975 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
-
Sylvain Defresne authored
The ChromeBrowserState has been moved from the "ios" namespace to the global namespace by http://crrev.com/c/2014913. Fix the uses from ios::ChromeBrowserState to ChromeBrowserState. Also remove includes of chrome_browser_state_forward.h and use a simple forward declaration instead (since the old name is no longer necessary). This CL was uploaded by git cl split. R=sczs@chromium.org Bug: 1042208 Change-Id: I3d4fe29485a1d7c554c2a811e23df22d21514f6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015094 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#734623}
-
Ioana Pandele authored
Bug: 1044930 Change-Id: I9c480c56f0aeb97074964545c732c0d427cdad7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015052 Commit-Queue: Ioana Pandele <ioanap@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#734622}
-
Bo Liu authored
Bug: 1042063 Change-Id: Icd092cbaa08951d90813e97ed869e91ac2af2672 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016850Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#734621}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/bdd89366d34e..684096347b67 git log bdd89366d34e..684096347b67 --date=short --first-parent --format='%ad %ae %s' 2020-01-23 contact@yannic-bonenberger.com Improve git cl split Created with: gclient setdep -r src/third_party/depot_tools@684096347b67 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 Bug: chromium:998922 Tbr: agable@chromium.org Change-Id: Iaddfb7db52842f4b5d7d0b2b876e5f84ea8bdfdf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015633Reviewed-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@{#734620}
-
Jonathan Freed authored
This includes the following changes: https://chromium.googlesource.com/feed/+/39fe4a79d4144e2e1eb170a7ba0a49b7510162f8 Change-Id: I462cf19eef5374e8aad4bc4b203e1fba03f73f73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2018142Reviewed-by:
Dan H <harringtond@chromium.org> Commit-Queue: Jonathan Freed <freedjm@chromium.org> Cr-Commit-Position: refs/heads/master@{#734619}
-
Sebastien Lalancette authored
TBR=anastasi@google.com Bug: 1045075 Change-Id: Ib269f054857ee483faef51c52e476764faa08f15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016859Reviewed-by:
Sebastien Lalancette <seblalancette@chromium.org> Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Cr-Commit-Position: refs/heads/master@{#734618}
-
Avi Drissman authored
MAC_OS_X_VERSION_10_12 is true if Chromium is being built with the macOS 10.12 SDK or newer, as it’s been since mid 2017. MAC_OS_X_VERSION_10_12 is not a runtime check for macOS 10.12 and cannot be used as such. Bug: 1044838 Change-Id: Ia8e40d0f3aab0405e423847dcf9ea1ea2f535091 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016846 Auto-Submit: Avi Drissman <avi@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/9ad78aa7dba2..a4f9acedf3c0 git log 9ad78aa7dba2..a4f9acedf3c0 --date=short --first-parent --format='%ad %ae %s' 2020-01-23 rharrison@google.com Big cleanup to normalize API behaviour (#967) Created with: gclient setdep -r src/third_party/shaderc/src@a4f9acedf3c0 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/shaderc-chromium-autoroll Please CC radial-bots+chrome-roll@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 Bug: None Tbr: radial-bots+chrome-roll@google.com Change-Id: I63e1ccddd1831d15caec16c72b2b74b6a666e984 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017653Reviewed-by:
-
Manu Cornet authored
Split out some helper classes into their own files in the process: HotseatStateWatcher, OverviewAnimationWaiter, ShelfLayoutManagerTestBase. This is a pure (albeit large) refactoring and does not modify any of the actual test semantics. Change-Id: Ica79e3dcead839daa83022de329b5aca8f636c40 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015672 Commit-Queue: Manu Cornet <manucornet@chromium.org> Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#734615}
-
Sebastien Lalancette authored
I apparently misunderstood how the test expectations framework works. Follow-up from: https://chromium-review.googlesource.com/c/chromium/src/+/2016857 TBR=chenwilliam@chromium.org Change-Id: I23d99c45c172cd6849b02b33313c7a0c3e4c033f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015431 Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
-
behdad authored
The reporters which caused no damage (Impl or Main) are terminated and will not be reported to the compositor latency metrics. Bug: chromium:1030304 Cq-Depend: chromium:1961074 Change-Id: I8cc4afe4b00f86b9f4893347d6ef76d8bf0126ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992345Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Cr-Commit-Position: refs/heads/master@{#734613}
-
Avi Drissman authored
BUG=1044828 Change-Id: Ifdbd3a894fe2bf35e784e59620bedcc4063da35b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017044 Auto-Submit: Avi Drissman <avi@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
-
kylechar authored
ContextFactoryObserver is just a wrapper around ContextLostObserver at this point. Switch SurfaceTreeHost so it's a ContextLostObserver. Keep the existing behaviour of posting a new task to handle context lost. This used to happen before ContextFactoryObservers were notified, but now it happens in SurfaceTreeHost::OnContextLost(). TEST=Verified arc++ apps recover after GPU crash on nocturne. Bug: 947279 Change-Id: I0cc9513ee8df252f0143f9c9af12eac84a39eadb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003470Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#734611}
-
Avery Musbach authored
Test: ash_unittests All/SplitViewOverviewSessionInClamshellTestMultiDisplayOnly.DragAndDropIntoAnotherOverviewGrid/0 Test: ash_unittests All/SplitViewOverviewSessionInClamshellTestMultiDisplayOnly.OverviewWidgetStackingOrderWithMultiDisplayDragging/0 Bug: 961170 Change-Id: I56862dfd8094b72ce0abf07a855d058be3d3c3da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008237 Commit-Queue: Avery Musbach <amusbach@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#734610}
-
Mike Reed authored
Very mechanical change: - MScalar --> Scalar - some conversion helpers just not needed: e.g. float_to_scalar Change-Id: I38104e07e8cbef0eba641cdf54fb77858691bc2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013861Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
Florin Malita <fmalita@chromium.org> Reviewed-by:
Martin Barbella <mbarbella@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Mike Reed <reed@google.com> Cr-Commit-Position: refs/heads/master@{#734609}
-
Yuly Novikov authored
Slight update to MSVC - VS version from 16.3.1 to 16.4.3 as a side effect. Other components kept at the old versions: Windows SDK 10.0.18362 Debuggers 10.0.17763 d3dcompiler_47.dll 10.0.17134 Packaging was done on a Windows Server 2019 VM, cleanly created for this purpose. The package was created by downloading VS Professional 2019 installer from https://visualstudio.microsoft.com/downloads/ and then running the installer like this: $ PATH_TO_INSTALLER.EXE ^ --add Microsoft.VisualStudio.Workload.NativeDesktop ^ --add Microsoft.VisualStudio.Component.VC.ATLMFC ^ --add Microsoft.VisualStudio.Component.VC.Tools.ARM64 ^ --add Microsoft.VisualStudio.Component.VC.MFC.ARM64 ^ --includeRecommended --passive The 10.0.18362.0 SDK was installed by this as well. Then Add or Remove Programs was used to modify the 10.0.18362.0 SDK to add the Debuggers package. Then the packaging script was run like this: python depot_tools\win_toolchain\package_from_installed.py 2019 -w 10.0.18362.0 Since the new d3dcompiler_47.dll uses the UCRT and we want to avoid shipping that the final packaging step was to unzip the package, copy over the two copies of that DLL from win_sdk\Redist, replace the Debuggers directory with the 10.0.17763 SDK, and then repackage the toolchain with: > python package_from_installed.py --repackage=<full-path-to-toolchain-dir> UWP support was previously added to package_from_installed.py in http://crrev.com/c/2007881 and http://crrev.com/c/2013579 Bug: 1032635 Change-Id: I85313de0529aa7591e5066bc697c640c5dc52463 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015984Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#734608}
-
Jay Harris authored
This is needed for the upcoming file handling origin trial, which will store state in the operating system, which needs to be cleaned up when the trial expires. WIP CL for the file handling origin trial: https://crrev.com/c/1940001 Bug: 1028448 Change-Id: I3bc8b5cdb786ef17bc8a0360f99d7b07d0cfd4b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010604Reviewed-by:
Jason Chase <chasej@chromium.org> Commit-Queue: Jay Harris <harrisjay@chromium.org> Cr-Commit-Position: refs/heads/master@{#734607}
-
Scott Violet authored
BUG=1033924 TEST=weblayer_support_instrumentation_test_apk BrowserFragmentLifecycleTest.restoresPreviousSession Change-Id: I8f74fda02ff0170c55fe3351153d8180362c9a6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015726Reviewed-by:Evan Stade <estade@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#734606}
-
Avi Drissman authored
MAC_OS_X_VERSION_10_12 is true if Chromium is being built with the macOS 10.12 SDK or newer, as it’s been since mid 2017. MAC_OS_X_VERSION_10_12 is not a runtime check for macOS 10.12 and cannot be used as such. Bug: 1044838, 992915 Change-Id: I28e00f3786831e8899eef917cb5eda3d031e1a2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016847 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Auto-Submit: Avi Drissman <avi@chromium.org> Reviewed-by:
-
Tricia Crichton authored
During ConnectIfNecessary, ChromeDriver will not wait for response to commands issued to DevTools. The first command can take very long to return when running in a debug build. This cl mimics the ways that other initialization commands are sent. Bug: 1040589 Change-Id: I4ca2fc090700f346a29d7b4a2708f486c8cbe847 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015359Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Tricia Crichton <triciac@chromium.org> Cr-Commit-Position: refs/heads/master@{#734604}
-
David Black authored
Existing feature implementation has been stable for a long time and probably no longer needs a kill switch. We can reuse the flag for upcoming experimentation but removing completely in this CL as the flag will be re-defined in the same file as all other Assistant feature flags. Bug: b:148219866 Change-Id: If8e3bca7f141b06c822ae4a8d75bb940c4c37b8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017666Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: David Black <dmblack@google.com> Cr-Commit-Position: refs/heads/master@{#734603}
-
Clark DuVall authored
This creates the permissions component, and moves in PermissionRequest, PermissionRequestID, and PermissionResult. Most of the changes in //chrome were performed with sed: - change includes of moved classes from chrome/browser/permissions to components/permissions - add permissions:: namespace on moved classes Bug: 1025609 Change-Id: Id13b874e84b9fadf96b228154091c5cc0b8f0121 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015763Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#734602}
-
Ryan Sturm authored
This feature allows us to experiment on Google without possibly creating issues with non-Google DSEs. This will hopefully prevent problems or regressions with other search engines. Bug: 1036489 Change-Id: I499b580b1bc0a2d25bed1c8727ba8b36ef6259b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013748 Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#734601}
-
Sylvain Defresne authored
The ChromeBrowserState has been moved from the "ios" namespace to the global namespace by http://crrev.com/c/2014913. Fix the uses from ios::ChromeBrowserState to ChromeBrowserState. Also remove includes of chrome_browser_state_forward.h and use a simple forward declaration instead (since the old name is no longer necessary). This CL was uploaded by git cl split. R=eugenebut@chromium.org Bug: 1042208 Change-Id: I2ac990201f0de9332a204023c8ad2ebbf18a9407 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017347 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#734600}
-
