- 29 Oct, 2020 40 commits
-
-
Daniel Cheng authored
Change-Id: Ie8e9b9ebd7ada8cce06f6500196ea950efd01201 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506617 Auto-Submit: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#822064}
-
Alexander Alekseev authored
This CL removes IME dependency from the session state and makes IME UI changes synchronous with the system UI. Bug: b/160647413 Change-Id: Iefc1711cafac3d2ee42108d08bc7f0165b00e18e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2479862Reviewed-by:
Shu Chen <shuchen@chromium.org> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Reviewed-by:
Anqing Zhao <anqing@chromium.org> Commit-Queue: Alexander Alekseev <alemate@chromium.org> Cr-Commit-Position: refs/heads/master@{#822063}
-
Mason Freed authored
These tests were in a group that was timing out on android servers. I converted both of them from PerfTestRunner.measureTime to PerfTestRunner.measureRunsPerSecond(), which should be more predictable across platforms. I also cleaned up the code a bit. * blink_perf.dom/custom-element-default-style-with-shadow.html * blink_perf.dom/custom-element-default-style.html Metrics for these two tests *will* change after this CL lands, but that should not be a concern. Bug: 1142315 Change-Id: I80bc469553621420eb2e3f8b250d96260e8515b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505744 Auto-Submit: Mason Freed <masonfreed@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#822062}
-
James Vecore authored
We now wait for the FastPathReady message before returning the result for the StartReceivingMessages mojo call. Fixed: 1134212 Change-Id: Ic1b64421544a90a7ae82b0d11f69edf64c2d1021 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506391Reviewed-by:
Alex Gough <ajgo@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Commit-Queue: James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#822061}
-
Solomon Kinard authored
Bug: None Change-Id: I91bb493036a66daa99da8932e167ef2e22dd805d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505882Reviewed-by:
David Bertoni <dbertoni@chromium.org> Commit-Queue: Solomon Kinard <solomonkinard@chromium.org> Cr-Commit-Position: refs/heads/master@{#822060}
-
Koji Ishii authored
When the `lang` attribute does not match the hyphenation dictionary exactly, this patch computes fallback languages, by incrementally removing the last component separated by U+002D HYPHEN-MINUS character. This allows, for instance, `lang="fr-fr"` or `lang=`fr-ca`" to find the `fr` dictionary. Bug: 815059 Change-Id: Ia4b76621dfb18b5aef604e8c7351ed9322f056dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505353 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#822059}
-
Keishi Hattori authored
Check if all FreelistEntry pointers in the linked list are valid. By making sure the FreelistEntry and the next one are on the same super page. Bug: 1137799 Change-Id: Ic37f4fb80a0a14251247fa39912f9d4cc8f90901 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500652 Commit-Queue: Keishi Hattori <keishi@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#822058}
-
Joel Hockey authored
Bug: 953310 Change-Id: I04762056fb288807d9dc7a8fce717f331d43784a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2504750Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Auto-Submit: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#822057}
-
Alex Danilo authored
Bug: 1110540 Tests: browser_tests --gtest_filter="*saveFileDialogAriaSingleSelect" Change-Id: I1ec00b62daaa7e4e476380a1a0f3df8fa6acce5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2504753 Commit-Queue: Alex Danilo <adanilo@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#822056}
-
Nidhi Jaju authored
In an effort to change the blink implementation of readable streams to better match the Web IDL descriptions in the Streams API Standard, this CL changes the first parameter of pipeTo() in readable_stream.idl to WritableStream type based on https://streams.spec.whatwg.org/#ref-for-rs-pipe-to%E2%91%A1. This CL also modifies the ordering and comments within pipeTo() inside the ReadableStream class to better reflect the steps outlined in https://streams.spec.whatwg.org/#rs-pipe-to. Bug: 1093862 Change-Id: Id6029dc3dc0551e59c812daac499a8e538f3be75 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505333Reviewed-by:
Adam Rice <ricea@chromium.org> Commit-Queue: Nidhi Jaju <nidhijaju@google.com> Cr-Commit-Position: refs/heads/master@{#822055}
-
Hiroshige Hayashizaki authored
According to the spec https://html.spec.whatwg.org/C/#timer-initialisation-steps setTimeout()/setInterval() don't inherit initiating script's muted errors flag, which matches with Chromium/Firefox/Safari. This CL fixes WPT tests to match with the spec/impl, i.e. to expect errors from setTimeout()/setInterval() from cross-origin scripts not to be muted. Bug: 1111134 Change-Id: I3b4d0a5450ccee8fb04113846c9e9773d476cfe7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485416Reviewed-by:
Domenic Denicola <domenic@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#822054}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/67e1cf4b1d81..4860462a2734 2020-10-29 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Dawn from 47ee61679da0 to a584311a6a73 (5 revisions) 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 jcgregorio@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: jcgregorio@google.com Change-Id: I8a4679a6cfe16ceb1b1238ebf8b46dd11d8a71e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506342Reviewed-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@{#822053}
-
Samuel Attard authored
Electron's Context Isolation implementation has a side-effect of initializing the isolated worlds WindowProxy during the initialization of the main world WindowProxy as a result of creating the isolated world inside the DidCreateScriptContext hook. This results in an assertion failing in Chromium during a frame swap where it expects to be able to set a new global_proxy in the WindowProxy of the isolated world BEFORE it is initialized. To meet this assumption this patch splits SetGlobalProxy into two calls, SetGlobalProxyWithoutInitializing and InitializeIfNeeded which has the same resultant effect but means that all of the global_proxy objects are set BEFORE any WindowProxy's are initialized. To further clarify, if an embedder creates and initializes new script context as a result of a call to DidCreateScriptContext the "global_proxy_.IsEmpty()" CHECK fails as it doesn't expect that context to have been initialized yet. Change-Id: I0efa579a4ec2d93369f3e1fc7a922a459a2300cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503397Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
-
Brett Kilty authored
No definitive repro, but found in several large automated test runs with rapid activity on device. All protect this remaining member against access after destruction. Bug: b/163868029 Test: Local execution, no regression Change-Id: Icaf5e73f10f75e6edcf414c830b8eb99611b4b27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503637Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Commit-Queue: Brett Kilty <brettk@google.com> Cr-Commit-Position: refs/heads/master@{#822051}
-
Julie Jeongeun Kim authored
As blink::mojom::ResourceType is deprecated[1], this CL uses network::mojom::RequestDestination in ServiceWorkerFetchDispatcher, ServiceWorkerControlleeRequestHandler, and ServiceWorkerMainResourceLoaderInterceptor. [1] https://crbug.com/960143 Bug: 1059639 Change-Id: Ida0434e7ba07ed4f87b0bdaa3c5c7d732613059f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491595 Commit-Queue: Julie Kim <jkim@igalia.com> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#822050}
-
Alex Moshchuk authored
Currently, there are two SiteIsolationPolicy objects: one in //content which knows about content-internal things, and one in //components, which knows about higher-layer modes such as password-triggered site isolation on Android. The ShouldPdfCompositorBeEnabledForOopifs() in content was a bit problematic for two reasons: (1) it's a bit of a layering violation for content to know about PDF compositor, (2) it implicitly relied on AreIsolatedOriginsEnabled() being true for the password-triggered site isolation mode used on Android, which stopped being true in https://crbug.com/1005895. This CL moves ShouldPdfCompositorBeEnabledForOopifs() to the SiteIsolationPolicy in //components, where it's also updated to check IsIsolationForPasswordSitesEnabled() in addition to the other two site isolation modes. Note that this still should exclude (1) low-memory Android devices that don't use any site isolation (enforced via IsSiteIsolationDisabled() checks inside SiteIsolationPolicy), and (2) Android Webview, where OOPIFs aren't supported (hopefully this is true because AW doesn't go through code paths that check ShouldPdfCompositorBeEnabledForOopifs()). Eventually, the goal is to enable PDF compositor everywhere, so hopefully we can remove ShouldPdfCompositorBeEnabledForOopifs() altogether at some point. Bug: 1022917 Change-Id: Ib8d3a7c7b133707d5c6ca88efbbdc0f77635fe1a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500444Reviewed-by:
Wei Li <weili@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#822049}
-
chrome://flags#check-offline-capabilityAsami Doi authored
Bug: 965802 Change-Id: Id0008fd9418110c3d1d4590c7ca035b5317d7aff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2494288 Commit-Queue: Asami Doi <asamidoi@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#822048}
-
Jiewei Qian authored
By default, we use an empty SWA list in test. When the test chrome process starts, SystemWebAppManager first calls SynchronizeInstalledApps with an empty list. In the upgrade test, this cause previously installed apps to be uninstalled. In the test body, we then use InstallSystemAppsForTesting to install the real system apps. This effectively installs apps on a clean state, and defeats the purpose of this test. This CL adds a check so SystemWebAppManager uses the real SWA list, if EnableAllSystemWebApps feature is enabled. Fixed: 1143108 Change-Id: I7f60429bcae45c011eb0681a6d8c322e898a32c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503374Reviewed-by:
calamity <calamity@chromium.org> Commit-Queue: Jiewei Qian <qjw@chromium.org> Cr-Commit-Position: refs/heads/master@{#822047}
-
Hiroshige Hayashizaki authored
Before this CL, there are three slightly different methods for module script evaluation: - Modulator::ExecuteModule() - ModuleRecord::Evaluate() - V8ScriptRunner::EvaluateModule() To unify the code paths and behavior, this CL - Merges them into V8ScriptRunner::EvaluateModule() (Mostly just inlining) - Merges Modulator::CaptureEvalErrorFlag into V8ScriptRunner::RethrowErrorsOption, and - Introduces a thin wrapper ModuleScript::RunScriptAndReturnValue() to align with the ClassicScript conterpart. The new behavior of V8ScriptRunner::EvaluateModule() is the same as the previous ModulatorImplBase::ExecuteModule(). This CL shouldn't change the non-test behavior, because all non-test code path went through ModulatorImplBase::ExecuteModule(), This CL also replaces some Modulator calls (that were in Modulator::ExecuteModule() and are now in V8ScriptRunner::EvaluateModule()) with equivalent direct calls to ExecutionContext, to avoid many more overrides in DummyModulator subclasses in unit tests. Bug: 1111134 Change-Id: Icbda1e657b33077f0ae1e681045b04857229cbfc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2462885Reviewed-by:
Dominic Farolino <dom@chromium.org> Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#822046}
-
Kenichi Ishibashi authored
There seems a situation where multiple operations are queued at a time for the same resource id. Since `active_entry_calls_` and `active_doom_calls_` used resource id as a key, only one callback was preserved. When DidGetEntryResult() or DidDoomEntry() were called for the second time, these tried to find active calls from the maps but callbacks were already consumed. This CL replaces keys of `active_entry_calls_` and `active_doom_calls_` with monotonically increasing `call_id_` to make sure we don't lose the callback of each operation. Bug: 1142779 Change-Id: Ie4a999c50bcee3417453da8bbe4b2b529462b91f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505338 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/77defeb04693..f418c109094a 2020-10-29 ianelliott@google.com Vulkan: Document how to turn on debug markers 2020-10-28 ianelliott@google.com Vulkan: App-compat for apps that disable validation & don't link 2020-10-28 cnorthrop@google.com Tests: Update COD:Mobile trace 2020-10-28 cnorthrop@google.com Tests: Add PUBG Mobile Lite trace 2020-10-28 geofflang@google.com Work around Mac glGenerateMipmap with missing levels bug. 2020-10-28 cnorthrop@google.com FrameCapture: Disable GL_OES_mapbuffer during capture 2020-10-28 cnorthrop@google.com FrameCapture: Track surface width/height per context If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC geofflang@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: geofflang@google.com Test: Test: Capture PUBG MobileTest: Test: Capture PUBG Mobile LiteTest: Test: angle_perftests --gtest_filter="*cod_mobile*"Test: Test: angle_perftests --gtest_filter="*pubg_mobile_lite*" Change-Id: I2306b49c5acc06747db6656e01399616647f204f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506388Reviewed-by:
-
chromium-autoroll authored
https://dawn.googlesource.com/tint.git/+log/5ede1190cf97..d2fa57d26dff 2020-10-29 dsinclair@chromium.org [doc] Add some documentation around translations. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/tint-chromium-autoroll Please CC rharrison@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 Bug: None Tbr: rharrison@google.com Change-Id: Id8ec10288703153b7dab16ac017c939b507cee01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506606Reviewed-by:
-
Dirk Pranke authored
Currently, when a bot runs a test (say, url_unittests) on an Android build, it'll launch `python test_env.py logdog_wrapper.py bin/run_url_unittests` (roughly speaking). This CL flips that around so that the generated bin/run_url_unittests script will invoke test_env.py to launch url_unittests (and the bot will then invoke bin/run_url_unittests directly). This slightly reduces the discrepancy between what a dev runs locally and what the bot runs, and will make Android consistent with every other platform. Bug: 816629 Change-Id: I76727641b5a4362f37762ed4ed4b175eea58ce2e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506634Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/master@{#822042}
-
Emircan Uysaler authored
This CL applies the crop rect calculated by the overlay processor on Scenic's scene graph. Bug: 1127984 Change-Id: Ifc4a7078c1323fcdc2921e8fccb367e05dfd3824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503857 Auto-Submit: Emircan Uysaler <emircan@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#822041}
-
Harvey Yang authored
This commit extracts ECLidAngleDriverSupported information from AccelerometerUpdate and adds a public function GetECLidAngleDriverStatus() in AccelerometerReader to provide this information because it doesn't change. It also adds SetECLidAngleDriverStatusForTesting() to fake the status for unittests. BUG=b:171446270 TEST=unit tests, and run on jacuzzi & hatch Change-Id: I80cb66e6caf77f9d193b92e9a675d649576fcc87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491462 Commit-Queue: Cheng-Hao Yang <chenghaoyang@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Cr-Commit-Position: refs/heads/master@{#822040}
-
Abigail Klein authored
Expose the caption bubble text accessibly in multiple AXVirtualViews, which are a type of AXPlatformNode. Each node has its name set as caption text. Each node corresponds to a line, where line wrapping is done by RenderText. The motivation for this change is that braille displays are sensitive to frequent updates, and exposing the caption bubble text in a single accessible node resulted in that same node to updating multiple times a second, leading to the braille display keeping the user's focus at the beginning of the text. This change allows users to read the captions at their own speed without noticing other nodes updating. Bug: 1055150, 1105676 AX-Relnotes: N/A (feature has not launched) Change-Id: I6433677652c0ebaf14617f4ac216f1fbade28e65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2462689 Commit-Queue: Abigail Klein <abigailbklein@google.com> Reviewed-by:
Michael Wasserman <msw@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#822039}
-
Sinan Sahin authored
Bug: 1134927 Change-Id: Icd06307a11bdfd218c77f8aaf3ab6e651bb1e978 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500483Reviewed-by:
Lijin Shen <lazzzis@google.com> Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Sinan Sahin <sinansahin@google.com> Cr-Commit-Position: refs/heads/master@{#822038}
-
Mark Pearson authored
Change-Id: I908a337129062e882b185a08329fecfd7db6c496 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2504593Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#822037}
-
Shik Chen authored
The ESLint version listed in peerDependencies of the upstream eslint-config-google is too old and does not support id-denylist yet, so we fix it in our codebase directly instead. Bug: 1123783 Test: CQ Change-Id: I0d7ba088dccbe9dc96ce72d526483d37d68bcc0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505257 Auto-Submit: Shik Chen <shik@chromium.org> Reviewed-by:
Wei Lee <wtlee@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#822036}
-
Chong Gu authored
Bug: 1130706 Change-Id: Iaf8bf9e37a06747d74c0722ce490e1dbd26ee9c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2504202 Auto-Submit: Chong Gu <chonggu@google.com> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Chong Gu <chonggu@google.com> Cr-Commit-Position: refs/heads/master@{#822035}
-
Ben Joyce authored
Bug: None Change-Id: I9f31aa8a2e1194825806969b7deba6a4ad4cd398 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506297Reviewed-by:
Ben Pastene <bpastene@chromium.org> Reviewed-by:
benjamin joyce <bjoyce@chromium.org> Commit-Queue: benjamin joyce <bjoyce@chromium.org> Cr-Commit-Position: refs/heads/master@{#822034}
-
Luciano Pacheco authored
First batch of files in metadata that Audio Player depends on: - metadata_provider.m.js - image_orientation_unittest.m.js - image_orientation.js - metadata_request.js Note on the image_orientation_unittest: assertArrayEquals() andassertDeepEquals() now check for the type, so changed to use Uint8ClampedArray in the expected value. Bug: 1133186 Change-Id: Icbf9d58039eaa94d732c62c29f9bef08dbd39390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503767 Auto-Submit: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Jeremie Boulic <jboulic@chromium.org> Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#822033}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/2971eb674935..2bb8035ddc14 2020-10-28 kainino@chromium.org Integrate deprecation testing into DawnTestBase 2020-10-28 dawn-autoroll@skia-public.iam.gserviceaccount.com Roll Tint from e8dc46a8c88b to 5ede1190cf97 (1 revision) 2020-10-28 dawn-autoroll@skia-public.iam.gserviceaccount.com Roll Tint from c23a5652bda1 to e8dc46a8c88b (2 revisions) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC rharrison@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: rharrison@google.com Change-Id: Id29654462a94a9cedcef7228533a76d3cb194668 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506603Reviewed-by:
-
Kent Tamura authored
TextControl NG: Fix All/HTMLTextAreaElementTest.ValueWithHardLineBreaks/1 test on linux_layout_tests_layout_ng_disabled bot HTMLTextAreaElementTest is a parameterized test for LayoutNGTextArea flag. However, the feature can be disabled even with GetParam() == true because we can disable LayoutNG flag. This CL fixes the issue by checking LayoutObject instead of GetParam(). Bug: 1040826 Change-Id: I160037df5b2f52694f96379188724b578fb77d59 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng_disabled Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505343 Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by:
-
Hiroki Nakagawa authored
This CL mechanically renames files (isolated_prerender to prefetch_proxy) and classes (IsolatedPrerender to PrefetchProxy) based on the discussion in this design doc: https://docs.google.com/document/d/1e_8buEEhqgY72R2_kjGC3ChBRbA9lt5jEAZr8RLc-5Q/edit?usp=sharing For keeping compatibility with external components, this CL doesn't rename runtime flags and UMA/UKM names. Bug: 1142211 Change-Id: Ic821fa2b1550e7caee9234d378890a58de85a444 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503378 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Nicolas Ouellet-Payeur <nicolaso@chromium.org> Reviewed-by:
Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#822030}
-
Chris Lu authored
This change adds logic to show a modal detailing Chromium's use of location data after First Run and showing the prompt if the user taps on the primary action button. This is hidden behind the kLocationFirstRunModal flag. Bug: 1138603 Change-Id: I5ba49231b547edaeaef1ee025744a344f9135998 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485748 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#822029}
-
Eric Lawrence authored
Now that OVERLAY_NEW_LAYOUT has launched, remove the flag, resources, and code related to the old layout. Bug: 1110709 Change-Id: I89e8fa4b6e6a3e5fee8f82305794c81d0c3f7df8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2504329Reviewed-by:
Donn Denman <donnd@chromium.org> Commit-Queue: Eric Lawrence [MSFT] <ericlaw@microsoft.com> Cr-Commit-Position: refs/heads/master@{#822028}
-
wutao authored
The Recent Highlights has 2x2 preview images. Screenshot: https://screenshot.googleplex.com/56hG78STNTdvCGC Bug: b/168068860 Test: Add new js tests. Change-Id: I1c830667327e18f465f568eb8abacea0929bc409 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2486285 Commit-Queue: Tao Wu <wutao@chromium.org> Reviewed-by:
Jimmy Gong <jimmyxgong@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#822027}
-
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-aemu-chromium-autoroll Please CC chonggu@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 Tbr: chonggu@google.com Change-Id: Iaf843991f6a22efa0b9322cfc23164f9564683fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506385Reviewed-by:
-
Alexandre Courbot authored
Before passing frames to convert to the backend, the image processor checks that the storage type of the frame is the same as the storage type the backend has been configured for. This check is however very strict, and does not take into account the fact that for some backends, different storage types might be equivalent. For instance on the V4L2 backend, GMB and DMABUF frames are processed the same way, and are entirely interchangeable. The VideoDecoderPipeline class always create the image processor for use with GMB, but when using the VideoDecoder from ARC, frames are backed by DMABUF. We have no easy way to differentiate these use-cases, and ARC decoding using the VD will thus fail if an image processor is involved. The backend will reject invalid frames when it tries to process it anyway ; so remove that check and let the backend decide whether it can work with a given frame or not. Bug: b:171683262 Test: ./video_decode_accelerator_tests passes on Kukui. Test: ./video_decode_accelerator_tests --use_vd passes on Kukui. Test: ./video_decode_accelerator_tests --use_vd_vda passes on Kukui. Change-Id: I99154597c77c7df99c5cfc6cb104da6b95b66c82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503913 Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by:
Fritz Koenig <frkoenig@chromium.org> Reviewed-by:
Chih-Yu Huang <akahuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#822025}
-
