- 21 Aug, 2020 40 commits
-
-
Garrett Beaty authored
Separating the branch configuration by file has been rather unwieldy and would only get worse when it is necessary to maintain a 3rd subset of builders for LTS. This puts the information about what branches the LUCI resources are applicable to with the resource. Bug: 1119446 Change-Id: I1c8622b7084fd332ae16fcdc9afe5d6e30dc1811 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365915 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Erik Staab <estaab@chromium.org> Cr-Commit-Position: refs/heads/master@{#800627}
-
OlivierLi authored
The nested loop process the native events but not the tasks which looks like a hang if not inhibited. Bug: 806174, 1120381 Change-Id: Ie298b16a4e0f8cdd6c4ba398d71a7fee02b9d46d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369253Reviewed-by:
Robert Liao <robliao@chromium.org> Commit-Queue: Robert Liao <robliao@chromium.org> Commit-Queue: Oliver Li <olivierli@chromium.org> Cr-Commit-Position: refs/heads/master@{#800626}
-
Andreea Bacanu authored
Make ClosedTabCache listen to MemoryPressure listener and flush the cache if the memory pressure level is critical. Design doc: https://docs.google.com/document/d/1SF230MYWgroe4WikDMn82ETd3-HFRzylKtIk0HZRaOU/edit?usp=sharing BUG=1100946 Change-Id: I73afb124ab596ae9bd9db1bed84684088c174096 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352942Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Sreeja Kamishetty <sreejakshetty@chromium.org> Commit-Queue: Andreea Bacanu <aebacanu@chromium.org> Cr-Commit-Position: refs/heads/master@{#800625}
-
dpapad authored
Bug: 1062154 Change-Id: I9c0550e34d6c88ab8a9db4d546852349bc9740d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368920Reviewed-by:
John Lee <johntlee@chromium.org> Commit-Queue: dpapad <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#800624}
-
Maksim Sisov authored
While fixing tests that started to fail with use_x11 && use_ozone config, I encountered some additional expectations that were not part of USE_X11 builds before. And given that we are heading towards use_x11 && use_ozone build, we need to continue to run tests and other stuff as it'd be a single use_x11 build. Also, it seems like our Ozone clipboard impl is more advanced than non-Ozone/X11. Thus, disable this expectation for x11. Bug: 1085700 Change-Id: I01f27f213f595ae5d635fa76d68164a8a178141b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367061Reviewed-by:
-
Ken Rockot authored
Rather than CHECK-failing before transmitting a message, this adds a DumpWithoutCrashing at serialization time. This will preserve useful crash stacks to identify offending messages but will no longer result in the poor user experience of crashing processes, including the browser. Fixed: 1098442 Change-Id: I638410f4787e833e9cb92573f26e9e7167d1bec7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365852 Commit-Queue: Ken Rockot <rockot@google.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#800622}
-
Sangwoo authored
']' was appended accidentally. Bug: None Change-Id: I5e07be3848a4b8b2483f8e2a7e61126ae8eeefb6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368696 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#800621}
-
Miguel Casas authored
This CL increases the SDR luminance (on HDR-capable systems and with an HDR-capable display) to 85%, following instructions from the PM office amd also to line up with Apple's maximum SDR value (equivalenty, HDR headroom) when brightness is at the max. Bug: b:165824699 Change-Id: I1bbfbba3512d87f84c26e5acc71cfd8f59a07e48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367872 Commit-Queue: Miguel Casas <mcasas@chromium.org> Auto-Submit: Miguel Casas <mcasas@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#800620}
-
Maksim Sisov authored
we seem to miss some test coverage for non-ozone X11. currently, non-ozone X11 uses dndclient ozone and should also run tests for that. though, two tests fail. thus enable the test suite for use_x11 and disable failing tests. A bug to fix the failures has also been created Bug: 1085700 Change-Id: I9a669f18d8e5affc71d5b1e8c21e48f3b8a1765b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366898Reviewed-by:
-
kylechar authored
For pixel tests with a single parameter for renderer type, implement improved test name suffixes. For example, the test name "RendererPixelTest.SimpleGreenRect/1" might become "RendererPixelTest.SimpleGreenRect/SkiaGL" which indicates the test uses SkiaRenderer with the GL backend. Bug: 1047820 Change-Id: I18b8cbc29313b4d05ecfda020c310caa548f22fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367439 Commit-Queue: kylechar <kylechar@chromium.org> Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#800618}
-
Noah Rose Ledesma authored
As the default device will fallback to one of the other devices listed in the audio device picker. We should avoid showing the default device when we know which of the other devices it falls back to. Due to complications with how the default device is reported by PulseAudio, it is not possible to reliably know which device default falls back to on Linux. Hence, on Linux the default device will still be shown. Bug: 1118193 Change-Id: I6c7d3a6f23d9cd7d2963f9e72e9b140f70bbb231 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363256Reviewed-by:
Tommy Steimel <steimel@chromium.org> Commit-Queue: Noah Rose Ledesma <noahrose@google.com> Cr-Commit-Position: refs/heads/master@{#800617}
-
Dirk Pranke authored
This CL was initially generated by //tools/gn/roll_gn.py and picks up the following changes: https://gn.googlesource.com/gn/+log/e327ffdc..6f13aaac 6f13aaac [visibility] Consider configs in visibility check 5da62d5e Fix native MinGW build 0649bd9a Add MSYS as a platform. 501b49a3 clang: Add support for C++ modules in deps 03df22eb [rust-project] Add "proc_macro" as dep for proc macro targets b489f906 Add support for Solaris and illumos systems 6f13aac is a breaking change, in that it addresses gn bug #22, where `visibility` was not actually enforced on configs (it was enforced only on targets); as a result, we have some visibility violations that are now picked up with the new GN binary. This CL fixes those violations. Change-Id: I52b6e01f31ce64c1926e97b699b7f8a399dbf9f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360685 Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#800616}
-
Yunke Zhou authored
Bug: 1101318 Change-Id: I7297f1522333927db4c14609c57747f79fe87829 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366737Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Yunke Zhou <yunkez@google.com> Cr-Commit-Position: refs/heads/master@{#800615}
-
Nate Chapin authored
This case is specific to when window.open() is used, then the opener write()s into the newly opened document and adds a <meta refresh> tag with the refresh url set to the opener's url. When document.write() is called from another document, the targeted document's url is updated to the caller's url. Therefore, the act of writing the <meta> into the newly opened window causes the opener and the opened window to have the same url. Because the <meta refresh>'s url matches the current one, it is flagged as a reload, rather than as a redirect to a new url. However, the browser process has not seen a commit in the newly opened window, so it gets confused and refuses to update the url for a reload when a reload shouldn't be possible. This CL detects that case and ensures that it is treated as a non-reload navigation, which ensures the state sent to the browser process is coherent. Bug: 1112815 Test: http/tests/history/document-write-meta-refresh-in-opened-window.html Change-Id: Ie665bdf40435728bf6bd4fae5ed8ffda99014800 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359377 Commit-Queue: Nate Chapin <japhet@chromium.org> Reviewed-by:
-
Eugene But authored
Swap product name and version calls as expected in function signature Bug: 1103752 Change-Id: I9e21b8c57c6134aee6d66c0e9685146876ee7c16 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368242 Auto-Submit: Eugene But <eugenebut@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Commit-Queue: Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Cr-Commit-Position: refs/heads/master@{#800613}
-
Ian Kilpatrick authored
There should be no behaviour change. Change-Id: Ic6d5d5d2ccebbaf2e8ef3bd72a89f9cf50b88add Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368440Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Mason Freed <masonfreed@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#800612}
-
Sami Kyostila authored
(Reland of https://chromium-review.googlesource.com/c/chromium/src/+/2332664) Chrome and WebView have supported basic Android ATrace tracing, but the current approach has some shortcomings: 1) Android R changes the way atrace session activations are broadcast, breaking the code in WebView listening for activations (OnTraceEnabledChangeListener). This means you can't trace a running WebView app with atrace. 2) Neither Chrome nor WebView record early startup events to atrace, which means all events before the native library has loaded are lost. 3) It's not possible to specify trace categories via atrace, which means we need more cumbersome alternative solutions (i.e., command line flags) for startup tracing. 4) Writing ATrace events is only supported in WebView. This patch reworks the ATrace integration to resolve these problems and to align the Chrome and WebView implementations. In short, ATrace session management is moved to the common (TraceEvent) layer, and Chrome and WebView only differ by which trace tags they listen to (APP vs. WEBVIEW). We also add a way to declare trace categories through per-app tags: $ atrace -a org.chromium.chrome,org.chromium.chrome/<category_filter> (Note that the plain package name without any category filters must always appear in the list on its own.) Multiple categories can be separated with a double colon: $ atrace -a org.chromium.chrome,org.chromium.chrome/cat1:cat2 Or by specifying the the app several times to get around the 91 character limit for each entry: $ atrace -a org.chromium.chrome,\ org.chromium.chrome/cat1,\ org.chromium.chrome/cat2 Finally, to capture Java startup events into a tracing session controlled by the system's Perfetto service instead of atrace, a special "-atrace" category can be used to only write events into Chrome's own tracing service instead of atrace. This way when we connect to Perfetto later in the startup sequence and establish the real tracing session, startup-related events can be flushed into that session without emitting duplicate events into ATrace. TEST=atrace -a org.chromium.chrome TEST=atrace webview TEST=atrace -a org.chromium.chrome TEST=atrace webview TEST=atrace -a org.chromium.chrome,org.chromium.chrome/-*:cc TEST=atrace -a com.google.android.gm,com.google.android.gm/-*:cc webview TEST=atrace -a org.chromium.chrome,org.chromium.chrome/-atrace Bug: 1095587, b/160768681 Change-Id: Ifc1488cc1a045bb79a804f13596935234fc7a163 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364635 Commit-Queue: Sami Kyöstilä <skyostil@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#800611}
-
Fred Mello authored
The Clank team is reviewing the ownership of all `/android` directories and updating OWNERS as part of an effort to normalize code health metrics across different data sources. https://docs.google.com/document/d/1aP5GMLwcKkdshT9YLS1dkeGAfNSNoLzdUfWvvt0qVLU Bug: 1112872 Change-Id: I58cfb139d7692f67b80694c65946bb4537380e1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368502 Auto-Submit: Fred Mello <fredmello@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#800610}
-
Leonard Grey authored
This is responsible for: - Mediating between the controller and WebUI layers. - Managing the widget the WebUI interface lives in. - Holding the web view the WebUI interface lives in. This is necessary because creating a renderer on demand caused unacceptable latency in the commander prototype. Reviewer note: Please note that there are 5 separate paths to close - Dismissed by controller via ViewModel - Dismissed by browser via Hide - Dismissed by WebUI via OnDismiss - Window closed (possibly from parent window closing) - Object destroyed I'm pretty sure they're all safe, but this part definitely needs a second pair of eyes. Bug: 1014639 Change-Id: I422754923a0be3ce3e2b7b6a500add76f7e5ecd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364225Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#800609}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c153394161f0..85132f3cbf67 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 nektar@google.com,fhorschig@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: nektar@google.com,fhorschig@google.com Change-Id: Ie9e441b50b375dcaccc8ac010c553f693f34c382 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369161Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
Friedrich [CET] <fhorschig@chromium.org> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#800608}
-
Richard Knoll authored
Opening and closing files needs to happen on a MayBlock runner. This CL introduces a NearbyFileHandler that does this. Bug: 1085067 Change-Id: I5c45f629d7fe9f6142d877f401c06fdf327eb3b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367932 Commit-Queue: Richard Knoll <knollr@chromium.org> Reviewed-by:
Alex Chau <alexchau@chromium.org> Cr-Commit-Position: refs/heads/master@{#800607}
-
yilkal authored
This cl ensures that the EDUCoexistence login ui is shown when the request for login comes from ARC++. Bug: 1118198 Change-Id: I04632fbf9d83ca2a9710f2fe5e014b2e16e9a865 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364973 Commit-Queue: Yilkal Abe <yilkal@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Anastasiia N <anastasiian@chromium.org> Reviewed-by:
Kush Sinha <sinhak@chromium.org> Cr-Commit-Position: refs/heads/master@{#800606}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/44e1791f100c..66d1f73e2c9d 2020-08-21 capn@google.com Perform independent blend state optimization 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: Ia31a537cf76db91e756ef2f278d38fbcf96fe0a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369162Reviewed-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@{#800605}
-
ckitagawa authored
The |service_| weak pointer in PaintPreviewCompositorClientImpl appears to be getting invalidated on a wrong thread in some in the wild crash reports. This CL moves the deleter of PaintPreviewCompositorClient and PaintPreviewCompositorService to always run on the default task runner this should ensure the WeakPtr is invalidated on the right thread. Bug: 1120313 Change-Id: I35f766c58c72537f96022131029008d2a0f6c603 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368462Reviewed-by:
Mehran Mahmoudi <mahmoudi@chromium.org> Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org> Cr-Commit-Position: refs/heads/master@{#800604}
-
Kevin Ellis authored
svg-x-interpolation.html was periodically flaking in debug builds due to timeouts. This patch marks the test as a long testin alignment with WPT guidelines. Bug: 1085564 Change-Id: Iffd627361de90f7301a37516a7002a5976fa77ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368015Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#800603}
-
Michael Thiessen authored
Introduce CriteriaHelper#pollUiThreadNested This change adds an assertion that pollUiThread is not called from the UI thread, which is equivalent to calling sleep(), and won't actually run any UI thread tasks. In the few cases where polling the UI Thread from the UI thread is necessary, I introduce CriteriaHelper#pollUiThreadNested, which nests the looper in order to continue running UI tasks. The reland introduces pollUiThreadForJUnit because some junit tests legitimately do need to sleep the UI thread to wait for events on other threads. Bug: 1115220 Change-Id: I09654521c0dab74f45a15b56b7876b4ee1871dd7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364085Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/7161209ef6f1..ee4fc2e01505 2020-08-21 chrome-bot@chromium.org Update config settings by config-updater. 2020-08-21 khmel@google.com arc: Add option to pin version for caches. 2020-08-21 ahassani@chromium.org auto_updater_transfer_unittest.py: Make class reference uniform 2020-08-21 ahassani@chromium.org auto_updater_transfer_unittest.py: Move class instantiator into its own class 2020-08-21 ahassani@chromium.org auto_updater_transfer_unittest.py: Rename class specific variables 2020-08-21 dburger@chromium.org Manually perform config-update from build_config.ToT.json 2020-08-20 vapier@chromium.org upload_prebuilts: rename dev-only-extras.tbz2 2020-08-20 bpastene@chromium.org cros_chrome_sdk: Use the passed in board when setting up the env. 2020-08-20 chrome-bot@chromium.org Update config settings by config-updater. 2020-08-20 vyshu@google.com auto_updater: change mode to scp for all LocalTransfer usecases 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: I1b4a0284797a0260323d368e878ee32cd5c92f7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369165Reviewed-by:
-
Yann Dago authored
Bug: 1109322 Change-Id: I73d3143fdf37e84a953da464b561f15c4ee11827 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368427 Commit-Queue: Yann Dago <ydago@chromium.org> Reviewed-by:
Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#800600}
-
Devon O'Brien authored
Add Let's Encrypt Oak 2023 and TrustAsia Logs 2020, 2021, 2022, 2023 to the list of Qualified CT Logs. Bug: 963693, 1073395 Change-Id: I5896aeecc56542594e16dcc2a1ce1bceb1b4af99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368144Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Commit-Queue: Devon O'Brien <asymmetric@chromium.org> Cr-Commit-Position: refs/heads/master@{#800599}
-
Ken MacKay authored
Merge-With: eureka-internal/439192 Bug: internal b/162442148 Change-Id: I48246585ffde00158b1aa9ee7a6c403b6668259f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363447Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Commit-Queue: Kenneth MacKay <kmackay@chromium.org> Cr-Commit-Position: refs/heads/master@{#800598}
-
Nicolas Ouellet-Payeur authored
Previously, the NewTabPageLocation policy is lower-priority than extensions' "chrome_url_overrides" setting. This is backwards, so this patch fixes the issue. TESTED=Installed Tabby Cat extension and set NewTabPageLocation policy. Manually opened a bunch of tabs before the patch (Tabby Cat) and after the patch (NewTabPageLocation) Bug: 1020590 Change-Id: Ic3dbe9b9e0ed7efb318c85c489ba7f1faefbbb92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367976Reviewed-by:Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Nicolas Ouellet-Payeur <nicolaso@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#800597}
-
James Long authored
This change adds a bit of clarification via comments on the various mechanisms of graph_view.js, plus a useful link at the beginning as a primer to D3. Bug: 1119942 Change-Id: I4e69ca8626d11d81ea41e0f7a516449866508711 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367743 Commit-Queue: James Long <yjlong@google.com> Reviewed-by:
Samuel Huang <huangs@chromium.org> Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#800596}
-
Mugdha Lakhani authored
Add a toggle to the WebLayer shell app to switch between dark and light mode overrides. This will help test dark mode override. At application launch, neither override is applied and the app follows system setting for dark mode. Bug: 1103716 Change-Id: Id11c40d4962396fcc641d0dc700008d96c57b725 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367097Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#800595}
-
kdillon authored
This queue class name is not accurate to the way that it is currently used and it can be merged with QueueClass::kNone. This class encompasses all of the 'kFrame' QueueTypes that are non-loading (kFrameThrottleable, kFramePausabale, kFrameDeferrable, etc.). Removing this QueueClass will prevent confusion when differentiating between queues with this class and JavaScriptTimer queues. Change-Id: I847eb5d1635eb2932a0399369e982f7a709ece0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2341394Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Reviewed-by:
Scott Haseley <shaseley@chromium.org> Commit-Queue: Katie Dillon <kdillon@chromium.org> Cr-Commit-Position: refs/heads/master@{#800594}
-
Russ Hamilton authored
This is a reland of d35f5dac with the addition of ensuring initialization of one of the SurfaceTracker fields in its constructor. The original change was reverted in d35cd337 due to breakage of build Linux ChromiumOS MSan Tests since https://ci.chromium.org/p/chromium/builders/ci/Linux%20ChromiumOS%20MSan%20Tests/20302 Original change's description: > Modify Privacy Budget UKM Entry Filter to measure identifiable surfaces. > > Add a "SurfaceTracker" to IdentifiabilityStudyState to keep track of > surfaces that have been previously reported for each source. This is > used for deduplication and to limit the number of metrics sent in each > UKM report. > > Bug: 1112787 > Change-Id: I00eb2360849ea6772fbfdcc9b1cf91680f8c6173 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363398 > Reviewed-by: Asanka Herath <asanka@chromium.org> > Commit-Queue: Russ Hamilton <behamilton@google.com> > Cr-Commit-Position: refs/heads/master@{#800332} Bug: 1112787 Change-Id: Iae86f07cb148ff17d449eb9ebf49b8c431391413 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368461Reviewed-by:
Asanka Herath <asanka@chromium.org> Commit-Queue: Russ Hamilton <behamilton@google.com> Cr-Commit-Position: refs/heads/master@{#800593}
-
Zhaoliang Ma authored
This CL set multi-threads encoding based on the image resolution and number of cores for vpx encoding, also enable parallel Tile encoding based on the threads number and row level multi-threading for vp9 encoding. Bug: 1116771 Change-Id: I750ef54c20b79349cefb347aef2522cf128f212c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354642 Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
James Zern <jzern@google.com> Cr-Commit-Position: refs/heads/master@{#800592}
-
Wenyu Fu authored
Change the FRE UI to better adapt to the transition from loading to ToS. Layout preview: go/clank-fre-ui-preview This CL also changes the visibility of UMA / ToS component to View.GONE when they are hidden. This will free up the space so that the screen will not be scrollable on blank content. Bug: 1108558, 1117352 Change-Id: I3f8616bd5810da71afa8b6e40dea2db92e89013e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352033 Commit-Queue: Wenyu Fu <wenyufu@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#800591}
-
James Long authored
This change resolves the TODO(yjlong) artifacts scattered around the codebase. Bug: 1119942 Change-Id: I678317d11d8c7b60356d4dabf12d6b9d71055571 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367647Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/e1e240804211..6a4e145832a9 2020-08-21 egdaniel@google.com Make some public vulkan structs use default initialization. 2020-08-21 fmalita@chromium.org [canvaskit] Fix for OffscreenCanvas-unaware browsers 2020-08-21 jmbetancourt@google.com add SurfaceView support for skottie on android 2020-08-21 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ANGLE from 5dff6075d29f to d3e800e9ad66 (7 revisions) 2020-08-21 skia-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from cbfd396756c6 to 44e1791f100c (1 revision) 2020-08-21 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from e45f0c4d to d3d82066 (463 revisions) 2020-08-21 skia-autoroll@skia-public.iam.gserviceaccount.com Roll dawn from eff9ef0f2212 to e8dc820fbc1e (6 revisions) 2020-08-20 johnstiles@google.com Fix thread-unsafe writes to function declarations in the symbol table. 2020-08-20 ethannicholas@google.com Reland "SkSL now supports uniform array types" 2020-08-20 hcm@google.com add M86 branch release notes 2020-08-20 fmalita@chromium.org [skottie] Custom prop manager updates 2020-08-20 jlavrova@google.com Fixing incorrect boundaries calculations + 3 ways of drawing a paragraph 2020-08-20 ethannicholas@google.com replaced SkSL nodeCount with visitor 2020-08-20 nifong@google.com Add origin visualization, add support for Concat44 2020-08-20 ethannicholas@google.com Reland "SkSL CPP and H backends no longer emitted in non-dev builds" 2020-08-20 johnstiles@google.com Migrate additional casts to as<T>. 2020-08-20 kjlubick@google.com Remove webgl from public.bzl 2020-08-20 csmartdalton@google.com Add new tests to trickycubicstrokes 2020-08-20 johnstiles@google.com Remove sk_TextureSamplers from SkSL. 2020-08-20 bungeman@google.com Notify when SkFontMetrics bounds are bogus. 2020-08-20 kjlubick@google.com [canvaskit] Remove getproc when creating WebGL interface 2020-08-20 kjlubick@google.com [canvaskit] Remove fringe EGL dependency. 2020-08-20 kjlubick@google.com [canvaskit,pathkit] Update to emsdk 2.0 2020-08-20 nikolay.igotti@jetbrains.com Search ICU data on Windows relative to the current module. 2020-08-20 johnstiles@google.com Add as<ProgramElementSubclass> to downcast ProgramElements more safely. 2020-08-20 ethannicholas@google.com Reland "Added support for the 'inline' hint on SkSL functions" 2020-08-20 hcm@google.com Update Skia milestone to 87 2020-08-20 reed@google.com Can we remove this flag to picture-recording? 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 stani@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: stani@google.com Test: Test: Test: FramebufferTest_ES31.*Blit*Test: Test: VulkanPerformanceCounterTest_ES31.MultisampleResolveWithBlit Change-Id: Id8bd9f76e8d9b09206e3bca8de8f7f18f979d502 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369163Reviewed-by:
-
Daniel Hosseinian authored
Because the sidenav is an "extension" of the toolbar, it too should be disabled when the toolbar is. Use the "hidden" attribute in lieu of the "closed" attribute to avoid a collapsing animation when the viewer starts up. Fixed: 1119950 Change-Id: I51a38f51303ac269509c8f5713b27e1fdd49f4d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368160 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
dpapad <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#800588}
-
