- 16 Nov, 2020 40 commits
-
-
Victor Hugo Vianna Silva authored
Before this CL, sign-out would clear the pref representing whether Sync should be decoupled from the Android master sync toggle. This CL removes the clean-up logic and also makes sure that the pref is set whenever ProfileSyncService detects there's no syncing account (either on browser startup, or after sign-out). Indeed, by the time the DecoupleSyncFromAndroidMasterSync feature is enabled, only users who were already syncing but had the master toggle disabled should remain in the coupled state. Bug: 1105795 Change-Id: If5e36080159150fe976885b469696103df890ed4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2539202 Commit-Queue: Victor Vianna <victorvianna@google.com> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#827887}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/9f94f31cc09d..5160aada22ed 2020-11-16 brianosman@google.com Test and implement all "common" intrinsics (GLSL ES Sec. 8.3) 2020-11-16 scroggo@google.com Reland "SkAndroidCodec: Support decoding all frames" 2020-11-16 jvanverth@google.com Add activation events to sk_app. 2020-11-16 borenet@google.com [infra] Mac VMs running NativeFonts tasks were updated 2020-11-16 johnstiles@google.com Convert remaining Metal tests to golden outputs. 2020-11-16 robertphillips@google.com Allow gpu_blur_utils* GMs to run with *ooprddl configs 2020-11-16 jvanverth@google.com Add product bundle name to iOS Xcode projects 2020-11-16 robertphillips@google.com Remove SkBaseDevice::flush If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC lovisolo@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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: lovisolo@google.com Change-Id: I6e6ac75f8fa50fef82f9f0054b631701d755f1ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541043Reviewed-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@{#827886}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c4294f0266f1..a73ba689e695 2020-11-16 futhark@google.com Change ::selection backgrounds according to Blink fix 2020-11-16 aerotwist@chromium.org TypeScriptify ObjectPropertiesSection.js 2020-11-16 aerotwist@chromium.org TypeScriptify TimelineGrid.js 2020-11-16 tvanderlippe@chromium.org Use TypeScript-authored files in sources/ 2020-11-16 tvanderlippe@chromium.org Update `@typescript-eslint` packages 2020-11-16 tvanderlippe@chromium.org Typecheck object_ui/RemoteObjectPreviewFormatter.js with TypeScript 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:1011811,chromium:1018450,chromium:1149259 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I322ad5822614ad186f650359575573116214d810 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541444Reviewed-by:
-
David Tseng authored
Fixes more DEPS violations; make sure it passes buildtools/checkdeps/checkdeps.py chrome/browser/chromeos/input_method which doesn't appear to be run on presubmits. TBR=avi@chromium.org, shend@chromium.org Original change description: https://chromium-review.googlesource.com/c/chromium/src/+/2538141 - fix the regex that was matching against .*(...|)\.(cc|h) (aka all *.cc, *.h). - add a rule for dependees of tts_controller.h with commentary. Bug: 1148093, b/173144152 Change-Id: I193b4bd9d1122223fae8fddb570dc182f0607283 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541725Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#827884}
-
Mario Sanchez Prada authored
This call is no longer needed since crrev.com/c/1757935, so it's safe to remove it along with all the production & test code related to it. Bug: 1039252 Change-Id: Ib30f0d43b6d33ebfbbde1eca205fc26c31874118 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2539196Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Cr-Commit-Position: refs/heads/master@{#827883}
-
Mario Bianucci authored
Calling saveLayer() on the canvas before drawing the delegated ink trail is unnecessarily expensive - it allocates a temporary buffer for the path to be drawn into for resolving and layer blending that may need to occur. However, since there is only one trail, this isn't required, and we can instead just use clipRect to ensure the trail is clipped to the bounds of the presentation area. Bug: 1148533 Change-Id: Id60d1def6215616f65838aae05658317c8fcd372 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536086Reviewed-by:
Michael Ludwig <michaelludwig@google.com> Reviewed-by:
weiliangc <weiliangc@chromium.org> Commit-Queue: Mario Bianucci <mabian@microsoft.com> Cr-Commit-Position: refs/heads/master@{#827882}
-
Vyshu authored
Add GetDlcState method to client as well as fake client and associated unittests. TEST=b:172223380 BUG=autoninja -C out/Default/ unit_tests && ./out/Default/unit_tests --gtest_filter=*Dlc* dlcservice: Change-Id: I6f26c75e7d73447d14e724558a1f381198de88d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540367Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Vyshu Khota <vyshu@google.com> Cr-Commit-Position: refs/heads/master@{#827881}
-
Matthias Körber authored
Change-Id: I11905913c5ed540f08ec9a290363951c83bf2a34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540471 Auto-Submit: Matthias Körber <koerber@google.com> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#827880}
-
minch authored
Only elements in "Dark theme" detailed view got live updated. We can add other elements later if necessary. See recorded video: https://drive.google.com/file/d/1L9WIaefJsmYZJkZ7dToIaamAItd0H0op/view?usp=sharing&resourcekey=0-TTa-8PRjR8KdAcQzVAC5UQ Bug: 1131543 Change-Id: Id68fcb43eb1c5a3a748e409e2020fd7b1ede9f50 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2539437Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Min Chen <minch@chromium.org> Cr-Commit-Position: refs/heads/master@{#827879}
-
spdonghao authored
Bug: 1148813 Change-Id: Ia4ec5c44f8e00d2af18f5a161f3bfe1c84a1d9f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2537115 Commit-Queue: Hao Dong <spdonghao@chromium.org> Reviewed-by:
Xi Han <hanxi@chromium.org> Reviewed-by:
Patrick Noland <pnoland@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Cr-Commit-Position: refs/heads/master@{#827878}
-
Jarryd authored
Quota.PercentUsedForTemporaryStorage2 and Quota.DaysBetweenRepeatedOriginEvictions extended by one year. Bug: 1140094 Change-Id: I539b0f3b045912db601ced6326ee76ec6f257e0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541125 Auto-Submit: Jarryd Goodman <jarrydg@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#827877}
-
David Bienvenu authored
The underlying issue is that the kProfilesLastActive pref gets cleared when Chrome is launched with a specific profile, which prevents Chrome from iterating over the last active profiles and calling session restore on each of them. This CL stops clearing the pref when launched with --app-id, and avoids restoring sessions for the last active profiles if launched with --app-id. Also, ignore browser opens and closes if the browser window is for a web app, in order to prevent kProfilesLastActive pref from getting overwritten. Bug: 1022795 Change-Id: I350a54eaaf167dabb297b9bda9061fe965f0750e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1984710Reviewed-by:
Greg Thompson <grt@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Commit-Queue: David Bienvenu <davidbienvenu@chromium.org> Cr-Commit-Position: refs/heads/master@{#827876}
-
Miguel Casas authored
This reverts commit 2ca0c46b. Reason for revert: broke some Tast tests https://crbug.com/1149134 Bug=1149134 Original change's description: > media/gpu/vaapi: reduce encoding quality on low power ChromeOSes > > This CL queries the driver for the encoding quality range and, if > available and the device is considered "low power" (celeron, pentium > and Core -Y devices), sets it to its maximum value, for highest speed > and lowest power consumption, albeit at lower encoding quality. The > quality difference should not be noticeable for video conference > scenarios. > > I followed the code in both of Intel's VA backends. > For the legacy i965: > - VP8 supports values 1-2 [1]. (ENCODER_LOW_QUALITY is 2 so at least > this CL can supersede the patch in [2] which is what it was set off to > do). > - AVC1 and VP9 support 1-7 [3,4], ENCODER_QUALITY_RANGE_(AVC,VP9) == 7 > see [5], but this only on Gen9 [6a, 6b] (VP9 encoding is only > available in Gen9+ FTR). > > For the modern intel-media-driver iHD, values are configured with > names, 1 being TARGETUSAGE_BEST_QUALITY ([7] and its following lines). > By default, the TARGETUSAGE_RT_SPEED == 4 is used, and 7 would be > TARGETUSAGE_BEST_SPEED. > > Improvements depend on the input content. I measured kohaku with > EncodeAccelPerf.h264_1080p_i420 and when ToT is ~204fps, 4.75W, with > this CL I see ~220 fps, 4.42W. > > [1] https://github.com/intel/intel-vaapi-driver/blob/d87db2111a33b157d1913415f15d201cc5182850/src/i965_drv_video.c#L1151 > [2] https://source.chromium.org/chromiumos/chromiumos/codesearch/+/master:src/third_party/chromiumos-overlay/x11-libs/libva-intel-driver/files/vp8-encoder-Workaround-to-force-perforamce-mode-enco.patch;l=36 > [3] https://github.com/intel/intel-vaapi-driver/blob/d87db2111a33b157d1913415f15d201cc5182850/src/i965_drv_video.c#L1142 > [4] https://github.com/intel/intel-vaapi-driver/blob/d87db2111a33b157d1913415f15d201cc5182850/src/i965_drv_video.c#L1149 > [5] https://github.com/intel/intel-vaapi-driver/blob/021bcb79d1bd873bbd9fbca55f40320344bab866/src/i965_drv_video.h#L76 > [6a] https://github.com/intel/intel-vaapi-driver/blob/021bcb79d1bd873bbd9fbca55f40320344bab866/src/i965_encoder.c#L1599 > [6b] https://github.com/intel/intel-vaapi-driver/blob/021bcb79d1bd873bbd9fbca55f40320344bab866/src/i965_encoder.c#L1653 > [7] https://github.com/intel/media-driver/blob/105f0341a21324ae3bc458cfa6c25c7df0517f3a/media_driver/agnostic/common/codec/shared/codec_def_common.h#L333 > > Bug: b:141147405 > Change-Id: I7e5c54f1e5a7ac7a51c5503f37168db16f9e99f7 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2344526 > Commit-Queue: Miguel Casas <mcasas@chromium.org> > Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org> > Reviewed-by: Sreerenj Balachandran <sreerenj.balachandran@intel.com> > Reviewed-by: Hirokazu Honda <hiroh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#827439} TBR=mcasas@chromium.org,hiroh@chromium.org,andrescj@chromium.org,sreerenj.balachandran@intel.com,sreerenj.balachandran@intel.corp-partner.google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: b:141147405 Change-Id: I343cb03a094c5e58f77a8f734b7eac2b0ecb51bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541744Reviewed-by:
Miguel Casas <mcasas@chromium.org> Commit-Queue: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#827875}
-
Adrienne Walker authored
This is a little bit awkward for native file system handles, which aren't related to blob writing failures. However, these are already returned as "failure to write blobs", so it's not too far afield. Bug: 1144131 Change-Id: I800445b39a93e7fda9d36480092d2cff55760f94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538155 Commit-Queue: enne <enne@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Auto-Submit: enne <enne@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#827874}
-
Corentin Wallez authored
The PSA in https://hackmd.io/uH1MI9cnQBG9GGOZG20COw deprecates a number of WebGPU APIs. Now that we are past the removal deadline we can remove them from Blink and only keep the supported paths. Bug: dawn:22 Change-Id: I9241e78db5578d6cb97593e9e3363b493fed481c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521120 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org> Auto-Submit: Corentin Wallez <cwallez@chromium.org> Reviewed-by:
Austin Eng <enga@chromium.org> Cr-Commit-Position: refs/heads/master@{#827873}
-
Mark Pearson authored
This reverts commit aa74ca79. Reason for revert: Due to a bug in the original changelist, these histograms were never emitted. In particular, they weren't emitted because the implementation classes (the ones that actually emit the metrics) aren't part of the class. In other words, they're not overriding the parent class behavior and thus not getting called. When I fixed the bug and tested the fix, I realized that the way I hooked up the metrics emitting code is wrong. I expected the UnsentLogs.Sent-emitting code to be run only when persisted logs (logs from past sessions) were going to be sent. However, it records all logs that are sent, not only persisted ones. For example, it records (i) the initial stability log and (ii) the logs that happen at regular intervals. Neither of those are counted in UnsentLogs.IntendingToSend. Long story short: bug in original changelist. Fixing the bug is non-trivial and requires substantial changes. Reverting to start over fro a clean slate. Reverting the histograms.xml change is safe because these histograms were never logged. BUG=1148523 Original change's description: > Add Metrics about Uploading UMA Records from Previous Sessions > > Change-Id: I908a337129062e882b185a08329fecfd7db6c496 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2504593 > Reviewed-by: Steven Holte <holte@chromium.org> > Commit-Queue: Mark Pearson <mpearson@chromium.org> > Cr-Commit-Position: refs/heads/master@{#822037} TBR=mpearson@chromium.org,holte@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: Ie44b8bac5948cb19af245800ac42e6b5bab11996 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2537604Reviewed-by:
-
dpapad authored
The logo image was accidentally only included for optimize_webui=false at r827003. Bug: 1149235 Change-Id: Ie6a965529e9d31cebcffc0a75672b3a505cc6411 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538397 Commit-Queue: dpapad <dpapad@chromium.org> Auto-Submit: dpapad <dpapad@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#827871}
-
Christopher Cameron authored
This function used to use the helper functions CopyToByteArray and ConvertPixelsFromCanvasPixelFormatToImageDataStorageFormat to first copy the data, then the convert formats. The function PaintImage::readPixels can do the copy and conversion simultaneously. Use that instead. Add the capability to read to uint16 (as well as uint8 and float16), since getImageData will be changed to allow specifying the type. Remove a bunch of unused helper functions left behind. Bug: 1115317 Change-Id: I88e637c2f314385c62b1a450ea2c0c9e7fc29ad9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533833Reviewed-by:
Yi Xu <yiyix@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#827870}
-
Angus L. M. McLean IV authored
Bug: 1071218 Change-Id: I79da1693562db63262084853b1d3c35cdb97518e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2537936 Commit-Queue: Angus McLean <angusmclean@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#827869}
-
Peter Kvitek authored
This is required because inbound Mojo messages which do not have a registered handler are considered an error, and the render process is terminated. Bug: 1090429 Change-Id: I6979013e55a32f30bb32f2918df5fde8ba852dbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2530198 Commit-Queue: Peter Kvitek <kvitekp@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Chris Mumford <cmumford@google.com> Cr-Commit-Position: refs/heads/master@{#827868}
-
Sigurdur Asgeirsson authored
ScopedObserver is being deprecated in favor of two new classes: - base::ScopedObservation for observers that only ever observe a single source. - base::ScopedMultiSourceObservation for observers that do or may observe more than a single source. This CL was uploaded by git cl split. R=djacobo@chromium.org Bug: 1145565 Change-Id: I436bf817ddb0820060ddcc817c324cf2ae5c9cee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532715Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
David Jacobo <djacobo@chromium.org> Commit-Queue: David Jacobo <djacobo@chromium.org> Auto-Submit: Sigurður Ásgeirsson <siggi@chromium.org> Cr-Commit-Position: refs/heads/master@{#827867}
-
manukh authored
Does not add logging for split rich autocompletion, only title and non-prefix autocompletion. Will only trigger if a rich autocompleted suggestion is actually the default suggestion during a session as otherwise they have no impact. Bug: 1062446 Change-Id: Idd6f11f94195fdae76a78dde70ec57f8725601ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465804Reviewed-by:
Tommy Li <tommycli@chromium.org> Commit-Queue: manuk hovanesian <manukh@chromium.org> Cr-Commit-Position: refs/heads/master@{#827866}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/8dceaddf8503..3e551b3ce67d 2020-11-16 capn@google.com Work around LLVM ORCv2 issue affecting Cuttlefish If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I5b1c2ecbe4247ea94d638da74ac9cfcf70d1650a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541102Reviewed-by:
-
cfredric authored
Change-Id: Ic2fdb5d1adb515af42735a7af1b563dd0aba8ed1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540571 Commit-Queue: Chris Fredrickson <cfredric@chromium.org> Reviewed-by:
Lily Chen <chlily@chromium.org> Cr-Commit-Position: refs/heads/master@{#827864}
-
Jeffrey Young authored
Previously monitored prefs only if ambient mode was already enabled. BUG=b:169579102 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Change-Id: I287ab1e710b8c45b6fb2b90ba6879fb5726fc2f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535111 Commit-Queue: Jeffrey Young <cowmoo@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by:
Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/heads/master@{#827863}
-
Clark DuVall authored
This change kicks off native library loading as early as possible in a separate thread, to reduce startup latency. There may be a few activities that don't actually need native libs, but the vast majority of the time we end up loading the native lib, and this seems like a good trade off for the perf improvements. Pinpoint results for messageloop_start_time in mobile.startup: Android Go: Cold start: -11.3% https://pinpoint-dot-chromeperf.appspot.com/job/10e6fbf3520000 Warm start: -23%: https://pinpoint-dot-chromeperf.appspot.com/job/1227a4cd520000 Pixel 2: Cold start: -0.3% https://pinpoint-dot-chromeperf.appspot.com/job/11822b23520000 Warm start: -1.7% https://pinpoint-dot-chromeperf.appspot.com/job/154a85cb520000 Bug: 1148803 Change-Id: I70256509cad47c20ec047222ba7bd0f576abe548 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535732 Commit-Queue: Clark DuVall <cduvall@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#827862}
-
Keishi Hattori authored
When using a binary operand with CheckedPtr and std::string, you get an invalid operands to binary expression error. With this CL, the rewriter matches CheckedPtr used with a std::string and adds .get() so the std::string/char* operator overrides gets used. Bug: 1073933 Change-Id: I4854d4d272ba1d9a107e7e346bfbe363e6861c06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535908Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/master@{#827861}
-
Etienne Bergeron authored
This CL is adding code coverage with unittests for whitespace elision. The intend is to ensure the code semantic stay the same while doing the eliding refactoring. R=gab@chromium.org,msw@chromium.org Bug: 1085014 Change-Id: I8a092e8d2c15449e80ba0508c854aca71dd7892d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533533 Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#827860}
-
Leonard Grey authored
This reverts commit bbf9dd65. Reason for revert: new test is failing on at least a few (maybe all) Mac builders. Example: https://ci.chromium.org/p/chromium/builders/ci/Mac10.12%20Tests/39329 Original change's description: > Portals: Fix a11y for orphaned portals > > Orphaned portals [1] don't have a RWHV (but did at some point), and can > have AXTree updates sent from its renderer process which would be > subsequently ignored in the browser process (due to there being no RWHV). > Once an orphaned portal is inserted into the DOM tree, we create a RWHV > for it, and at this point any new AXTree updates received will be invalid > as the browser's tree state is different from the renderer's. > > To fix this, this CL makes BrowserAccessibilityManager creation > independent of a view being present. The view is only used on android > to pass it a pointer to WCAXAndroid, and we now do this through > a BrowserAccessibilityDelegate method. > > [1] See "orphaned" here: https://wicg.github.io/portals/#concepts > > Bug: 1139784 > Change-Id: Ifdebe1f05e37a6f704b937101ea44bb824cf045b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2499861 > Commit-Queue: Adithya Srinivasan <adithyas@chromium.org> > Reviewed-by: Aaron Colwell <acolwell@chromium.org> > Reviewed-by: Kevin McNee <mcnee@chromium.org> > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > Cr-Commit-Position: refs/heads/master@{#827803} TBR=dmazzoni@chromium.org,acolwell@chromium.org,adithyas@chromium.org,mcnee@chromium.org Change-Id: I617e4b9e6a56fd3c23b56f7620df9206628d4030 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1139784 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541647Reviewed-by:
Leonard Grey <lgrey@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#827859}
-
Kevin Ellis authored
The CompositeRelativeKeyframes feature was turned on in stable in the following CL. https://chromium-review.googlesource.com/c/chromium/src/+/2495604 This change introduced a regression (crbug.com/1149012) in which the animation onfinished event is not being fired. Disabling the feature while we determine why the event is not firing. Bug: 1149012, 389359 Change-Id: Ibe789132f0782fa12b129045777c53bd46596697 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540568Reviewed-by:
Robert Flack <flackr@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#827858}
-
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: I31d070f7b47d676076dd5c7d2bc7ce69004340a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540368Reviewed-by:
-
Ben Pastene authored
To hopefully help avoid high pending times -> low cache hit -> increased build durations. crrev.com/i/3402719 allocates the machines for this builder. Bug: 1140727 Change-Id: Ieb64b7e2a9ea829540d42878d0adb3f8b6c98eb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540922Reviewed-by:
Haiyang Pan <hypan@google.com> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#827856}
-
Sigurdur Asgeirsson authored
ScopedObserver is being deprecated in favor of two new classes: - base::ScopedObservation for observers that only ever observe a single source. - base::ScopedMultiSourceObservation for observers that do or may observe more than a single source. This CL was uploaded by git cl split. R=rushans@google.com Bug: 1145565 Change-Id: I760ad7d03410e304b00db5497fb44120e9768fd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532959 Auto-Submit: Sigurður Ásgeirsson <siggi@chromium.org> Commit-Queue: Rushan Suleymanov <rushans@google.com> Reviewed-by:
Rushan Suleymanov <rushans@google.com> Cr-Commit-Position: refs/heads/master@{#827855}
-
Ian Kilpatrick authored
This block-stretching logic as: https://chromium-review.googlesource.com/c/chromium/src/+/2513771 ... did for the inline-axis. Previously we didn't have the concept of "stretching" the block-axis instead relying on the parent layout algorithm to set a fixed block-size. This allow stretching (similar to the inline-dimension). The failing tests (which I'll update in the test expectations) are due to this specification issue: https://github.com/w3c/csswg-drafts/issues/5713 The changes in layout_replaced.cc are needed to transfer the stretched size through the aspect-ratio. Bug: 1045599 Change-Id: Ifdd8653d81a1ead84a0afbf5ebd31ba0b75dc8ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523743 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Kurt Catti-Schmidt <kschmi@microsoft.com> Reviewed-by:
David Grogan <dgrogan@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#827854}
-
Austin Eng authored
--enable-toggles=skip_validation,foo,bar is the new way to enable toggles in Dawn's tests. The other command line flags will be removed. Bug: dawn:571 Change-Id: Ia917943fb07abb53346ffe0022ff27b01db6f4db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538482Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org> Cr-Commit-Position: refs/heads/master@{#827853}
-
Wan-Teh Chang authored
Change AVIFImageDecoder::OnSetData() to parse the image metadata automatically when all data is received. This meets the expectations of ImageFrameGenerator::GetYUVAInfo() and ImageFrameGenerator::DecodeToYUV(). In the ReadYUV() function in avif_image_decoder_test.cc, change the IsSizeAvailable() call (which calls DecodeSize()) to IsDecodedSizeAvailable() (which has no side effects) and call a few more getter methods related to DecodeToYUV() to emulate the code in ImageFrameGenerator::GetYUVAInfo() and ImageFrameGenerator::DecodeToYUV(). Bug: 1149144 Bug: 1136922 Change-Id: I3790de99fd0e9745c4b3ab9555aa027f25a6d374 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2539329Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Wan-Teh Chang <wtc@google.com> Cr-Commit-Position: refs/heads/master@{#827852}
-
Boris Sazonov authored
This reverts commit dbf8c7e8. Reason for revert: caused crashes and test failures (https://crbug.com/1149348, https://crbug.com/1149382). Original change's description: > [ToolbarMVC] Move child coordinator initialization and ownership to LBC > > This puts LocationBarCoordinator in charge of constructing and > destroying UrlBarCoordinator, StatusCoordinator, and > AutocompleteCoordinator. This allows us to wire a few more > dependencies into constructors instead of via setters. The > coordinators are still passed to LocationBarLayout for it to use via > a new initialize() method that consolidates a few different setter > methods on LocationBarLayout. initialize() helps avoid bugs that > could arise when calling these setters out of order. There is an > additional change to LocationBarLayoutTest that fixes a DCHECK when > running tests on a debug build. > > Bug: 1146057, 1146062 > > Change-Id: Ie6c7e871d6cb0eb4bbffff0ab3ed275968d84e85 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495969 > Commit-Queue: Patrick Noland <pnoland@chromium.org> > Reviewed-by: Ted Choc <tedchoc@chromium.org> > Reviewed-by: Filip Gorski <fgorski@chromium.org> > Reviewed-by: Tomasz Wiszkowski <ender@google.com> > Reviewed-by: Peter Conn <peconn@chromium.org> > Cr-Commit-Position: refs/heads/master@{#827494} TBR=fgorski@chromium.org,tedchoc@chromium.org,peconn@chromium.org,pnoland@chromium.org,ender@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1146057, 1146062, 11493484, 1149382 Change-Id: Ie6578c072ab9bc1d5da8f9a5e29676ba3321442d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540587 Commit-Queue: Patrick Noland <pnoland@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/master@{#827851}
-
Brandon Wylie authored
mocks: https://www.figma.com/file/b1CT6jM3mj0MdBvgQicy4b Bug: 1117271 Change-Id: I67cba57fce298e5ddf83edef10d331ee136cf289 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538356Reviewed-by:
-
Mike Dougherty authored
CRWContextMenuController was previously used with WKWebViews which were not associated with a WebState. This added complexity to the context menu feature which is no longer necessary. Bug: None Change-Id: I8c07675da49dd0a9cf07b14e9b14ce73d14c9ebd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523754 Commit-Queue: Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#827849}
-
Leonard Grey authored
This reverts commit 11191b81. Reason for revert: Causing checkdeps failures on linux-trusty-rel Example: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8863455424170691152/+/steps/checkdeps/0/stdout Original change's description: > Correct c/b/c/input_method/DEPS > > - fix the regex that was matching against .*(...|)\.(cc|h) > (aka all *.cc, *.h). > - add a rule for dependees of tts_controller.h with commentary. > > Bug: 1148093, b/173144152 > > Change-Id: I0e1ca36fdeec5e838fa845f6f9520d130f11a68d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538141 > Reviewed-by: Darren Shen <shend@chromium.org> > Reviewed-by: Avi Drissman <avi@chromium.org> > Commit-Queue: David Tseng <dtseng@chromium.org> > Cr-Commit-Position: refs/heads/master@{#827804} TBR=avi@chromium.org,dtseng@chromium.org,shend@chromium.org Change-Id: I102b9b65dfb5e34b0c6a24b5f8baec0c02ae645d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1148093 Bug: b/173144152 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541922Reviewed-by:
-
