- 19 Aug, 2020 21 commits
-
-
Russ Hamilton authored
Change-Id: Idd9f8996b430df63f44273c07e6a4ad993aad38a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359558Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Russ Hamilton <behamilton@google.com> Cr-Commit-Position: refs/heads/master@{#799415}
-
rbpotter authored
Bug: 1000989 Change-Id: I8bf967219ae6fb20446bb2d096be49f4a3765be2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360697Reviewed-by:
dpapad <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#799414}
-
Wan-Teh Chang authored
I completed an audit of the grid image code in libavif. See bug 1114916. Change-Id: Ifb2d4859bff5fc5647095b04e3bdb4db88a31ae4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354777Reviewed-by:
Peter Kasting <pkasting@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Wan-Teh Chang <wtc@google.com> Cr-Commit-Position: refs/heads/master@{#799413}
-
Kenichi Ishibashi authored
This test depends on in-memory representations of service worker registrations and versions. Move the test from service_worker_storage_unittest.cc to service_worker_registry_unittest.cc so that the storage_unittest.cc can be moved to the Storage Service directory. This CL also modifies ServiceWorkerStorage::StoreRegistrationData so that it can LazyInitialize() when uninitialized. This allows the test to eliminate explicit LazyInitialize() call. Bug: 1055677 Change-Id: I2425d9aa964c37191df355f1c5c67ed250cb1f74 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2361382Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#799412}
-
Haiyang Pan authored
This reverts commit c3907c3e. Reason for revert: Observed multiple test failures in chrome_pulic_test_apk on android builders, since the following builds: * https://ci.chromium.org/p/chromium/builders/ci/android-marshmallow-x86-rel/973 * https://ci.chromium.org/p/chromium/builders/ci/android-pie-x86-rel/1894 * https://ci.chromium.org/p/chromium/builders/ci/android-arm64-proguard-rel/2437 Original change's description: > Migrate remaining chrome/android native_java_unittest to javatests > > native_java_unittests are going away, so these tests need to be migrated > to javatests. > > Bug: 1103344 > Change-Id: I49a99d1cc1e3170d4af01af8e1a75e9b09249fc5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353391 > Commit-Queue: Michael Thiessen <mthiesse@chromium.org> > Reviewed-by: Yaron Friedman <yfriedman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#799264} TBR=yfriedman@chromium.org,mthiesse@chromium.org Change-Id: Ia64e53afde3d7fdeecb1a4500c74bf6e0ad69ffa No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1103344 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363925Reviewed-by:
Haiyang Pan <hypan@google.com> Commit-Queue: Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#799411}
-
Miguel Casas authored
ToT VaapiWrapper uses |va_buffers_| for internal Vpp uses and also for external VEA/JEA use. This CL starts refactoring these VABufferIDs lifetime, by splitting the Vpp VABufferID out of |va_buffers_| and into a ScopedID |va_buffer_for_vpp_|. Bug: b:162962069 Change-Id: Ic54d0d26f5d17ea49fe896cf7ca5e1c931d07e0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352522 Commit-Queue: Miguel Casas <mcasas@chromium.org> Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#799410}
-
Brandon Wylie authored
This property is captured implicitly by other events. When reparenting, this property isn't captured properly. Adding an explicit event for this to ensure it is. Bug: 1076798 Change-Id: I1e5fa720627128a13e3969abc0a891b37d846936 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2293160 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#799409}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/c4a82aaabbdd..573931528077 2020-08-18 jmadill@chromium.org Auto-gen more Overlay code. 2020-08-18 jmadill@chromium.org Clean up Overlay code duplication. 2020-08-18 jmadill@chromium.org Vulkan: Clean up ImageLayout enum. 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 cnorthrop@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: cnorthrop@google.com Change-Id: I533bb3e858398874b6c3b0e3e90efc9ab864f9f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363793Reviewed-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@{#799408}
-
Lily Chen authored
This fixes a crash caused by failure of a consistency check on the Reporting endpoints present in an endpoint group, triggered by receiving malformed Report-To headers (or multiple Report-To headers in one response). Upon parsing a Reporting group from a newly received header, if an equivalent group already exists in the cache, any preexisting endpoints with URLs that are not present in the newly parsed group are removed, i.e. a new header should overwrite the equivalent group set by a previous header. The problem occurs when there are multiple equivalent groups with disjoint endpoint URLs present in the same header (or multple headers on the same response). We should treat these headers as if a single group were specified, containing the combined set of URLs. However, we were deleting preexisting but no-longer-present endpoints multiple times, once for each duplicate group listed. The (malformed) header would effectively overwrite previous parts of itself, causing a consistency check failure. This is fixed by removing old endpoints only after the entire header has been processed. Bug: 1116529 Change-Id: I1bf5d57db2acf9f90a9d1cb63a5b1b79d9145fca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357468 Commit-Queue: Lily Chen <chlily@chromium.org> Reviewed-by:
Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#799407}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/9d0f7dea2a59..0795384a7997 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium Please CC perfetto-bugs@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: perfetto-bugs@google.com Change-Id: I33e6e011455a92bc4a8ba165135ac88ac31838b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363446Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/9d0f7dea2a59..0795384a7997 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-mac-chromium Please CC perfetto-bugs@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: perfetto-bugs@google.com Change-Id: I3266d7e79c26347701cf5adc1c73aeebcb76666e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363645Reviewed-by:
-
Dan Sanders authored
https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+log/d2dd36c03501..45b753b2d1 $ git log d2dd36c03..45b753b2d --date=short --no-merges --format='%ad %ae %s' 2020-08-17 sandersd@chromium.org Always use av_realloc() for ogg_stream |buf|. 2020-08-14 sandersd@chromium.org README.chromium file 2020-08-14 sandersd@chromium.org Chromium patches file 2020-08-14 sandersd@chromium.org GN Configuration 2020-08-01 lance.lmwang@gmail.com avcodec/libsvtav1: remove unneeded svt_av1_enc_deinit_handle() (...) 2020-04-16 josh.brewster libavcodec/libx264: fix reference frame computation based on level 2020-04-20 barryjzhao lavf/mp3enc: fix ID3v1 year metadata setting issue 2020-04-26 lance.lmwang avformat/dashenc: use av_reallocp_array() 2020-04-26 lance.lmwang avformat/dashenc: use local variable and avoid calculate duration multiple times 2020-04-26 lance.lmwang avformat/dashenc: cosmetics Created with: roll-dep src/third_party/ffmpeg Bug: 1105118, 1117613 Change-Id: Ife0e3dca60640e88a2b3f508fbfc6fe8d9308be9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359167 Commit-Queue: Dan Sanders <sandersd@chromium.org> Reviewed-by:
-
Kartik Hegde authored
Tests whether a firewall is blocking HTTP port 80. TEST=unit_tests --gtest_filter=HttpFirewallRoutineTest.* BUG=chromium:956783 Change-Id: I9e847e433417dd2f2cca551041d7bf4ab5ad032e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303464 Commit-Queue: Kartik Hegde <khegde@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#799403}
-
Yoichi Osato authored
This CL is a follow up of the histogram: crrev.com/c/2255925 Bug: 688906 Change-Id: Ic81f629a8074708f2ea6240cf09036318ac97e11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354125 Commit-Queue: Yoichi Osato <yoichio@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#799402}
-
Klaus Weidner authored
If entering WebXR mode using DOM Overlay when we're already in fullscreen mode, and if we have a remote ancestor frame that's in another process, the ancestor frame didn't get set to transparent since fullscreen_controller ignores changes to fullscreen options. As a workaround, exit fullscreen mode in this case before proceeding with the session request. Bug: 1101193 Change-Id: I36b9918717abf6c5d462b7c78d545ae53fc5391e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358493Reviewed-by:
Piotr Bialecki <bialpio@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#799401}
-
Brandon Maslen authored
The Storage Access API is enabled in Edge but is still disabled by default in Chromium. This change updates the expiration of the about:flags entry to allow for continued use for a few more milestones. Bug: 989663 Change-Id: I8072fd21606c152fb1106a8e1aebe2fb3e78c054 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363642Reviewed-by:
Nicolas Arciniega <niarci@microsoft.com> Commit-Queue: Brandon Maslen <brandm@microsoft.com> Cr-Commit-Position: refs/heads/master@{#799400}
-
Yue Li authored
Bug: b/164287576 Test: Run QuickAnswersControllerTest.* in ash_unittests Change-Id: Id59933ae2535cc485c2515d8e8971b2b85752e21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2355492 Commit-Queue: Reilly Grant <reillyg@chromium.org> Auto-Submit: Yue Li <updowndota@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Jeroen Dhollander <jeroendh@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#799399}
-
Alan Screen authored
Move the printing::ColorModel enum to print.mojom for using it in Mojo interfaces. This is in preparation for mojoifying PrintBackend class. Bug: 809738 Change-Id: Ibe3f4a47c807a8d4af28fb72f3667aa7a2163cd2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2355083Reviewed-by:
Will Harris <wfh@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Alan Screen <awscreen@chromium.org> Cr-Commit-Position: refs/heads/master@{#799398}
-
Sky Malice authored
This reverts commit b27232d7. Reason for revert: Test failures, see crbug.com/1117676 Original change's description: > [PwdCheckAndroid] Add redirect to Google Password Check on quota limit > > This CL adds the logic to redirect the user to the Google Password > Check on quota limit error. The redirect is called through > PasswordCheckBridge to avoid dependencies on chrome_java. > > IDS_PASSWORD_CHECK_STATUS_MESSAGE_ERROR_QUOTA_LIMIT_ACCOUNT_CHECK.png > https://storage.cloud.google.com/chromium-translation-screenshots/c4546cf199aa6314ead807fa1fc0e1ed8b779a83 > > Bug: 1092444 > Change-Id: I374ad088c305d299fea00f412f27dd6ab3d0e9b5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362023 > Reviewed-by: Ioana Pandele <ioanap@chromium.org> > Reviewed-by: Friedrich [CET] <fhorschig@chromium.org> > Commit-Queue: Eleonora Rocchi <erocchi@google.com> > Cr-Commit-Position: refs/heads/master@{#799117} TBR=fhorschig@chromium.org,ioanap@chromium.org,erocchi@google.com Change-Id: I38a6779f2a9a278317ab5ce2be2edb0742e34f34 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1092444 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363444Reviewed-by:
Sky Malice <skym@chromium.org> Commit-Queue: Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#799397}
-
Eric Roman authored
This also moves udp_socket_test_util.cc into the test/ subdirectory, in order to satisfy existing DEPS rules. Bug: 1083278 Change-Id: I45fd4ceb8b46e0464ff0cd2a41a897efa294f64b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360125Reviewed-by:
David Schinazi <dschinazi@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: John Abd-El-Malek <jam@chromium.org> Auto-Submit: Eric Roman <eroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#799396}
-
Haoyue Wang authored
https://quiche.googlesource.com/quiche.git/+log/e1e5e502ea64..abf77f1b3891 $ git log e1e5e502e..abf77f1b3 --date=short --no-merges --format='%ad %ae %s' 2020-08-18 wub Internal QUICHE change 2020-08-18 fayang Add a stable enum for QuicFrameType for logging purpose. 2020-08-17 renjietang In QUIC, change OnOneRttKeysAvailable() to OnTlsHandshakeFinished(). Created with: roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src Change-Id: Iebc4860945ebbc443c531172a1cc234463c4568d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363807 Commit-Queue: Haoyue Wang <haoyuewang@chromium.org> Commit-Queue: Zhongyi Shi <zhongyi@chromium.org> Auto-Submit: Haoyue Wang <haoyuewang@chromium.org> Reviewed-by:
Zhongyi Shi <zhongyi@chromium.org> Cr-Commit-Position: refs/heads/master@{#799395}
-
- 18 Aug, 2020 19 commits
-
-
Tommy Li authored
This CL refactors ZeroSuggestProvider::TypeOfResultToRun to take an AutocompleteInput as a parameter instead of just the current page URL. We need this because differentiating the on-focus vs. on-clobber ZeroSuggest modes requires access to AutocompleteInput::focus_type(). This CL also makes the method 'static', for three reasons: 1. The function is more easily testable when it only depends on its parameters, rather than any state in the member variables. 2. The member variables store data that's also in the |input| parameter, and I didn't want to introduce ambiguity as to which is used. 3. We plan to split MostVisited into its own provider, and we will want to share some logic from TypeOfResultToRun. Making this method static is a step towards that future. For reviewability, this CL actually has no functional changes, and just moves things around. The followup CL will actually add the on-clobber vs. on-focus logic to TypeOfResultToRun. Bug: 1106096 Change-Id: I69c8f2f08a182796be9ce1c66611fe6788a6158a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360562Reviewed-by:Tomasz Wiszkowski <ender@google.com> Commit-Queue: Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#799394}
-
Steven Bennetts authored
This is in preparation for adding UI to allow users to set a custom DHCP hostname. Currently the policy code is always setting the hostname, even if kDeviceHostnameTemplate is not set by policy, which overrides any other custom set hostname. Bug: 1103272 Change-Id: Ia99ee58c59ae1f38e8fe10ed693997dead861c4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320991 Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Omar Morsi <omorsi@google.com> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#799393}
-
Sammie Quon authored
Original thought the dark ripple was for the dark background. Test: manual Bug: 1117203 Change-Id: I3221271f8bb1d1d32a8832c75a46c0b8f726426e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363997Reviewed-by:
-
John Palmer authored
Should be 8px, old number worked out to 16px BUG=1117379 Change-Id: Ic6cef89a6c9b93fab24b538f13d6c07fa4f06647 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362062 Auto-Submit: John Palmer <jopalmer@chromium.org> Commit-Queue: Keith Lee <keithlee@chromium.org> Reviewed-by:
Keith Lee <keithlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#799391}
-
David Bokan authored
As part of splitting out input from LayerTreeHostImpl I found some issues in tests that use FakeLayerTreeHost. This class also initializes a FakeLayerTreeHostImpl which is used in some tests. However, some tests also call InitializeSingleThreaded to use the FakeLayerTreeHost with a Proxy. Initializing a Proxy will call LayerTreeHost::CreateLayerTreeHostImpl which currently creates a (real) LayerTreeHostImpl that's owned by the Proxy. These tests are incorrectly running with multiple LTHI objects. This CL overrides CreateLayerTreeHostImpl in the fake so that this method creates a fake Impl object. We also avoid manually creating a fake Impl inside the FakeLayerTreeHost and instead rely on the call to CreateLayerTreeHostImpl to store a pointer to the fake impl. For tests that don't use a Proxy, we now manually call a new CreateFakeLayerTreeHostImpl method that does the same thing and the FakeLayerTreeHost takes ownership of the Impl instead. Bug: 915926 Change-Id: I63202e1717d2eab026688d69c8d0ef75939c7c47 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363247Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#799390}
-
Miguel Casas authored
ToT VaapiWrapper has a simple report-to-uma callback that clients have to implement and that usually just points to "error happened" in either the normal or the Vpp VaapiWrapper. This CL changes that: - VaapiWrapper provides a function for this: ReportVaapiErrorToUMA(). - Clients bind their histogram (eg. Media.VaapiVideoDecoder.VAAPIError) to that new ReportVaapiErrorToUMA() method. - A new VaapiFunctions enumeration (with a matching UMA enum) is added to vaapi_wrapper.cc to identify which concrete vaBla() function failed, and is logged to UMA. This forces ToT UMA histograms (and associated enums) to be marked as obsolete, namely: -Media.VAJDA.DecoderFailure -Media.VAJDA.VppFailure -Media.VAJDAWorker.DecoderFailure -Media.VAJEA.VppFailure -Media.VAVDA.DecoderFailure -Media.VAVEA.EncoderFailure New ones are landed instead (with associated VaapiFunctions enum): -Media.VaapiImageDecodeAcceleratorWorker.VAAPIError -Media.VaapiJpegEncodeAccelerator.VAAPIError -Media.VaapiJpegEncodeAccelerator.VAAPIVppError -Media.VaapiMjpegDecodeAccelerator.VAAPIError -Media.VaapiMjpegDecodeAccelerator.VAAPIVppError -Media.VaapiVideoDecodeAccelerator.VAAPIError -Media.VaapiVideoDecoder.VAAPIError -Media.VaapiVideoEncodeAccelerator.VAAPIError -Media.VaapiVideoEncodeAccelerator.VAAPIVppError This CL also adds two new boolean histograms for VaapiVideoDecoder, who had none. Bug: b:162962069 Change-Id: I561e48183f61de86247598fea4f3b10cd590c2e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339787 Commit-Queue: Miguel Casas <mcasas@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Jao-ke Chin-Lee <jchinlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#799389}
-
Becca Hughes authored
For normal images contentAttributes are optional in the spec but the converter requires them. This makes them optional. Change-Id: I4073de51009e6e7802667b2d79a7ad485d939978 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363477 Auto-Submit: Becca Hughes <beccahughes@chromium.org> Commit-Queue: Sam Bowen <sgbowen@google.com> Reviewed-by:
Sam Bowen <sgbowen@google.com> Cr-Commit-Position: refs/heads/master@{#799388}
-
Evan Stade authored
Bug: 1110930 Change-Id: I20914d3f88ad98944e0f5525421bc666cc79eb73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363696Reviewed-by:
-
James Cook authored
Add support for image, list, and progress notifications. This involves serializing the RichNotificationData structure. Move some existing crosapi::Bitmap serialization code into a shared utility file. Add deserialization to SkBitmap. For now the image format is hard-coded. crbug.com/1116652 tracks more flexible image serialization. Add unit tests for both ash side and lacros side. Bug: 1113889 Test: unit_tests, manual with Notifications Galore chrome app Change-Id: I27b1c74f828751f35d845e625052386530de9722 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357749 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by:
Jun Mukai <mukai@chromium.org> Reviewed-by:
Greg Kerr <kerrnel@chromium.org> Reviewed-by:
Darin Fisher <darin@chromium.org> Reviewed-by:
Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#799386}
-
Daniel Cheng authored
The current browser-side navigation code can ask the renderer to commit a MIME type that it cannot handle. When this happens, the renderer simply ignores the commit request, tripping the CHECKs added in https://crrev.com/796508. For now, allow these commits to silently fail and not commit a new document... Bug: 999255, 1115912, 1117282 Change-Id: I435831058db8e059b0389a8e2262f6bd72e875fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360602 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#799385}
-
Anupam Snigdha authored
Before this change we used to set the pointer type to touch only when DoDefaultAction was called. This led to issues as sometimes I don't see this API being called when narrator is active and the user double taps on the edit control to set the selection. VK should show up when caret starts blinking in the edit control, so we set the pointer type to touch when we receive focus from the narrator and then in blink we invoke a call to show the VK if the focus happened to be inside an edit control. FWIW, I discussed this with narrator team and it is hard to come up with a solution that is deterministic and reliable as narrator eats up all the gesture events and VK is controlled by a different component that relies on VK show call from Chromium when input modality is touch and input policy is set as manual(Chromium specific). This solution is just a heuristic. Bug: 1106556 Change-Id: I12fcfcda52ba058ed5377b0312e6652988dacced Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2361045Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Anupam Snigdha <snianu@microsoft.com> Cr-Commit-Position: refs/heads/master@{#799384}
-
Kenichi Ishibashi authored
crrev.com/c/2340417 replaced a C++ method call with a mojo method call. Apparently, the method, GetUserDataForAllRegistrations(), is called when a profile is created on weblayer. It seems we need to wait for the callback of GetUserDataForAllRegistrations() to be completed when a profile is created or updated. Bug: 1115172 Change-Id: I2b5f6614171b3502130127109bbe6822493f5497 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352268Reviewed-by:
-
Fred Mello authored
https://docs.google.com/document/d/1Xg4VKZ7YWNS4jUpxoXOWXP5yI8Gy7HzaUIBzplrDkOA Bug: 1112872 Change-Id: Ic78efa44cdd30350e6f82875b483807ae1baca79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360230Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
-
Meredith Lane authored
This CL is a follow up to https://crbug.com/1016615, and stores the users chosen font magnification size as a preference. AXRelnotes: N/A Bug: 1016615 Change-Id: I4a2331edf7d36fa12a5e260fef863cd495d90bdd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212222Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Meredith Lane <meredithl@chromium.org> Cr-Commit-Position: refs/heads/master@{#799381}
-
Orin Jaworski authored
This CL fixes the translate Pedal behavior by relying on the translate manager to determine appropriate page translation, languages, etc., instead of driving the UI directly with info from client and language state. The new behavior is described in the translate manager comment: Initiate a manually triggered translation process for the current page. Collect source and target languages, and show translation UI. If |auto_translate| is true the page gets translated to the target language Bug: 1117542 Change-Id: I270d29f966646bbf4508c4e041383bcb47e5ed26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363907 Commit-Queue: Orin Jaworski <orinj@chromium.org> Commit-Queue: Tommy Li <tommycli@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Auto-Submit: Orin Jaworski <orinj@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#799380}
-
Akihiro Ota authored
This change: 1. Adds content for tab, shift + tab, enter, and using selects to the OOBE tutorial. 2. Makes lesson content reachable via tab and shift + tab. Bug: 1075752 Change-Id: I79ad352c15cf6483b12c43dd43611c891f93f669 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358133Reviewed-by:
-
Dirk Pranke authored
This adds an optional --isolated=outdir=PATH flag to the test executable API; this gives the test runners a stable path to the output directory from a swarming task, so that we can key other files off of it without needing to pass them all explicitly via the command line. This also adds the arg to the isolated_script wrapper, so that we those types of tests can handle the flag (by ignoring it for now). We may need to work through the other cases (like gtest tests) individually, which will be done in subsequent CLs. Bug: 816629 Change-Id: Ibff6a47544bf94af5d7693a8446dfb669351cc07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358604 Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by:
Dirk Pranke <dpranke@google.com> Reviewed-by:
Erik Staab <estaab@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#799378}
-
Christian Biesinger authored
This exposed a bug where we don't correctly compute the cross size in a column flexbox with aspect-ratio. R=ikilpatrick@chromium.org Bug: 1045668,1117279 Change-Id: Ic823ed349e2caf061834e116d5958832745cd63a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358827 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#799377}
-
Peter Kotwicz authored
This CL renames IDS_SHOW to IDS_SHOW_CONTENT in components/component_strings.grd so that it no longer conflicts with components/browser_ui/strings/android/browser_ui_strings.grd I renamed the string as opposed to deleting the copy because the two strings are used for different purposes. IDS_SHOW in //components/component_strings.grd is used to toggle hiding and showing content IDS_SHOW in components/browser_ui/strings/android/browser_ui_strings.grd is used as text in button in a dialog. BUG=1093825 Change-Id: If77186cd7c52c3cdb0002b05d9c91628421a5ebe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358770 Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#799376}
-
