- 15 Aug, 2018 40 commits
-
-
Devlin Cronin authored
In order to extract apps-specific code from extensions, we'll need to be able to add extra information to the extensions client from outside extensions code. This will require having a centralized initialization for the extensions client. Introduce a single method, EnsureExtensionsClientInitialized(), which constructs and sets the ChromeExtensionsClient. Remove the old way of constructing the client, ChromeExtensionsClient::GetInstance(). Update all callers to construct the client via the new method. While we're at it, update the client to use base::NoDestructor instead of LazyInstance. Bug: 873937 Change-Id: I47147cd5f33ea44079c0a319626c57f3c5813af8 Reviewed-on: https://chromium-review.googlesource.com/1175459 Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#583217}
-
Kyoko Muto authored
The tests demonstrate that nodes which are not connected to host should not be assigned to slot, and slotting API should not have any effect in auto mode. Change-Id: I9403f386f457cd198813d0f49e50cacf1ac23b4b Reviewed-on: https://chromium-review.googlesource.com/1175505 Commit-Queue: Kyoko Muto <kymuto@google.com> Reviewed-by:
Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#583216}
-
Morten Stenshorne authored
This reverts commit a2ce204c. Reason for revert: Sorry, still flaky; see crbug.com/874380 Original change's description: > Reenable PasswordGenerationInteractiveTest.AutoSavingGeneratedPassword. > > Bug: 791389 > Change-Id: Iea3b6e0f2ec7899e099bd9d7e23017ac4c83e459 > Reviewed-on: https://chromium-review.googlesource.com/1170908 > Reviewed-by: Vadym Doroshenko <dvadym@chromium.org> > Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> > Cr-Commit-Position: refs/heads/master@{#582537} TBR=vasilii@chromium.org,dvadym@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 791389, 874380 Change-Id: I1551a9ae472ef3e6645622951bdfcd87f2fb74c7 Reviewed-on: https://chromium-review.googlesource.com/1175761Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#583215}
-
Xida Chen authored
See https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-xenial-rel/2413 TBR=wjmaclean@chromium.org NOTRY=true Bug: 862716 Change-Id: I8e44194cc964ee607d4216d1c338bfeed28e630f Reviewed-on: https://chromium-review.googlesource.com/1175693Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#583214}
-
Sheng-Hao Tsao authored
This reverts commit e30ad9f8. Reasons for revert: breaks CrOS JEA functionality. Details are in: https://b.corp.google.com/issues/112573321 fine. Bug: b:112573321 Test: After reverting the CL, image capture in Chrome camera app works 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 Change-Id: I2fe0458e8997906c10506f8511645ebd2514afe1 Reviewed-on: https://chromium-review.googlesource.com/1175707Reviewed-by:
Ricky Liang <jcliang@chromium.org> Commit-Queue: Sheng-hao Tsao <shenghao@google.com> Cr-Commit-Position: refs/heads/master@{#583213}
-
Kyoko Muto authored
This CL make Hashmap in ShadowTree to connect nodes to slot in manual slotting mode. BUG=869308 Change-Id: I59e6bfcb1dc2a91cf3344623bbbf6f7c8545af0a Reviewed-on: https://chromium-review.googlesource.com/1174133Reviewed-by:
-
Elad Alon authored
This is a reland of 04509e6d Reland reason - the original CL did not cause the test to be flaky, it just exposed it. The offending test has now been disabled. TBR=ari@chromium.org Original change's description: > Rename LogList to TextLogList where appropriate > > Help distinguish WebRTC event logs from textual logs. > > Bug: 775415 > Change-Id: I17b14cfc25ab0c70eecd905cd28bad77304c3b3f > Reviewed-on: https://chromium-review.googlesource.com/1174352 > Reviewed-by: Henrik Grunell <grunell@chromium.org> > Reviewed-by: Avi Drissman <avi@chromium.org> > Commit-Queue: Elad Alon <eladalon@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583036} Bug: 775415 Change-Id: Ia3bd09edfa9ef8dd2fb96a4e2166fe19ac322b18 Reviewed-on: https://chromium-review.googlesource.com/1175661Reviewed-by:
Henrik Grunell <grunell@chromium.org> Commit-Queue: Elad Alon <eladalon@chromium.org> Cr-Commit-Position: refs/heads/master@{#583211}
-
Momoko Sumida authored
This WPT shows that :scope does not work for shadow root. :scope matches nothing when the direct child element or descendant of shadow root should be selected, while :scope works fine for descendant elements within shadow root. Link to the spec: https://drafts.csswg.org/selectors-4/#the-scope-pseudo Link to related issue: https://github.com/w3c/csswg-drafts/issues/3016 Bug: 859692 Change-Id: I801706eb7891035dcb900588d5542bd48fa1c12a Reviewed-on: https://chromium-review.googlesource.com/1158445 Commit-Queue: Momoko Sumida <momon@google.com> Reviewed-by:
Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
-
Morten Stenshorne authored
It's flaky. TBR=joenotcharles@chromium.org Bug: 874387 Change-Id: I3056f49cb1879a6fbacd195f94dfe6992cfd6710 Reviewed-on: https://chromium-review.googlesource.com/1175123Reviewed-by:
-
Makoto Shimazu authored
This is to reflect updates of RendererPreferences arrived at RenderViewImpl to WebWorkerFetchContextImpls. In order to propagate settings to all nested workers, this CL uses mojom::RendererPreferenceWatcher. RenderViewImpl holds mojom::RendererPreferenceWatcherPtr connected to each worker created on the page's context, and each worker has mojom::RendererPreferenceWatcherPtr connected to each child worker created on the worker's context. Once new preference is arrived at RenderViewImpl::OnSetRenderPrefs(), the new preferences will be propagated by passing through the pipes one by one. TBR=avi@chromium.org Bug: 853085 Change-Id: I158fac878f984c9e6e69e45862c5d9209fd6927e Reviewed-on: https://chromium-review.googlesource.com/1170673 Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#583208}
-
Mattias Nissler authored
Edge cases have been discovered where the TPM firmware update completes successfully after interruption, but leaves the TPM in a state where the SRK is still vulnerable. This adds support for a new "cleanup" mode that is available when the system flags a vulnerable SRK on an updated system. BUG=chromium:872746 TEST=Extended existing unit tests. Change-Id: I4fd5dab72961d9cac4b985b688ebff6740317111 Reviewed-on: https://chromium-review.googlesource.com/1172685 Commit-Queue: Mattias Nissler <mnissler@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#583207}
-
Koji Ishii authored
Following bot results are included. 8831 8832 8840 8846 8849 8854 8858 8862 8865 8868 8877 0 lines were removed and 2 lines were deflaked by consecutive results since 8823. TBR=eae@chromium.org, mstensho@chromium.org NOTRY=true Bug: 591099 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: Id2e7578bb8b988c4ec9f21e9328492eef66a9ced Reviewed-on: https://chromium-review.googlesource.com/1173940 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#583206}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 0ecac343. With Chromium commits locally applied on WPT: 7dad0f17 "Added new Sec-Metadata Web Platform Tests." Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/22749 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 Directory owners for changes in this CL: jsbell@chromium.org: external/wpt/resources NOAUTOREVERT=true TBR=raphael.kubo.da.costa@intel.com No-Export: true Change-Id: I953afb89497304a427dcba8b844eb18e792dd90d Reviewed-on: https://chromium-review.googlesource.com/1175559 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#583205}
-
Alex Loiko authored
Implementations CLs in WebRTC are https://webrtc-review.googlesource.com/c/src/+/93468 and https://webrtc-review.googlesource.com/c/src/+/93464. Bug: webrtc:7494 Change-Id: I1f6c66505dbcbe066a0c7fd9750a643e968c3636 Reviewed-on: https://chromium-review.googlesource.com/1170833Reviewed-by:
Brian White <bcwhite@chromium.org> Commit-Queue: Alex Loiko <aleloi@chromium.org> Cr-Commit-Position: refs/heads/master@{#583204}
-
Takashi Toyoshima authored
Though the interface is plumbed, only one layout test calls it for testing itself and there is no real user today. This interface was introduced in WebKit era, and chromium use of this interface was completely replaced by RemoveAllOriginAccessWhitelistEntriesForOrigin in https://chromium-review.googlesource.com/c/chromium/src/+/1105287. This is a trivial preparation for implementing origin whitelising for the Network Service. Bug: 870172 Change-Id: I4ff5a91d95dbb65fa30c471e77d44b7e2ad3a92a Reviewed-on: https://chromium-review.googlesource.com/1175581Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#583203}
-
Yutaka Hirano authored
Those are needed because a request could match with another request made by a foreign origin, but [1] fixed the issue. This is basically reverting [2]. Two layout tests are added to detect regressions. This CL changes the behavior a bit. Without this CL, - A response with a proper access-control-allow-origin header for a cross-origin request with "no-cors" mode is treated as non-opaque, and - A response without a proper access-control-allow-origin header for a same-origin request with "no-cors" mode redirected from a cross-origin resource is treated as opaque while with this CL, - A response with a proper access-control-allow-origin header for a cross-origin request with "no-cors" mode is treated as opaque, and - A response without a proper access-control-allow-origin header for a same-origin request with "no-cors" mode redirected from a cross-origin resource is treated as non-opaque. Also, before this CL, CORSStatus is calculated with an opaque origin for top-level worklet scripts. This CL changes that: now CORSStatus is calculated with the origin of the parent context, and so it stops muting error messages in worklets. 1: https://chromium.googlesource.com/chromium/src.git/+/c1df004861ab704945d31a0d207bb7f4c205e60c 2: https://chromium.googlesource.com/chromium/src.git/+/fad67a5b73639d7211b24fd9bdb242e82039b765 Bug: 809350, 799477 Change-Id: If28f59f6e6ac03a4d5992cca85801231748019bd Reviewed-on: https://chromium-review.googlesource.com/1158165 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Fredrik Söderquist <fs@opera.com> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#583202}
-
Hayato Ito authored
This CL also changes a few other related pieces of code to use references as necessary. Change-Id: I8aaf0dd00e3f56819244a8b6dbdd6c2f758bee64 Reviewed-on: https://chromium-review.googlesource.com/1175592Reviewed-by:
-
Rune Lillesveen authored
Similarly to what we do for slot elements. When moving from a separate re-attach where computing style as part of AttachLayoutTree to RecalcStyle for re-attach we need to detect that we recalc style for distributed nodes for re-attach to SetNonAttachedStyle(). Since we can't really propagate the kReattach up from inside the shadow tree recalc to the shadow host when recalculating light tree children, we recalculate the distributed nodes from the insertion point when we are in a kReattach change. Bug: 873129, 873279 Change-Id: I2364c5f1dce3a79e725d3cb94750f1cfb3e98221 Reviewed-on: https://chromium-review.googlesource.com/1172424 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#583200}
-
Alexander Yashkin authored
This fixes the bug when every window opened from remote NTP tab with same host as remote NTP but different path would be considered to belong to same SiteInstance as NTP. That could lead to nasty effects, such as referrer reset for transfers from Yandex remote NTP. Basically its a rewrite of https://chromium-review.googlesource.com/c/chromium/src/+/998178 patch so it would apply to hosted apps only, as intended, IMHO. Bug: 859062,718516 Change-Id: I76e90c2ff6311ca99a234e75424f8cba9932c05a Reviewed-on: https://chromium-review.googlesource.com/1141574 Commit-Queue: Alexander Yashkin <a-v-y@yandex-team.ru> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#583199}
-
Wei-Yin Chen (陳威尹) authored
AllowReaderForAccessibility was launched in M65. Bug: 777962 Change-Id: I1d702be283cb551ae64cb5c87009a05b6510e2e9 Reviewed-on: https://chromium-review.googlesource.com/1174098Reviewed-by:
Matthew Jones <mdjones@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#583198}
-
Morten Stenshorne authored
This reverts commit 41b5497b. Reason for revert: Caused ash_content_unittests failure on linux-chromeos-dbg - https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-chromeos-dbg/7312 Original change's description: > chromeos: gets more ash_unittests working with single-process mash > > The OverviewButtonTrayTests need to set the keyboard devices *after* > AshTestBase::SetUp() is called. This is is important in single-process mash > as Ash is the one creating the Env that the keyboard devices us. In > non-single-process-mash AshTestSuite is creating the Env these tests use. > > The case ShellTest2.DontCrashWhenWindowDeleted is exercising is different > enough for single-process mash that I created a separate test. > > Adding NOPRESUBMIT=true as this bot passed the trybots, and we're ok with > this test including Env::GetInstance(). > > NOPRESUBMIT=true > > BUG=847992 > TEST=test only changes > > Change-Id: I0543db96ca9aa910340360d8da3e6aafcda34d7f > Reviewed-on: https://chromium-review.googlesource.com/1174978 > Commit-Queue: Scott Violet <sky@chromium.org> > Reviewed-by: James Cook <jamescook@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583161} TBR=jamescook@chromium.org,sky@chromium.org Change-Id: Ib23d73ef909ac7fe2c9821d7ca8203228bd7fb4a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 847992 Reviewed-on: https://chromium-review.googlesource.com/1174493Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/022206d5..091d6f21 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I4e66592ca53b500ba9210e408cb6ecc4d3241914 Reviewed-on: https://chromium-review.googlesource.com/1175497Reviewed-by:
V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#583196}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/35fbbed72c49..21a68ae8e5fa git log 35fbbed72c49..21a68ae8e5fa --date=short --no-merges --format='%ad %ae %s' 2018-08-15 moragues@google.com chromeos_config: Mark nocturne as experimental. Created with: gclient setdep -r src/third_party/chromite@21a68ae8e5fa The AutoRoll server is located here: https://chromite-chromium-roll.skia.org 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=chrome-os-gardeners@chromium.org Change-Id: I470d5d1bfab53de9a1355fa5dadf5a5f04386465 Reviewed-on: https://chromium-review.googlesource.com/1175522Reviewed-by:
Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#583195}
-
Dan Elphick authored
Replace deprecated parameterless *Type*Value() methods with the *Type*Value(Local<Context>) equivalent method. Since these functions return a Maybe, use FromMaybe() on the return value to guarantee a return value even if the conversion could throw an exception. (In future many of these could be converted to use As<Int32>::Cast()->Value() if they had IsInt32 checks instead of IsNumber). This is the cast version of a chromium CL: https://chromium-review.googlesource.com/c/chromium/src/+/1153247 Bug: v8:7786 Change-Id: I09a59a7de133ec429fa1aea1c5350e8af8bc81c3 Reviewed-on: https://chromium-review.googlesource.com/1174730Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Cr-Commit-Position: refs/heads/master@{#583194}
-
Findit authored
This reverts commit a011e05f. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 583132 as the culprit for failures in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2EwMTFlMDVmMDAxYmVmMzkwOTk5MDYyM2FkZDU3ZGYwZWI5YTIwNDIM Sample Failed Build: https://ci.chromium.org/buildbot/chromium.memory/Linux%20ChromiumOS%20MSan%20Tests/8223 Sample Failed Step: ash_unittests Original change's description: > Generalize AccessibilityPanel sizing > > Modify AccessibilityPanel sizing to be more flexible, and work for > both the ChromeVox panel and the SwitchAccess context menu. > > Also fixes a bug where ChromeVox Panel fullscreen goes offscreen when > Docked Magnifier is enabled. > > Bug: 864796 > Change-Id: Ib99150f68dcb332aa86a0cc72d7863d6e6b301f7 > Reviewed-on: https://chromium-review.googlesource.com/1167886 > Commit-Queue: Zach Helfinstein <zhelfins@chromium.org> > Reviewed-by: Robert Sesek <rsesek@chromium.org> > Reviewed-by: David Tseng <dtseng@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583132} Change-Id: Id70f8b9a1b1f7d0f089b38b26c085c773ef9dde1 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 864796 Reviewed-on: https://chromium-review.googlesource.com/1175462 Cr-Commit-Position: refs/heads/master@{#583193}
-
Yuki Shiino authored
https://heycam.github.io/webidl/#construct-a-callback-function This patch supports "construct" algorithm of IDL callback functions. The following WIP patch will be going to use this algorithm. https://chromium-review.googlesource.com/c/chromium/src/+/1170731 Bug: 873942 Change-Id: I3d58db6cb4cb23662593e2c96080668346a399a2 Reviewed-on: https://chromium-review.googlesource.com/1174079Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#583192}
-
Momoko Sumida authored
This reverts commit 2472878c. The following CL was reverted as a suspect for https://crbug.com/873015: crrev.com/c/1164876 This CL reverts the revert as the failing test is not related to CSSStyleSheet. The flaky test has been disabled in crrev.com/c/1171681 Bug: 873015 Change-Id: I54cefa72e4f82b1075550d6efb4a0ca8efe98383 Reviewed-on: https://chromium-review.googlesource.com/1174150 Commit-Queue: Momoko Sumida <momon@google.com> Reviewed-by:
-
Chromium WPT Sync authored
Using wpt-import in Chromium 53f90379. With Chromium commits locally applied on WPT: 7dad0f17 "Added new Sec-Metadata Web Platform Tests." Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/22747 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=raphael.kubo.da.costa@intel.com No-Export: true Change-Id: I81c9d62cdbbfd15082eb71cd8bbeb83c2945a9b8 Reviewed-on: https://chromium-review.googlesource.com/1175543 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
-
Hiroki Nakagawa authored
This test (OnDiskApp/NetworkContextConfigurationBrowserTest.CookiesEnabled/1) is now failing on the Mac10.11 bot: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.11%20Tests/28580 Noth that the Findit suspects the following CL is failing the test with 86% confidence: https://chromium-review.googlesource.com/c/chromium/src/+/1153630 https://findit-for-me.appspot.com/waterfall/failure?url=https://build.chromium.org/p/chromium.mac/builders/Mac10.11%20Tests/builds/28580 At first, I tried to revert it but failed because of merge conflict: https://chromium-review.googlesource.com/c/chromium/src/+/1175601 Bug: 847555 Change-Id: Idf91c9f8595139dd1d9c667adc304e08d0e6083d Tbr: mmenke@chromium.org Reviewed-on: https://chromium-review.googlesource.com/1175585 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
-
Khushal authored
The RasterInterface should be notified when accessing the GrContext, so it can make sure any state tracked in the implementation is reset if it could be modified by using the GrContext. We are already doing this for raster tasks in GpuRasterBufferProvider, also do this in upload tasks which use the GrContext for uploading images. R=ericrk@chromium.org Bug: 870317 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I2b5039f2a2f64fb6986181639b81597c741103a5 Reviewed-on: https://chromium-review.googlesource.com/1175415 Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
Eric Karl <ericrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#583188}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/a66ea19e9d55..35fbbed72c49 git log a66ea19e9d55..35fbbed72c49 --date=short --no-merges --format='%ad %ae %s' 2018-08-15 chrome-bot@chromium.org Update config settings by config-updater. Created with: gclient setdep -r src/third_party/chromite@35fbbed72c49 The AutoRoll server is located here: https://chromite-chromium-roll.skia.org 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=chrome-os-gardeners@chromium.org Change-Id: I44def4ab9ed56c6a414e404540fd7aff66a377ed Reviewed-on: https://chromium-review.googlesource.com/1175521Reviewed-by:
-
Hiroki Nakagawa authored
This reverts commit 04509e6d. Reason for revert: Looks like this is failing the following test on the Mac10.12 bot: WebRtcAudioDebugRecordingsBrowserTest.TwoCallsWithAudioDebugRecordings See: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.12%20Tests/14929 Original change's description: > Rename LogList to TextLogList where appropriate > > Help distinguish WebRTC event logs from textual logs. > > Bug: 775415 > Change-Id: I17b14cfc25ab0c70eecd905cd28bad77304c3b3f > Reviewed-on: https://chromium-review.googlesource.com/1174352 > Reviewed-by: Henrik Grunell <grunell@chromium.org> > Reviewed-by: Avi Drissman <avi@chromium.org> > Commit-Queue: Elad Alon <eladalon@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583036} TBR=avi@chromium.org,grunell@chromium.org,eladalon@chromium.org Change-Id: I90c270f52209fed5963f18bd4c64225dc7aebfb3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 775415 Reviewed-on: https://chromium-review.googlesource.com/1175621Reviewed-by:
-
Stuart Langley authored
Team drives can have no ascii and path like characters in the name. Normalize the names to remove these. This will lead to a delta between what you see in the web app and what you see in the file manager for team drives with these names. Bug: 873920 Change-Id: I24fd8664cc64a62b9a1d5e72d0138c0792c449d9 Reviewed-on: https://chromium-review.googlesource.com/1174134Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Stuart Langley <slangley@chromium.org> Cr-Commit-Position: refs/heads/master@{#583185}
-
Stuart Langley authored
If the user has a large number of team drives, we fetch the list in batches. If this value is not set then we get a small amount per batch, resulting in many more calls to the server to get the list of drives, which degrades app startup performance. Bug: 874354 Change-Id: I82982a6decda3f4a342925b7b3d9872226938cd7 Reviewed-on: https://chromium-review.googlesource.com/1175520Reviewed-by:
-
Ramin Halavati authored
Preferences related to proxy config are removed from the persistent storage list for incognito mode. After this CL, if these preferences are changed from incognito mode, they are only stored in memory and won't affect user profile. Bug: 861722 Change-Id: I2670d44b59443f1c26844612842402511d246e63 Reviewed-on: https://chromium-review.googlesource.com/1172133Reviewed-by:
-
Dominic Mazzoni authored
crrev.com/c/1062661 made it so that any time an accessibility node changes, we re-serialize the entire CSS block it's contained in - while this fixed some correctness issues, it introduced a performance regression that's too significant to ignore. This change rolls back the fix for now until we can find a way to fix it that doesn't impact performance. TBR=dtseng@chromium.org Bug: 868830, 865621, 843746 Change-Id: I900a4e6ba796608974e881f091b99b0d45c09536 Reviewed-on: https://chromium-review.googlesource.com/1174851Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#583182}
-
Giovanni Ortuño Urquidi authored
ProcessAppOperations will need to include the URL of the app that was installed. To avoid having two distinct callbacks, this CL changes InstallCallback to also return the url. Bug: 864904 Change-Id: Ie296a90b4588c0d301c9a03d487433b9d56832b1 Reviewed-on: https://chromium-review.googlesource.com/1174589 Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#583181}
-
Ramin Halavati authored
Preferences related to network time are removed from the persistent storage list for incognito mode. After this CL, if these preferences are changed from incognito mode, they are only stored in memory and won't affect user profile. Bug: 861722 Change-Id: I7a37a22be09e21942e608b1f407b1d27704fa8fd Reviewed-on: https://chromium-review.googlesource.com/1172134Reviewed-by:
Nicolas Zea <zea@chromium.org> Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/master@{#583180}
-
Tatsuhisa Yamaguchi authored
This will prevent notification counter icon shown in white while in the OOBE screen, when the background of the icons are also bright color. Test: manual test Bug: 874021 Change-Id: I91cbbd1111b33d1a030b1d5aae2bdd884a1d487a Reviewed-on: https://chromium-review.googlesource.com/1175517Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Commit-Queue: Tatsuhisa Yamaguchi <yamaguchi@chromium.org> Cr-Commit-Position: refs/heads/master@{#583179}
-
Kyoko Muto authored
As the second step of implementing "Imperative Shadow DOM Distribution API", this CL make assign function to assign nodes to slot in manual slotting mode. This CL also introduces HeapVector for each slot to store the nodes that assign introduced. BUG=869308 Change-Id: I9b02a70f601364123fb565221d3def760408bc2a Reviewed-on: https://chromium-review.googlesource.com/1166925Reviewed-by:
-
