- 12 Jan, 2021 40 commits
-
-
David Bertoni authored
Service Worker support is now available in the Stable channel, so there is no longer a need for channel overrides. Bug: 1165397 Change-Id: Ie5a7e5a0b58814b40bcb94f437b784904f6164f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2612028Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#842383}
-
Tsuyoshi Horo authored
This member variable was introduced for Service Worker link registration by https://codereview.chromium.org/1781783002. Service Worker link registration was removed from the specification. And the logic was removed by http://crrev.com/c/792731. So this variable is not used anymore. Bug: 788604 Change-Id: Ieaf4f3cb31526d9767f4a6666f2c26a1109d0605 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622357Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Auto-Submit: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#842382}
-
Sara Kato authored
Bug: 1159562 Test: build Change-Id: I9619c4861c34dc6bcd537d752b4b57602ec4fdd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2615722 Commit-Queue: Sara Kato <sarakato@chromium.org> Auto-Submit: Sara Kato <sarakato@chromium.org> Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Reviewed-by:
Allen Bauer <kylixrd@chromium.org> Cr-Commit-Position: refs/heads/master@{#842381}
-
Reilly Grant authored
This change expands the manual test for transferIn() to send much more data and assert that many overlapping transfers will still complete in the correct order. Two changes are necessary to make these tests pass. First, when aborting a transfer on device close the ERROR_REQUEST_ABORTED should be mapped to an AbortError DOMException. Second, transfers should be tracked in a list rather than a map so that iteration order is well defined. Bug: 1153647 Change-Id: I248ce4724e391216783a6873809aca43e4690b96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2591928 Commit-Queue: Reilly Grant <reillyg@chromium.org> Reviewed-by:
James Hollyer <jameshollyer@chromium.org> Cr-Commit-Position: refs/heads/master@{#842380}
-
Harry Cutts authored
Bug: none Test: check virtual keyboard still appears with drawing tablets connected to a device in tablet mode, and that buttons on the drawing tablet (if any) still work. Change-Id: I7502a585443bda79c448c46e379703258d62ba81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622759Reviewed-by:
Michael Spang <spang@chromium.org> Commit-Queue: Michael Spang <spang@chromium.org> Auto-Submit: Harry Cutts <hcutts@chromium.org> Cr-Commit-Position: refs/heads/master@{#842379}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/de32c3d2de00..2c65da28a2ee 2021-01-12 natsu@google.com Default roll_aosp.sh to copy artifacts to vendor partition 2021-01-12 jmadill@chromium.org Vulkan: Use angle::FormatID instead of VkFormat. 2021-01-11 stha09@googlemail.com libstdc++: fix incomplete type for FramebufferCache 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 timvp@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: chromium:957519 Tbr: timvp@google.com Test: Test: ./scripts/roll_aosp.sh and build in AOSP Change-Id: Id14dfd0c2c2df4159dcb6a052a826ca031b9323c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622299Reviewed-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@{#842378}
-
Ian Kilpatrick authored
Previously if our initial block-size was indefinite, and we were a flexbox - we'd apply a series of additional invalidations to ensure correctness. These are cases where we can't guarantee "trust" in the value of NGLayoutResult::IntrinsicBlockSize, as it depends on "extrinsic" constraints such as a parent forcing a fixed-block-size or a %-block-size changing. In an upcoming patch, there are more cases where we treat an *initial* block-size as indefinite, even though ComputeBlockSizeForFragment will return a definite size. E.g. there will be a difference between ComputeBlockSizeForFragment, and ComputeInitialBlockSizeForFragment. This change makes the cache more precise in the above case, by always calling ComputeBlockSizeForFragment, but (importantly) giving an indefinite intrinsic-block-size where we can't trust NGLayoutResult::IntrinsicBlockSize. Bug: 1033476 Change-Id: I798fe7d50247a4eec0131ec46061b33484347e8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2621976 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#842377}
-
Corentin Wallez authored
This avoids doing the conversion from WTF::String to an enum once in the Blink bindings and once in the WebGPU module. Bug: chromium:852089 Change-Id: I8765631c2b0562bdabfc6af246cab0453de63593 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2621754 Auto-Submit: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by:
Kai Ninomiya <kainino@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Austin Eng <enga@chromium.org> Cr-Commit-Position: refs/heads/master@{#842376}
-
Yoichi Osato authored
This reverts commit f4b58578. Reason for revert: caused layout test CRASH: https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Tests%20(dbg)(1)/94262/overview Original change's description: > service worker: Simplify main resource "handler" & "interceptor" (3/3) > > Bug: 1138155 > Change-Id: Iafb12ae9de19e68e637e7fb990bb8439ec4df848 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2602307 > Reviewed-by: Asami Doi <asamidoi@chromium.org> > Commit-Queue: Matt Falkenhagen <falken@chromium.org> > Cr-Commit-Position: refs/heads/master@{#842305} TBR=falken@chromium.org,mstensho@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com,asamidoi@chromium.org Change-Id: I5b4756817dd149a9f721c5aaeb2da54aadaf4308 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1138155 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623572Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoichi Osato <yoichio@chromium.org> Cr-Commit-Position: refs/heads/master@{#842375}
-
Zufeng Wang authored
Makes subcategories searchable, but they don't appear in the search result snippets. Bug: b/172533871 Change-Id: I6b1e053929bc1a4ecada135ae582a5deba1e673a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2620740 Commit-Queue: Zufeng Wang <zufeng@google.com> Reviewed-by:
dstockwell <dstockwell@google.com> Cr-Commit-Position: refs/heads/master@{#842374}
-
Clark DuVall authored
This was reverted because the latest androidx.lifecycle library performs thread checks in the ComponentActivity constructor. The constructor calls LifecycleRegistry.addObserver(), so we can just override that method and make it a no-op when loading on a background thread. Bug: 1150600, 1160614 Change-Id: I52e6eb63ce0b4a9c90c002fe34281298b02ef9d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622005Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#842373}
-
Alan Cutter authored
This CL does 3 things: - Hides the Extensions menu item from web app windows when no Extensions are installed. - Fixes a bug exposed by the updated test where the Extensions puzzle piece would show when an Extension was installed due to the layout animation. - Addresses comments from https://chromium-review.googlesource.com/c/chromium/src/+/2602305 Bug: 1164829 Change-Id: I75e3fc5e8a7262316947b7322b825a10be3bb848 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2621512 Commit-Queue: Alan Cutter <alancutter@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#842372}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/d08c55317628..537f11c11412 2021-01-12 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 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: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I08a68dbd375f0fac31446100baa181eb6d5ab960 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623265Reviewed-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@{#842371}
-
Chromium WPT Sync authored
Using wpt-import in Chromium da4ff2f2. Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: foolip@chromium.org, lpz@chromium.org, smcgruer@chromium.org: external/wpt/tools NOAUTOREVERT=true TBR=robertma@google.com No-Export: true Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-input-fyi-rel Change-Id: Ide515c126e4da5b2cd43b10c1057cfa1f34fe21c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622460Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#842370}
-
Yoichi Osato authored
This reverts commit d409e5a5. Reason for revert: Caused IOS build error. example https://ci.chromium.org/ui/p/chromium/builders/ci/ios-device/176674/overview Original change's description: > Enable building ANGLE's end2end and white_box tests everywhere > > Previously were disabled on iOS and Fuchsia > > Bug: angleproject:5417 > Change-Id: I3e73e11b728ebfacb8082ce90f333193cb44a3d3 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2621926 > Reviewed-by: Dirk Pranke <dpranke@google.com> > Commit-Queue: Yuly Novikov <ynovikov@chromium.org> > Cr-Commit-Position: refs/heads/master@{#842338} TBR=ynovikov@chromium.org,dpranke@google.com,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: Ib8cf39cb0a73198f27cebbe997dd2d7350811655 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: angleproject:5417 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623730Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoichi Osato <yoichio@chromium.org> Cr-Commit-Position: refs/heads/master@{#842369}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=bindusuvarna@chromium.org Change-Id: I4143b62d2dbafe909db0454ba7b013955da121bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622330Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#842368}
-
Olga Gerchikov authored
Updated procedure that computes scroll timeline progress to accommodate for overlapping offsets. The update is to find last matching interval in the list of offsets. This is analogous to CSS property overrides where last specified property is applied. Bug: 1094014 Change-Id: I7d5c84e58bfea021f931b702d66a87d2d28aaf6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2508356 Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com> Reviewed-by:
Kevin Ellis <kevers@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#842367}
-
Stephen Chenney authored
Code in DarkModeFilter was applying a dark mode color filter to any painted content that had some other shader associated with it. Such shaders come from gradients, mostly, but also tiled images and some background images. This patch limits the application of the dark mode color filter shaders that are not images or paint records. The former because we should not be applying a naive color filter to images, and the latter because they should already have filters dark mode filters applied. Fixes: 1160239 Change-Id: Id7dfbf999d43d7a9f5953d1f5a5edc5a1c92fe07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622989 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#842366}
-
Keishi Hattori authored
ast_type_traits namespace was removed in https://reviews.llvm.org/D93244 Change-Id: I93b7cb789085185036f257a764afc3d6ee7c47ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2612589Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/master@{#842365}
-
Eugene Zemtsov authored
plus some minimal C++ code to make things compile Bug: 1094179 Change-Id: Idea9b5fec09aeb19be4748c1746178744e5991e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2619621 Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#842364}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/026943fd29be..53a231c0ae86 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: I7be859d6f99690fd6a819dc6cb4bfeb9b1d360b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623270Reviewed-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@{#842363}
-
Yoichi Osato authored
This CL disables DragMultipleTabsRightIntoGroup and DragAllToSeparateWindow on windows. TBR=sky@chromium.org Bug: 1164561, 1128774 Change-Id: I49c825f1950af449e765f0a3f2a1918b1ddfb3a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623570Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoichi Osato <yoichio@chromium.org> Cr-Commit-Position: refs/heads/master@{#842362}
-
Yutaka Hirano authored
- DataElement::SetToEmptyBytes and DataElement::AppendBytes are used only by tests. Remove them. - Pass base::Time by value, rather than passing by reference. Bug: None Change-Id: I50180b3dbf7292063a6221de424499f8ca907eb7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595761 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Reviewed-by:
Fabio Tirelo <ftirelo@chromium.org> Cr-Commit-Position: refs/heads/master@{#842361}
-
Ken Rockot authored
Bug: 1004256 Change-Id: I77c6539836d48687d78151f947ee26fb2f0b58ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617056 Auto-Submit: Ken Rockot <rockot@google.com> Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#842360}
-
Lukasz Anforowicz authored
This CL makes VerifyThatBrowserAndRendererCalculatedOriginsToCommitMatch slightly stricter - it now requires that browser-side and renderer-side have to agree whether the origin to commit should be opaque (previously browser-side origin would be ignored if renderer-side was opaque). The above is achieved by the combination of the following changes: 1. Extracting NavigationRequest::ShouldCommitOpaqueOrigin to account not only for sandbox flags, but also for network errors. Accounting for network errors in GetOriginForURLLoaderFactory allows to simplify (a bit) RFHI::ExtractFactoryParamsFromNavigationRequest.. 2. Focusing the origin calculations and checks on cross-document navigations. 2.1. Moving the VerifyThat...OriginsToCommitMatch call to RenderFrameHostImpl::DidCommitNewDocument (next to a similar check for browser-side vs renderer-side sandbox flags). 2.2. Tweaking NavigationRequest::GetOriginForURLLoaderFactory to use the last committed origin for same-document and back-forward-cache navigations. 3. Tweaking NavigationSimulatorImpl::BuildDidCommitProvisionalLoadParams to more accurately simulate the product code, by taking into account CSP headers that (through sandbox directive) end up committing an opaque origin. This new ability had to be used in one of unit tests tweaked by this CL. Bug: 888079 Change-Id: I86edbd6920a1e17abb4e1d20104c5356a4dc3ca8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581008 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#842359}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/cf65caef0129..6f7379c80b03 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 yoichio@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: yoichio@google.com Change-Id: I36880c105b84b666583b876c6520db1e51f7568a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622763Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#842358}
-
Sophie Chang authored
This is a reland of 9a33bf90 RELAND_REASON: This one got wrongly reverted. https://chromium-review.googlesource.com/c/chromium/src/+/2622582 should be reverted instead. TBR=sky@chromium.org,waffles@chromium.org Original change's description: > Componentize OptimizationHintsComponentInstaller for reuse on iOS > > This also makes the component available on incognito (which was an > oversight in previous support to have optimization hints be in incognito) > > Bug: 1154790 > Change-Id: I97a427d5af0f94fa0b5282032b8cef6ce754c81d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617866 > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Joshua Pawlicki <waffles@chromium.org> > Reviewed-by: Michael Crouse <mcrouse@chromium.org> > Reviewed-by: Robert Ogden <robertogden@chromium.org> > Commit-Queue: Sophie Chang <sophiechang@chromium.org> > Cr-Commit-Position: refs/heads/master@{#842267} Bug: 1154790 Change-Id: I547245f282f4088368e05f4910a414cea49b741f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622583 Commit-Queue: Sophie Chang <sophiechang@chromium.org> Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Cr-Commit-Position: refs/heads/master@{#842357}
-
Wei Lee authored
There are several ways to minimize CCA: 1. Clicking minimize button on the top bar of the window 2. Pressing "<-" (F1) button on the keyboard 3. Pressing "Alt + -" on the keyboard (Default behavior) 4. (Tablet mode) Swipe from left to right (Default behavior) When handling intent, we don't want users to minimize window. We have already removed the minimize button from the window (1). In this CL, for (2) we only proactively minimize window for non-intent instance. For (3), we prevent the default behavior for intent window. For (4), we explicitly disable the corresponding window property to totally disable it. Bug: b/175322338, b/175326967 Test: Manually Change-Id: I4b4fb91ab07dcd46bb61512fe2622770c0a4c373 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2619249Reviewed-by:
Shik Chen <shik@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#842356}
-
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: I6db1f918c5759d768083ef3b0cf17c8ec3dd9692 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623469Reviewed-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@{#842355}
-
Jonah Chin authored
This reverts commit 0c93bcb5. Reason for revert: An earlier change is causing a canvas video issue. This change depends on that change. Reverting both changes until the bug is resolved. See crbug.com/1164407. Original change's description: > Introduce mailbox-based version of VideoTextureBacking > > This CL introduces an OOPR compatible version of VideoTextureBacking and > updates PaintCanvasVideoRenderer::UpdateLastImage() to use this new > version in the OOPR codepath. > > More details about overall PaintImage effort: crbug.com/1023259 > Info about the OOPR-Canvas2D project: crbug.com/1018894 > > Bug: 1115217 > Change-Id: I4590cf16d6faef0e5575b0b4006ea88de89aa13d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419653 > Reviewed-by: Khushal <khushalsagar@chromium.org> > Reviewed-by: Dale Curtis <dalecurtis@chromium.org> > Commit-Queue: Jonah Chin <jochin@microsoft.com> > Cr-Commit-Position: refs/heads/master@{#826449} TBR=dalecurtis@chromium.org,khushalsagar@chromium.org,jochin@microsoft.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1115217 Change-Id: I3b1d370e7048eee9d8885651ee0e68b342340b9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623174Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Jonah Chin <jochin@microsoft.com> Commit-Queue: Jonah Chin <jochin@microsoft.com> Cr-Commit-Position: refs/heads/master@{#842354}
-
Alan Cutter authored
These methods call non-trivial methods and should be moved to the cc file. Change-Id: I9b24047da4d48e90022edfc53498332bb333ec89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616644 Commit-Queue: Alan Cutter <alancutter@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#842353}
-
Alexander Timin authored
Remove old-style deprecated macros and reduce confusion. R=eseckler@chromium.org,sunnyps@chromium.org,rockot@chromium.org BUG=1164298 Change-Id: Ibb827cb42b62fb0f00ae46bd082c8b4a6f17caa1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617782 Commit-Queue: Alexander Timin <altimin@chromium.org> Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#842352}
-
Honglin Yu authored
Add the "Call" postfix. TEST=compiles BUG=none Change-Id: Iddb96ff06e576be0231db154405a331375a3116e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2619103 Commit-Queue: Honglin Yu <honglinyu@chromium.org> Reviewed-by:
Andrew Moylan <amoylan@chromium.org> Cr-Commit-Position: refs/heads/master@{#842351}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1610387594-3b3bb0a15d14b239dcb6d81b73ae08ab0d827c57.profdata to chrome-win32-master-1610398040-59038019b78fe7d9277311f636fda97275a69be4.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I465aa6bbda21787870788599e0a0324d14834b7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623248Reviewed-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@{#842350}
-
Michael Crouse authored
Current usages do not run on the trybot, this change moves the code towards compiling and running successfully. Bug: 1165517 Change-Id: Ic9f06e296b9b5c4158923c3ba37f9a307a170776 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623530Reviewed-by:
Sophie Chang <sophiechang@chromium.org> Commit-Queue: Michael Crouse <mcrouse@chromium.org> Cr-Commit-Position: refs/heads/master@{#842349}
-
David Dorwin authored
The target already builds successfully when directly referenced. Bug: 1164524 Change-Id: I54c74b87be87069c005bed8416ac307d0eb7a5c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618961 Auto-Submit: David Dorwin <ddorwin@chromium.org> Reviewed-by:
Sharon Yang <yangsharon@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#842348}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/b2230ba88f16..d1a3011cd912 2021-01-12 jbudorick@chromium.org Revert "devil: make devil_env_test pass under py3. (reland)" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC sadrul@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:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: chromium:1007101 Tbr: sadrul@google.com Change-Id: Ie136edd232910dff2ce0dd136ff562aea8f2e4dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623252Reviewed-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@{#842347}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1610387594-9644082f15d83cc3788996ee889bd06710e6b3cf.profdata to chrome-mac-master-1610408110-5a618b6e0bdb5b4a60796f5aa8c6f6759f78cdd3.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ieab1de1e4012865a5b23466b92c7a14ca9bdcf00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623257Reviewed-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@{#842346}
-
Koji Ishii authored
Blink (legacy and NG) and WebKit does not hyphenate the last word in a paragraph, except when it is a single-word paragraph. However, when the containing block is narrow, sometimes authors want a long last word to be hyphenated. This patch changtes the heursitic to allow hyphenation if the line is a single-word line. CSS Text 4 has a property to control this behavior, but no browsers have implemented it yet. Bug: 1022415 Change-Id: Ibd8d8b132e540a142f18efc09a37fed2b207bfdf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599567 Commit-Queue: Kent Tamura <tkent@chromium.org> Auto-Submit: Koji Ishii <kojii@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#842345}
-
Sinan Sahin authored
Clean-up work after crbug.com/1153706 Bug: 1154731 Change-Id: I27a1003541b1ce577ca28f92f0b8aa5f0705b9c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622734Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Sinan Sahin <sinansahin@google.com> Cr-Commit-Position: refs/heads/master@{#842344}
-