- 14 Jan, 2021 40 commits
-
-
Adithya Srinivasan authored
Looks like this wasn't disabled correctly the first time. Disabling for real (and also added OS_ANDROID due to large number of flakes there). Bug: 1156218 Change-Id: I2b308bf11505b1081ac9c3f88676bcc61e65fb38 Tbr: arthursonzogni@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627716Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Commit-Queue: Adithya Srinivasan <adithyas@chromium.org> Cr-Commit-Position: refs/heads/master@{#843591}
-
Sophie Chang authored
This is a reland of 1a291df2 Original change's description: > Re-enable PredictionManager browser tests on Win/Mac/CrOS > > And fix init issue on ChromeOS for sign in profiles > > Change-Id: I26b87d58f2eae2afecf67685690312a8aed70c60 > Bug: 1146151 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625157 > Reviewed-by: Michael Crouse <mcrouse@chromium.org> > Commit-Queue: Sophie Chang <sophiechang@chromium.org> > Cr-Commit-Position: refs/heads/master@{#843176} Bug: 1146151 Change-Id: Id9b0353b3f5e7d5ffc3d27f68aec612efad4e68e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626985Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Commit-Queue: Sophie Chang <sophiechang@chromium.org> Cr-Commit-Position: refs/heads/master@{#843590}
-
Alice Wang authored
This CL disables the flaky test FirstRunIntegrationTest#testExitFirstRunWithPolicy. Bug: 1166585 Change-Id: I83ce1d787b894fbfcb00d61b4cf4477729e461cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628953 Auto-Submit: Alice Wang <aliceywang@chromium.org> Commit-Queue: Wenyu Fu <wenyufu@chromium.org> Reviewed-by:
Wenyu Fu <wenyufu@chromium.org> Cr-Commit-Position: refs/heads/master@{#843589}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/d46475f87758..628b7f61f813 2021-01-14 chrome-bot@chromium.org Update config settings by config-updater. 2021-01-14 saklein@chromium.org cbuildbot/commands.py: Fix for python3/encoding issue. 2021-01-14 chrome-bot@chromium.org Update config settings by config-updater. 2021-01-14 inglorion@chromium.org cros_setup_toolchains: build post-cross packages after others 2021-01-13 pwang@chromium.org For *-borealis run suite:av-analysis_trace_per-build 2021-01-13 jwata@google.com Remove ISOLATESERVER from lib/constants.py If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel Tbr: chrome-os-gardeners@google.com Change-Id: I2ec6cfc8434c5aef685ac0ddc6d67bb8a198dc06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628601Reviewed-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@{#843588}
-
Olivier Robin authored
Unittests trigger some shutdowns and SessionService is not built to handle multiple shutdowns correctly. Bug: 1166186 Change-Id: Ic3b1ca9b68af7d8b02eafed588b308f5f78c5610 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627277Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/master@{#843587}
-
Caitlin Fischer authored
Bug: 1126640 Change-Id: Idf2906985b34d3b69556e55fb745a9d23acf526a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629567Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#843586}
-
Becca Hughes authored
WebContentsDestroyed Destroys MediaSessionControllersManager when the web contents is destroyed to avoid a crash. At the moment when WebContentsImpl is destroyed it ends up calling GetMediaSessionInfoSync which calls the destroyed WebContentsImpl. This destroys the media session controllers before they can do that. BUG=1136465,1157779 Change-Id: I7a3d678c4011a818c0ca5ac8d53b8a3420e662fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626920 Commit-Queue: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Cr-Commit-Position: refs/heads/master@{#843585}
-
Egor Pasko authored
The LegacyLinker still wants to wait until RELRO arrives (because there is no atomic RELRO replacement support yet - but it is not hard). In order to accommodate both waiting and delayed use, the Linker.java looks whether the subclass waited for RELRO, and if there was no explicit waiting, assumes the atomic replacement is implemented. This parent/subclass coordination is a bit unfortunate, as it makes the state transitions hard to understand, but the implementation of it is small. I do not expect this to have a big impact on startup. My local testing did not reveal any evidence of faster renderer load time. Potentially in the future mLibInfo could be guarded by another lock, so that it could arrive *while* the native library is loading. Currently it is not done, as it would require a larger change. I think it would have a chance to help only if this change as-is provides some nontrivial help. New metrics are introduced to try to avoid the overhead of a fair A/B test. They would approximate how many times a cold browser process makes a shared RELRO region such that it arrives *after* the child has loaded the native library (in other words, the child is not blocked). These metrics do not account for being in background and such, so it is a very rough approximation. Lab performance testing summary: android-go-perf,android-pixel2-perf,android-nexus5x-perf: no change Bug: 1154224 Change-Id: I6d385280910424e1d6b09784650d72b598a1ba23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610030 Commit-Queue: Egor Pasko <pasko@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Benoit L <lizeb@chromium.org> Cr-Commit-Position: refs/heads/master@{#843584}
-
Anders Hartvoll Ruud authored
This plumbs the StyleRecalcContext from OriginalStyleForLayoutObject, through StyleResolver and into ElementRuleCollector. Bug: 1145970 Change-Id: I301ab3b459db8ef65dce3793390ed53a95504f01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627409 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#843583}
-
Robert Kaplow authored
Bug: 1053702 Change-Id: I123c2282008bd4312752e8f71f8d7d29aad580b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626777 Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#843582}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/069cce000b9e..9513255f7c36 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 adithyas@google.com,andypaicu@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: chromium:1158445 Tbr: adithyas@google.com,andypaicu@google.com Change-Id: I688bb6a9b172543236e682c62b1f50f2f35ad9b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629398Reviewed-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@{#843581}
-
Alexander Surkov authored
Bug: 1160279 Change-Id: I90c4da626f364d2c47637c748cc1ba0b37333fb3 AX-Relnotes: n/a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2598577Reviewed-by:
Joanmarie Diggs <jdiggs@igalia.com> Commit-Queue: Alexander Surkov <asurkov@igalia.com> Cr-Commit-Position: refs/heads/master@{#843580}
-
Minoru Chikamune authored
Before this CL, there was only a per-thread CompositorTaskRunner. So any compositor task was running on per-thread compositor task runner even when the task belongs to ASG. This CL introduces per-ASG CompositorTaskRunner to run ASG’s compositor tasks, and migrate MediaFactory to use per-ASG CompositorTaskRunner. The remaining callsites will be migrated on following CL. Bug: 1105403 Change-Id: I548e4aaeefee8c229d2f31c26a5a30b3d6386ed2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2601019 Commit-Queue: Minoru Chikamune <chikamune@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#843579}
-
Kevin Ellis authored
Presently the test with the highest flake score under Blink>Animation. The cause of the flake is text aliasing differences; however, the test is not specifically for antialiasing but merely ensuring that an animation containing a neutral keyframe takes effect. Replacing the text with a box addresses the flake. Bug: 1165833 Change-Id: Ic87010210eda9055c0f67d996267cd9a814ad5d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623819Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#843578}
-
Jesse Doherty authored
This action is logged at the same time as Search.ContextualSearch.All.ResultsSeen::true. The value is used as part of a high-level guiding metric. We're trying to consolidate these metrics as user actions to improve query speeds and enable new analysis. Bug: b/161525144 Change-Id: Ic272acac7e75d2666ae6d6815d1ff9d38f46727d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628150 Commit-Queue: Jesse Doherty <jwd@chromium.org> Auto-Submit: Jesse Doherty <jwd@chromium.org> Reviewed-by:
Donn Denman <donnd@chromium.org> Cr-Commit-Position: refs/heads/master@{#843577}
-
Avi Drissman authored
CF-style frameworks use the CF naming conventions, and calls named "Create" create objects whose lifetimes need to be managed. Bug: none Change-Id: I56a57f93627a9fcb874f9f90d1c1d637e1172664 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626517 Commit-Queue: Avi Drissman <avi@chromium.org> Auto-Submit: Avi Drissman <avi@chromium.org> Reviewed-by:
Markus Handell <handellm@google.com> Cr-Commit-Position: refs/heads/master@{#843576}
-
Peter Kasting authored
Bug: 1159562 Change-Id: Iad8ed010bb6ca7123f8a6a4fe2546712790a75ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628084 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Allen Bauer <kylixrd@chromium.org> Reviewed-by:
Allen Bauer <kylixrd@chromium.org> Cr-Commit-Position: refs/heads/master@{#843575}
-
chromium-internal-autoroll authored
Release_Notes: http://go/help_app-x20/relnotes/Main/help_app_nightly_202101140600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/help_app/app/+/bx6pXjyY-3vkrBjpqnuCDbusE-Ui_g3xSzSffOHHktoC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll Please CC help-app@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 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: b/174321021 Tbr: help-app@grotations.appspotmail.com Change-Id: Id04cacd8e798e1b12249939ac113392ce3d70602 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629396Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1610614773-8fa72e139bfbe669301559d8a5dcb0f175d80f50.profdata to chrome-win64-master-1610625483-0e8af23579a6861bbbc901692aa081cb0bce75b1.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-win64-chromium Please CC pgo-profile-sheriffs@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:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I9c2ca94a72349b0ce9e9ed88ee897132e6553f40 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628377Reviewed-by:
-
Etienne Bergeron authored
This CL is moving the computation of engaged sites to the worker pool. Move the worker model to a single static function to avoid any incorrect fields accesses. The worker compute the sites and pass it to the main thread. The callbacks are queued and executed when at the completion of the background computation. Bug: 1157596 Change-Id: I4021d87fde51d673f78154b6cd5fc94fa71356d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627758Reviewed-by:
Joe DeBlasio <jdeblasio@chromium.org> Reviewed-by:
Etienne Pierre-Doray <etiennep@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#843572}
-
Peter Kasting authored
Bug: 1159562 Change-Id: I1f6e904976a027ed870744c50ec1f6444deefd62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628498 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Allen Bauer <kylixrd@chromium.org> Reviewed-by:
-
Peter Kasting authored
Bug: 1159562 Change-Id: Ie757c300fe2f4c6ab30173d777b1abdacd979feb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625960 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Allen Bauer <kylixrd@chromium.org> Reviewed-by:
-
danakj authored
When ThreatDetails starts up, it walks the frame tree to request the DOM details of each frame. However it also tries to request this from a RenderFrameHost that has not loaded and created a RenderFrame in a renderer process. Previously, this message would be held and eventually dropped when the RenderFrameHost is replaced in the commit of the safe browsing error page. Soon we will crash if we try to talk to a non- existent RenderFrame, so we avoid attempting to do so here. R=nparker@chromium.org Bug: 1158869 Change-Id: I394a3e1775761ec0e99cc63e7f8b3e2d194c4d73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626177Reviewed-by:
Nathan Parker <nparker@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#843569}
-
Dominique Fauteux-Chapleau authored
This is a reland of crrev.com/c/2623812 that was reverted by crrev.com/c/2628041. The issue was that enabling per-profile in unrelated tests made for a bad combination with realtime URL checks (that landed in crrev.com/c/2615779) and resulted in the browser DM token reading code being used needlessly. The fix to this is to add an optimization to ConnectorsService::GetDMTokenForRealTimeUrlCheck and check the main policy value before calling the expensive DM token reading code. Aside from that change this reland is identical to crrev.com/c/2623812. Original change's description: > Add testing config for per-profile Connectors > > A small change in ConnectorsService is required to make this test config > work. When checking analysis/reporting settings, 2 things are required > to obtain settings: a policy set to a valid value and a DM token (from > the browser or the profile). The previous implementation checked the DM > token first, meaning the blocking BrowserDMTokenStorage::RetrieveDMToken > call would trigger on multiple tests and crash them (see patchset 1 > failures for examples of this). > > The solution is to simply switch the > order of checks and read the policy first. This is also a valid > optimization of Connectors logic, as reading prefs is faster than > potentially reading the DM token from local storage. > > Change-Id: Ie1026b57cf7a4fd66663530ec2a77a72f21d6d81 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623812 > Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org> > Reviewed-by: Marc-André Decoste <mad@chromium.org> > Reviewed-by: Robert Kaplow <rkaplow@chromium.org> > Cr-Commit-Position: refs/heads/master@{#843115} Change-Id: Ie2959239571905251081c39af7cc4b124863890d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628110 Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org> Reviewed-by:
Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:
Marc-André Decoste <mad@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#843568}
-
Marc Treib authored
This CL adds the account-indication footers also for single-account and for sync users. Bug: 1121258 Change-Id: Idc78aad4ccb3ae8173adb97e3011789f174d21d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627161 Auto-Submit: Marc Treib <treib@chromium.org> Reviewed-by:
Maksim Moskvitin <mmoskvitin@google.com> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#843567}
-
Mihai Sardarescu authored
The methods OnPrimaryAccount{Set|Cleared} were replaced by OnPrimaryAccountChanged(). This CL removes them. Bug: 1158855 Change-Id: I7652904a299a9edbffb5d1ff078c54f0f1cbeb66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627390 Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Reviewed-by:Tanmoy Mollik <triploblastic@chromium.org> Cr-Commit-Position: refs/heads/master@{#843566}
-
Leonard Grey authored
Looks like I missed these in r835679 Bug: 1152274 Change-Id: I9ab585c62c753b2945b88a77ad1c3938f6693dae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626513Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#843565}
-
Michael Lippautz authored
The Oilpan library version does not require detaching manually from an Isolate as the heap is tied directly to V8's JS heap for its lifetime. Bug: 1056170 Change-Id: I61e7c9d017a523aaf4ad09430fc1e8363e2b2fc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629307 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Peter Kasting authored
Bug: 1159562 Change-Id: I236611f9223a6a9172a6b29a16ca947b43a4561d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628085 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Allen Bauer <kylixrd@chromium.org> Reviewed-by:
-
Antonio Sartori authored
This is a small refactoring of the code in blink::CSPDirectiveList which is parsing new Content Security Policies. This change separates the raw parsing of the policies from the side effects (applying the policies and storing state). This is part of a project to harmonize the CSP code in Blink and in services/network, and will make it easier to synchronize Content Security Policies between the two. Bug: 1021462,1149272 Change-Id: Iace800247ef6165a47adef2601d336a09e930897 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2601368 Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#843562}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202101140600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/DYU_0-Aok5UvqgV35z_dEgBIqBP98Ypx98hUZ8a8NcoC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll Please CC media-app@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 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: b/170172576,b/175344485,b/177365224,b/177375485,b/18961540 Tbr: media-app@grotations.appspotmail.com Change-Id: Idcf3c25bf23ced4a58cf644dcbb879717c4cff8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629395Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC chrome-fuchsia-gardener@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 Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-deterministic-dbg;luci.chromium.try:fuchsia-x64-cast Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: I87da04ea6e4088e695809d9973d1fa37a024c6c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629388Reviewed-by:
-
Elaine Chien authored
Since UNKNOWN is the least stable channel these features wouldn't work when run with official builds. Changing allowed channel to STABLE. Bug: 1165704 Change-Id: I5822c9c719cda9336bc50e39eeadb8e0b3438c24 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626915 Commit-Queue: Caroline Rising <corising@chromium.org> Auto-Submit: Elaine Chien <elainechien@chromium.org> Reviewed-by:
Caroline Rising <corising@chromium.org> Cr-Commit-Position: refs/heads/master@{#843559}
-
Rushan Suleymanov authored
This metrics shows fullness of the full title field in specifics. Since most of bookmarks were reuploaded, this metric is not needed anymore. Bug: 1153774 Change-Id: Iacc69717212f6ec41cd327c6a0ade0f677768d32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2600831Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Commit-Queue: Rushan Suleymanov <rushans@google.com> Cr-Commit-Position: refs/heads/master@{#843558}
-
David Roger authored
Local profile: https://drive.google.com/file/d/1GH_DmqD-A0bVU-ebZND96-vGN5ao7_fZ/view?usp=sharing&resourcekey=0-WGPrVjdN2hJcXBJ7YVwE2w Signedin profile: https://drive.google.com/file/d/1cK0pYOunr_j6sS84bgJDlC6-6fi_WyRJ/view?usp=sharing&resourcekey=0-o_2bkNB9RiJtxxTVAWDOSQ Fixed: 1166653 Change-Id: I46365046e2a940951088f77367a4cb47ded0d1c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628295 Auto-Submit: David Roger <droger@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Commit-Queue: Alex Ilin <alexilin@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#843557}
-
Adithya Srinivasan authored
Bug: 1166659 Change-Id: Ifcfae51d6b5bf6d43435e55774aad3e503165b6f Tbr: tellier@google.com Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628134Reviewed-by:
Andy Paicu <andypaicu@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#843556}
-
David Maunder authored
Speedup: 48997ms -> 21318ms (56% speedup) Bug: 1166399 Change-Id: I296c5c40d9136a816c8b881c904f19b5baa1e5bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627629Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Commit-Queue: David Maunder <davidjm@chromium.org> Cr-Commit-Position: refs/heads/master@{#843555}
-
David Maunder authored
Speedup: 4500ms -> 1810ms (61% improvement) Bug: 1166382 Change-Id: I75839a35b02373bf31235c05aef3cc2bd2b6c74f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628314Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: David Maunder <davidjm@chromium.org> Cr-Commit-Position: refs/heads/master@{#843554}
-
Benjamin Beaudry authored
Elements with the listitem role should always expose their accessible names with UIA. This was causing an issue with Narrator on Windows when navigating by list item - Narrator would only announce "element x of N" when it should actually announce "[listitem name], element x of N". This is per spec: https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-listitem-control-type Bug: N/A Change-Id: I4f2d1a999d00cc8f5b23989d3ade90c907764152 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610264Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Reviewed-by:
Victor Fei <vicfei@microsoft.com> Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Commit-Queue: Benjamin Beaudry <benjamin.beaudry@microsoft.com> Cr-Commit-Position: refs/heads/master@{#843553}
-
John Delaney authored
What: Use schemeful domain when matching the url a a conversion occurs on with conversion destinations from impressions. Why: This is the proposed mechanism in the API explainer, and allows for advertisers to track conversions across different subdomains for a single impression. How: We add a new column `conversion_destination` to the impressions table which holds the etld+1 of the conversion destination. This column is used when attributing impressions for a conversion and deactivating impressions instead of `conversion_origin`. `conversion_origin` is still used for data remover integrations. All existing impressions are updated with an associated conversion domain, so there will be no data loss across the migration, but slight behavior changes are expected. When a conversion is received, we now associate it with the etld+1 of the top-level frame where it was received instead of the origin. This adds a new migration mechanism for ConversionStorage, including a MetaTable to store the current database version and a test suite. Much of the migration logic and testing follows WebDatabase: https://source.chromium.org/chromium/chromium/src/+/master:components/webdata/common/web_database_migration_unittest.cc;l=1 This does not yet update information in the conversion-internals page, which will be left for a follow-up CL. Bug: 1131624 Change-Id: I41e5d61930beab5278fe3fc3f3e40e0369e553d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2194182 Commit-Queue: John Delaney <johnidel@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Weilun Shi <sweilun@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#843552}
-
