- 22 Sep, 2020 40 commits
-
-
Chromium WPT Sync authored
Using wpt-import in Chromium 627dabbe. With Chromium commits locally applied on WPT: 434c646e "[mathml] Make math display values on pseudo elements compute to flow" 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: mkwst@chromium.org, andypaicu@chromium.org: external/wpt/content-security-policy NOAUTOREVERT=true TBR=foolip@google.com No-Export: true Change-Id: Idcc99809bdf90783e2e8ced3d63e6c32777ec134 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424063Reviewed-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@{#809336}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/6a7c1f2e304e..ac231dd664d0 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 lgrey@google.com,rsorokin@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: lgrey@google.com,rsorokin@google.com Change-Id: Ia57edf658d69e21b566aece1a0ed74350b901d69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423970Reviewed-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@{#809335}
-
Maksim Sisov authored
This is a reland of fa06bf45 Fix: disable CloseWithAppMenuOpen for lacros. See https://crbug.com/1126339 Original change's description: > ozone/wayland: gracefully shutdown the browser on protocol error. > > Wayland may disconnect the client if it hits an unrecoverable > error. That is, it prints an error message and client cannot > do anything about that after that except shutting itself down. > > Thus, while watching the display fd, always check for errors. If > a protocol error is set, trigger |shutdown_cb| and also stop > watching the fd. > > Bug: 1127278 > Change-Id: Ie324af93d455c0c83f8e75cdecfafe2254da1972 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404931 > Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> > Reviewed-by: Robert Kroeger <rjkroege@chromium.org> > Cr-Commit-Position: refs/heads/master@{#807775} Bug: 1127278, 1126339 Change-Id: I9c72d2f72b331d278ef0ece89e6954b6f3850e39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416355 Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Cr-Commit-Position: refs/heads/master@{#809334}
-
Alexander Surkov authored
--active-tab is a handy way to dump accessible tree of an active tab in a browser and allows to reduce bulky output from the browser UI. The selector is intended to be used in conjunction with other selectors, for example, ax_dump_tree --firefox --active-tab will dump accessible tree of a selected tab in Firefox browser. Bug: 1124366 Change-Id: I5ddfa333d44d0e854e5b38d98f52e226a9a53e06 AX-Relnotes: n/a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416773Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Alexander Surkov <asurkov@igalia.com> Cr-Commit-Position: refs/heads/master@{#809333}
-
Peter Qiu authored
Required for supporting GpuMemoryBuffer backed by NV12 dmabuf. Bug: b/166284508 Test: Manually on cast device Change-Id: I18201b53fbd77e0f1e4c4947a346b68ee6895eb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417508 Commit-Queue: Michael Spang <spang@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Reviewed-by:
Albert Chaulk <achaulk@chromium.org> Cr-Commit-Position: refs/heads/master@{#809332}
-
Hua, Chunbo authored
Bug: 880486 Change-Id: Ia10f8917c02adff50747ad722a8d8a2174edbba2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422325Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Chunbo Hua <chunbo.hua@intel.com> Cr-Commit-Position: refs/heads/master@{#809331}
-
Eugene But authored
The data is retrieved from PreviousSessionInfo singleton and includes the following fields: - free_disk_in_kb - memory_warning_in_progress Original CL: https://chromium-review.googlesource.com/c/chromium/src/+/2414784 Bug: 1103752 Change-Id: I6e9b543be19634d08596a4b83368d800605c9cb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422143 Auto-Submit: Eugene But <eugenebut@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/master@{#809330}
-
Sigurd Schneider authored
This CL adds the IO agent to all kinds of workers. Bug: chromium:1069378 Change-Id: Ic8ad45f2c9f5a19a81c6ac8231871e1a087a952c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2421369 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#809329}
-
Etienne Pierre-doray authored
To let the user do special handling on the main thread e.g. Scavenging uses different tracing categories for background/foreground threads. Change-Id: I001b669e318bf88f39358ddb96482ec5ed4b62a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2418986Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/master@{#809328}
-
Aaron Krajeski authored
CanvasResourceProvider::CreateSharedImageProvider receives a weak pointer to the ContextProviderWrapper and returns nullptr if it does not exist. Unfortunately SharedGpuContext::IsGpuCompositingEnabled can re-create the ContextProviderWrapper after this check happens, leading to potential use-after-frees. To me it simply makes the most sense to not create a CRP if context is lost, as the created provider would be invalid and nullptr would get returned anyway. Bug: 1126424 Change-Id: Ic92709d7a38d94e5e7529efac3a09405d64eaa34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417097Reviewed-by:
Juanmi Huertas <juanmihd@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#809327}
-
Sahel Sharify authored
Before: PaymentRequestSpec.java stores duplicates of payment details to be used in its getters. This is error prone since the variables on c++ side and their duplicates on java side need to kept synced. After: PaymentRequestSpec.java always retrieves most updated payment details from c++ implementation. Bug: 1129708 Change-Id: Ia106446bc08e91a6fcdcfc3875f078d2fd6ed6c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417543Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Liquan (Max) Gu <maxlg@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#809326}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1600754349-f2bf1ecbd6b189476a5e50362abd5d7f8ec183c4.profdata to chrome-mac-master-1600775907-1d0a614b540ad15c6823911f93c081428c564ce9.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:mac-chrome Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com Change-Id: I4e376d4a9d268a7b8c1fd301fb7b5f6e9ca4715c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423967Reviewed-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@{#809325}
-
Esmael El-Moslimany authored
When removing a download entry, a toast is shown. Some download entries are considered dangerous or to be mixed content. Those entries can be removed. Undo can bring back what was removed, but this does not include dangerous or mixed content entries. This CL hides the undo button if the single entry removed is dangerous or mixed content. Or in the case for clear all, if all entries are dangerous or mixed content, the undo button is also not shown in the toast. Bug: 1116329 Change-Id: If4cb9dc81764c6e8bce7329267aa95fd477e20ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416741Reviewed-by:
John Lee <johntlee@chromium.org> Reviewed-by:
Alex Gough <ajgo@chromium.org> Commit-Queue: Esmael Elmoslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#809324}
-
Lukasz Anforowicz authored
This CL excludes from the rewrite source code in directories that contain the following substrings: third_party/blink/ /renderer/ Bug: 1069567 Change-Id: I11e05452418eed416dbf1f6787333f9b4dfe89cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416402Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#809323}
-
Mugdha Lakhani authored
Add TODOs for web platform support tasks which are being tracked by a shared label for easy tracking. Bug: None Change-Id: I84b24f9582b734e6a36bc5dd7e443a7e2d7f9669 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424143 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Auto-Submit: Mugdha Lakhani <nator@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#809322}
-
Aaron Leventhal authored
Previously, the document lifecycle changed at least once per node that is either dirty or an event source, during SendPendingAccessibilityEvents(). This updates SendPendingAccessibilityEvents() to only update the main document and popup document lifecycles only once. In addition, detailed DCHECKs are performed to ensure that the layout layout tree state is up to date for each node accessed during this process. AX-Relnotes: n/a Bug: None Change-Id: I45cdcb1c03e5284c43fd94a8c5ac4d58d837566f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2187136 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#809321}
-
Adithya Srinivasan authored
Found while doing an audit of WebContents::GetMainFrame(). web_contents->GetMainFrame()->GetParent() will always return null. Change-Id: Idc5d2ed719a400a300198b9c36ab4e3307934556 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422440 Commit-Queue: Adithya Srinivasan <adithyas@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#809320}
-
Jonathan Ross authored
Currently content/renderer/android/OWNERS lists a dependency on content/renderer/input which was removed. That owner file is being temporarily re-added[1]. As without it all changes to content/renderer/android fail, including updating the owners file. This change removes the dependency, and places dtapuska@ as an OWNER. This will be followed by a revert of the temporary re-add of content/renderer/input/OWNERS [1] https://chromium-review.googlesource.com/c/chromium/src/+/2422141/ Bug: 1097816 Change-Id: I06a554dc52dfd9820048eb14af79163db97e40ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422181Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#809319}
-
Sky Malice authored
Adding skym@ and wenyufu@, who have recently made feature modifications to the firstrun. Removing yusufo@ who is not currently making changes in this space and is also an OWNER in a parent folder anyways. Change-Id: I9343df6eb96a52fa3e381b9859ec8c2198485a63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417300Reviewed-by:
Wenyu Fu <wenyufu@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#809318}
-
Boris Sazonov authored
Fixes two separate issues with the unconsented primary account sign-out flow within PrimaryAccountMutator and PrimaryAccountManager: 1. Check HasUnconsentedPrimaryAccount in PrimaryAccountMutator so that the PrimaryAccountManager::SignOutXYZ is actually invoked even if there's no sync consent. 2. Make sure PrimaryAccountMutator calls GoogleSignedOut using a correct account info - before this change, it would be invoked with an empty account info if there's no sync consent. Bug: 1130526 Change-Id: I9019faeb602a32a499ae7fd3cab09f5634fc69ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2421739 Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#809317}
-
Joshua Pawlicki authored
This data is already sent in the <app> element, but sending it in <request> ties it to the updater and enables Omaha's cross-product monitoring and logging to be more aware of this updater. Bug: 1110339 Change-Id: Ib4ec718a281664e3732f6ca060be7300902fa1a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2418474 Auto-Submit: Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Commit-Queue: Joshua Pawlicki <waffles@chromium.org> Cr-Commit-Position: refs/heads/master@{#809316}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/566821cb0e58..44623aeccd06 2020-09-22 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SPIRV-Tools from 60ce96e2ff10 to 125b64241909 (1 revision) 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 syoussefi@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/+doc/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-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: syoussefi@google.com Change-Id: I76a9dd1465dd6a584a565dc6764b8859affb0d15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423542Reviewed-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@{#809315}
-
Vladimir Levin authored
This patch ensures that we don't try and update assignments if the layout view is locked in its parent frame. If the view is locked, it means that we skipped processing prepaint for it, which means that the contents here might not have the LocalBorderBoxProperties (created during prepaint). However, the assignment needs the properties to do its work. Since the frame walk here is unconditional, there is no need to keep track of the dirty bit flags, as long as we don't clear the flags on the compositor itself. This is similar to how the throttling logic behaves. R=chrishtr@chromium.org Bug: 1128790 Change-Id: Ic325b618161c68d5886d0a5c0926cbd29e81d38e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422265 Commit-Queue: vmpstr <vmpstr@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#809314}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1600754349-bb0b36845adda8f601cf43d9095b0eb5c5334e61.profdata to chrome-linux-master-1600775907-52df3750a6dec0d6a74672a50b3faa88175a1e9e.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com,chrome-brapp-engprod@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chrome Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com,chrome-brapp-engprod@google.com Change-Id: Ibbad7da619409ff8fc0365cfdab25f45ac3291de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423968Reviewed-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@{#809313}
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: I73e93914aedf3fcce9a61766c21f91973e709358 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423406Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#809312}
-
Aaron Leventhal authored
Do not create or initialize accessibility objects at the wrong time. Bug: 1125186 Change-Id: I14110615efb4e18a22ebccf2e67b64ce6f258e5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399317Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#809311}
-
Antonio Gomes authored
This header is included by pepper and chromecast code, and won't move out of the Blink API any soon. BUG=787252 R=guidou@chromium.org, haraken@chromium.org TBR=spang@chromium.org Change-Id: I7bc274541ef242cf6146b9988b7c29cf10869145 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2418798 Commit-Queue: Antonio Gomes (GMT-4) <tonikitoo@igalia.com> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#809310}
-
Aaron Krajeski authored
Merging this CL with TODOs to keep this CL small. TODOs: - Single radius version of function called without an array - Accept generic dictionaries with "x" and "y" values as arguments - Add WPT tests Bug: 1123971 Change-Id: I41816beca0678b7df873310d16f826f2f3ed5e07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2388151Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#809309}
-
Olga Sharonova authored
(Behind a flag) * Configures renderer-side RT audio threads based on the audio buffer duration, the same way CoreAudio does for audio device threads. * This CL covers only audio playback and capture which use base::PlatformThread directly (this is most of the audio paths). * WebAudio worklet and audio loopback could probably also benefit from such changes, but it requires a separate effort of exposing API in blink::Thread/SimpleThread (WebAudio) and base::Thread (loopback). * The change is disabled by default. We'll run a finch experiment to evaluate it. *If we do decide to keep it, as part of cleaning up the experiment, we will remove the new virtual from PlatformThread::Delegate and move it to be passed along with the ThreadPriority (presumably in some sort of struct, but TBD). Doc: https://docs.google.com/document/d/12grOIZ4ootmJb5RYoe3GuJDCzYTjtNiuGIG6PvCz-78/edit?usp=sharing ------ API discussion: V3 of API (PS10) * Removed a data member from Delegate V2 of API (PS8) * Looks a bit better V1 of API (PS7) * I'm not a fan of having |audio_buffer_duration| in the thread API, but left it for now, to make it clear what exactly is going on. Bug: 1112952 Change-Id: I43c0b92d60622c74b9eede4e9feba9142cbca9fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398661 Commit-Queue: Olga Sharonova <olka@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#809308}
-
Jonathan Ross authored
When content/renderer/input was moved[1] it removed the OWNERS file. However content/renderer/android/OWNERS lists it as a dependency. This leads to any changes to content/renderer/android to fail presubmit, due to the missing file. This includes changes to remove that dependency in the OWNERS. This change temporarily re-adds the file so that the dependency can be removed. Removing the dependency will be done in a follow-up[2]. After which this change will be reverted. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2411941 [2] https://chromium-review.googlesource.com/c/chromium/src/+/2422181/ Bug: 1097816 Change-Id: Ic318ebdd5c9e845afb6047776a2b9ebb0b5d746a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422141Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#809307}
-
Jan Wilken Dörrie authored
This change modifies the WellKnownChangePasswordNavigationThrottle to use the URL used in the beginning of the navigation for the fallback logic in case the server does not support .well-known/change-password URLs. So far it has been using `navigation_handle()->GetURL()`, which could change in the presence of server-side redirects and thus could point to a different origin, for which the fallback logic would be wrong. Fixed: 1130519 Change-Id: I8177f7a8f794de91d2cf81d92aab11179280f73c Bug: 1130519 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2421512Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#809306}
-
Roman Aleksandrov authored
Add TPM locked bubble which shows information on how long user should wait. Bug: 1126908 Change-Id: I45e4738eca22fa172298111b97218689d945a912 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410120 Commit-Queue: Roman Aleksandrov <raleksandrov@google.com> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Cr-Commit-Position: refs/heads/master@{#809305}
-
Maksim Sisov authored
This happens because mojo::core::Init() is being called multiple times. Move that into the Environment setup. Bug: 1124902 Change-Id: I98a05ff1c813c32ae8f3223907c8cf22b2f078ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424164 Auto-Submit: Maksim Sisov (GMT+3) <msisov@igalia.com> Commit-Queue: Nick Yamane <nickdiego@igalia.com> Reviewed-by:
Nick Yamane <nickdiego@igalia.com> Cr-Commit-Position: refs/heads/master@{#809304}
-
Alan Cutter authored
This CL adds three metrics for preinstalled web apps: - WebApp.Preinstalled.ConfigErrorCount - WebApp.Preinstalled.EnabledCount - WebApp.Preinstalled.DisabledCount This helps track whether we see the expected number of preinstalled apps configured on devices and whether there are bad config files. Bug: 1128801 Change-Id: I2a33d9d5812ff29d0218f345ba68c8727542218c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2418756 Commit-Queue: Alan Cutter <alancutter@chromium.org> Reviewed-by:
Glen Robertson <glenrob@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#809303}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/d53ca9807f41..dcc28c9f5a3d 2020-09-22 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2020-09-22 tvanderlippe@chromium.org Remove scripts support from module.json 2020-09-22 wolfi@chromium.org Add css variable for link-color If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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/+doc/master/autoroll/README.md Bug: chromium:1122511 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I6cee085115b483d29241f9c6ca816f435f6c2868 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423964Reviewed-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@{#809302}
-
Nick Diego Yamane authored
Recent refactors in surface code caused a regression in tab dragging. More specifically, when running on Wayland compositors that drop the DND session when the DND origin window gets destroyed (see [1] for further explanation). The crash happens due to a use-after-free issue in WaylandSurface event handlers, when the wl_surface::leave event comes in after its root window destruction (eg: a single-tab window being snapped into tab strip). To fix it, this CL unsets WaylandSurace's root_window when surface ownership transferring to WindowDragController is done. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2267637 R=msisov@igalia.com them containing 1 tab, then drag the tab from window 1 to window 2. Once it gets snapped into window 2 the drag session must keep responding to drag events, etc. Test: On a Gnome Shell Wayland session, open 2 Chromium windows, each of Bug: 896640 Change-Id: Ie31948099968ec9a932c44efde2985e6c4d7dea8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422273 Commit-Queue: Nick Yamane <nickdiego@igalia.com> Reviewed-by:
Maksim Sisov (GMT+3) <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#809301}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/540c58aa5949..6a7c1f2e304e 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 rsorokin@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: rsorokin@google.com Change-Id: Ie8ba2c5a9d91660233010699197d7e1572b4705d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423963Reviewed-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@{#809300}
-
Rushan Suleymanov authored
Bug: 1127959 Change-Id: Icb7990bdc7ac2071ae6c13cc80a625c47c4a8d61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423845 Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#809299}
-
Matthias Körber authored
Change-Id: I7cdeead924974d382c09c9e2072473186200e98e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2421666 Auto-Submit: Matthias Körber <koerber@google.com> Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#809298}
-
Gyuyoung Kim authored
As content::ViewportStyle enum type was moved to Blink, it would be good if we can use it in the whole area without converting. So, this CL replaces the existing enum type and all uses with web_pref::WebViewportStyle after moving web_viewport_style.h from public/platform/web_viewport_style.h to public/common/web_preferences. Bug: 919392 Change-Id: I7443ea5642c36e609086ca52af87c5e66630bca2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2418597Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Sean Topping <seantopping@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Cr-Commit-Position: refs/heads/master@{#809297}
-