- 11 Oct, 2019 40 commits
-
-
Hitoshi Yoshida authored
"async iterable" and "iterable" are literally similar, but have different definitions in spec. And it provides us following benefit to separate "async iterable" and "iterable"; - It makes easy to dispatch different functions in the code generator. https://cs.chromium.org/chromium/src/third_party/blink/renderer/bindings/scripts/web_idl/ir_builder.py?q=ir_builder&dr&l=104&rcl=489221aa216913b574354b09ff94469151b682b4 is a bad example that comes from setting "callback" property on "interface" node. - Current code generators do not support "async iterable", but they accidentally accept it as "(synchronous) iterable" without throwing errors. This CL makes it an error. Bug: 839389 Change-Id: Ie48829802ac2a73916ba081459208c0d11f13740 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855540 Commit-Queue: Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#705022}
-
Gyuyoung Kim authored
To reduce pre-processed size of header files have been including foo.mojom-blink.h, this CL replaces .mojom-blink.h with .mojom-blink-forward.h in blink header files. This CL has no behavior changes and following CLs will continue replacing them more. Bug: 1001360 Change-Id: I42c62234c64878d23057366df8823eb94a8a5e6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852354 Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#705021}
-
arthursonzogni authored
The FrameHostInterceptor observe RenderFrameHost creation and destruction. In its constructor, it simulate observing RenderFrameHost creation for every active RenderFrameHost. It misses the ones in the BackForwardCache. This causes a mismatch later when it observe a RenderFrameHost deletion. Change-Id: Ifabf5eab92f3275d71e5a7d760f44e4178e00d6a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816509 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#705020}
-
Fredrik Söderquist authored
When no more intervals can be resolved, ResolveInterval(...) will return an interval that return false from IsResolved() (meaning it has no finite begin time). When this happens we should "clear" |interval_| by setting it to an unresolved interval. This fixes the behavior of SVGAnimationElement.getStartTime() which now correctly report (throws) when the last interval of element has ended. Add a new test for that and move an old somewhat related test to WPT. Also adjust SVGAnimationTestCase.js which uses this to offset the sample times (although in most cases) to avoid the debug dump when there's no current interval (no tests actually rely on the old broken behavior). This makes us match Firefox. Bug: 998526 Change-Id: Idcf348343768ffc9392e29af2e976b9a3a1e31aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849897Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#705019}
-
Morten Stenshorne authored
This ensures that we have room for the tallest piece of monolithic content, and also the tallest container with break-inside:avoid. There are more things we could pay attention to here, but at least for now we don't. We could take break avoidance between siblings into account, and also orphans and widows. Orphans and widows are honored when balancing in the legacy engine, but it's somewhat buggy; see crbug.com/1013151 - it may lead to taller columns than necessary. The net increase in passing tests isn't impressive, but this is largely due to lack of support for fragment painting. The "regressing" span-all-dynamic tests are laid out more correctly now than before, but doing things dynamically vs. doing it right away matters for the fragment painting code. This CL also introduces a mild regression. By honoring unbreakable content, we should also make sure that underflow is ignored (i.e. content that comes before the start of a fragmentainer, caused by negative margins). Otherwise we risk overstretching. This is what fast/multicol/balance-line-underflow-1.html is about. I'll submit a separate CL for that, since this one is big enough on its own. Bug: 829028 Change-Id: Iee389525c34961a7748bd5597f22c75026919671 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854224 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#705018}
-
Hirokazu Honda authored
There are two modes in VEA, native input mode and non native input mode. In native input mode, a input buffer given by VEA client is a graphic native input buffer. The buffer alignment is decided in minigbm implementation. It is 64 and 4 for width and height, respectively. In non native input mode, the buffer is a shared memory based buffer. The width and height is specified by VEA. crrev.com/c/1810453 changes a dimension alignment for an input buffer in HW video encoder using VA-API. The width and height are aligned by 16 before the CL. The width is aligned by 64 and height aligned by 4 since the CL. For example, if a configured encode stream size is 176x144. | A size of buffer | VA Surface size | VA surface size for | given by client | for an input buffer | a reconstructed surface N-I mode | 192x144 | 192x144 | 192x144 non N-I mode | 192x144 | 192x144 | 192x144 This change causes a lot of failures in chrome encoder test (crbug.com/1009297) and CTS (b:142210669). This CL is expected to mitigate the failures. A reconstructed surface size is the same as coded size, whose width and height both are aligned by 16. The size of a buffer is the same as coded size in non native input mode. This is fine because an input buffer is copied in a client size in non native input mode. The sizes in the above example are below. | A size of buffer | VA Surface size | VA surface size for | given by client | for an input buffer | a reconstructed surface N-I mode | 192x144 | 192x144 | 176x144 non N-I mode | 176x144 | 176x144 | 176x144 Bug: 1009297, 1005205 Bug: b:142210669, b:142217112, b:142091557 Test: EncodeDecodeTest#testEncodeDecodeVideoFromBufferToBufferQCIF on caroline Test: VEA unittest on eve Change-Id: Ibca0f951ace886fcbeb8031e886c196913f69cca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847432Reviewed-by:Pawel Osciak <posciak@chromium.org> Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#705017}
-
Yutaka Hirano authored
We would like to understand how common it is to serialize / transfer non-Origin-clean ImageBitmap. Bug: 1013087 Change-Id: Id593ee1e1e448d9cd234638d2e86d4893e13f8d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852346 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#705016}
-
Gyuyoung Kim authored
To reduce pre-processed size of header files have been including foo.mojom-blink.h, this CL replaces .mojom-blink.h with .mojom-blink-forward.h in blink header files. This CL has no behavior changes and following CLs will continue replacing them more. Bug: 1001360 Change-Id: Ib32bcfd0a27a50a74d433ff77251a5f0ad14b604 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855238 Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Reviewed-by:
-
Hayato Ito authored
Disable flaky SingleClientBookmarksSyncTest.ApplyRemoteUpdateWithValidGUID on all platforms. Note that the previous CL, https://crrev.com/c/1855144/, was inntended to disable this test, however, the CL actually disabled another test for http://crbug.com/1012222 accidentally. TBR=mmoskvitin@google.com Bug: 1012223 Change-Id: Iadd0fa11535eb696d2f0cef516f22270723d34ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855319Reviewed-by:
Hayato Ito <hayato@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#705014}
-
dpapad authored
This is in preparation of migrating this UI to Polymer3/JS Modules, in which global namespaces like sync.confirmation will not exist. Bug: 1012533 Change-Id: I7fb3f6f3767a760d09c827acec133ef3f2c020f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853804 Commit-Queue: Thomas Tangl <tangltom@chromium.org> Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Thomas Tangl <tangltom@chromium.org> Cr-Commit-Position: refs/heads/master@{#705013}
-
Koji Ishii authored
The assumption is |NGLineBreaker::CreateBreakToken| always has a valid style. This patch adds DCHECK for the assumption. TBR=mstensho@chromium.org Bug: 1013040 Change-Id: Idbe5594136c8b1b9c4556dacf81631af49a56a06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855066Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#705012}
-
Koji Ishii authored
This test was unstable when I tried to rebaseline before, but wangxianzhu told me that Mac10.10 bots were unstable, and its instability was fixed. Re-trying the rebaseline. TBR=wangxianzhu@chromium.org NOTRY=true Bug: 1011453 Change-Id: Ic7f54ab756538e23cf17df3774863d62be99484e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855246Reviewed-by:
-
Nick Burris authored
Update the feature detectability API to window.location.fragmentDirective per https://github.com/WICG/ScrollToTextFragment/issues/19 Also updated web platform tests and confirmed tests pass. Bug: 1000308 Change-Id: Ib2391abe3d142d57cea61840e721ed35c81089af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850364 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#705010}
-
Colin Blundell authored
As part of the effort to replace base::Bind by base::Bind{Once, Repeating}, this CL converts the one usage of base::Bind() in //components/web_resource to instead be a usage of base::BindRepeating(). The rational for using base::BindRepeating() is that the callback is being passed in to a PrefChangeRegistrar, which can invoke it multiple times in response to pref changes. This CL also takes the opportunity to update the PrefChangeRegistrar API in question to take in a base::RepeatingClosure rather than a base::Closure. TBR=jochen@chromium.org Bug: 1007753 Change-Id: I7550f64eedb9d0da719f9ff8617e2c4d9d415eab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847216 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#705009}
-
Daichi Hirono authored
Previously ArcAccessibilityHelperBridges has used GetCaptionStyleFromPrefs. But it started adding "important!" token to override existing style, which Android side does not recognize. The CL stop using GetCaptionStyleFromPrefs and loads caption style directly from prefs. BUG=b:141660231 TEST=GetCaptionStyleFromPrefsTests.* Change-Id: Iee017eb3c5afd28205067df842f112cc553406a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1837437Reviewed-by:
Sara Kato <sarakato@chromium.org> Commit-Queue: Daichi Hirono <hirono@chromium.org> Cr-Commit-Position: refs/heads/master@{#705008}
-
Alexey Baskakov authored
Previously we did in-place immediate updates for existing apps. This was not consistent with the commit ideology since effects were becoming visible immediately. It didn't match the creation and deletion of apps: they were deferred until commit. With this CL we implement basic copy-on-write for WebApp object updates. We commit the created copy into the original for real, during the commit call. In next CLs: Fix UpdateSync algorithm to avoid excessive change_processor Put and Delete calls. TBR=alancutter@chromium.org Bug: 860583 Change-Id: I26eb53b668f74ce0c606a60af9016aa8a4cca1c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851792 Commit-Queue: Alexey Baskakov <loyso@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#705007}
-
Keishi Hattori authored
Replace ScopedPersistent in GarbageCollected classes with TraceWrapperV8Reference. Use of ScopedPersistent is discourage in favour of TraceWrapperV8Reference which is GC aware. Bug: 1013149 Change-Id: Idb131f7ff6af3bf405afe3ec3b2ae29ea67b42b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852349Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/6950a87f9054..a5f5e7778ad7 git log 6950a87f9054..a5f5e7778ad7 --date=short --no-merges --format='%ad %ae %s' 2019-10-11 jmadill@chromium.org D3D11: Fix warning that showed up in VS2019. Created with: gclient setdep -r src/third_party/angle@a5f5e7778ad7 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/+/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_optional_gpu_tests_rel TBR=geofflang@google.com Bug: None Change-Id: I7107839b8467a1ced9b64573edf87ec2eda2ceb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855206Reviewed-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@{#705005}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 535458f6. With Chromium commits locally applied on WPT: 23748e60 "Change text directive to text=" 2f7c5562 "Fetch Metadata: Split `sec-fetch-dest` out from other headers' tests." d52a9d07 "Port IndexedDB Blob Web Tests to web-platform-tests." 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, robertma@chromium.org: external/wpt/tools NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: Ib6a485ce3061beaf17c4dda316808db6a85db9f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853953Reviewed-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@{#705004}
-
Yoshifumi Inoue authored
Make LayoutTreeAsText to utilize NGInlineCursor instead of NGInlineFragmentTraversal::SelfFragmentsOf() This patch makes |LayoutTreeAsText| to utilize |NGInlineCursor| instead of |NGInlineFragmentTraversal::SelfFragmentsOf()| as preparation for migrating |NGFragmentItem|. Bug: 982194 Change-Id: I78a568464330228940e18ebd7cc836630627aea3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852324 Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-chrome BUG=762641 TBR=xiyuan@chromium.org Change-Id: I48c2e94c9ea998cf8992415fb2cba9d6206fdb53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855438Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#705002}
-
Lei Zhang authored
Instead of trying to handle a NOTREACHED() condition, just crash if the impossible happens. Change-Id: Ifbfdabe7e044c22c61b2e143d516d250319b6fe3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854245Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#705001}
-
Hayato Ito authored
The test is flaky on platforms other than mac. TBR=rdevlin.cronin@chromium.org Bug: 851252 Change-Id: I72f099a12c5c99c52eedd6bde6c335f8f169b61a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855064Reviewed-by:
-
Peter Kotwicz authored
This CL removes the UMA tracking which occurs in AppBannerUiDelegateAndroid destructor. As of http://crrev.com/c/1609744 AppBannerUiDelegateAndroid is only used for showing a dialog and is no longer used for infobars. - It is guaranteed that either AppBannerUiDelegateAndroid::OnUiCancelled() or AppBannerUiDelegateAndroid::AddToHomescreen() will be called, thus the UMA recording which occurs in the !has_user_interaction_ case can be removed. - TrackDismissEvent(DISMISS_EVENT_DISMISSED) is moved to OnUiCancelled() and AddToHomescreen(). This is in preparation for http://crrev.com/c/1833068 which changes when AppBannerUiDelegateAndroid's destructor is called. This CL also brings up to date the documentation for the AppBanners.UserResponse and WebApk.Install.InstallEvent UMA metrics BUG=994759 Change-Id: I44ee30b17a5a750aa7722ae8a3d4d2a0b52c05c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846562 Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#704999}
-
Chris Cunningham authored
CHECK is very aggressive - saving bad data is generally not a show stopper (except for data that causes FLT_EXCEPTIONS on win). The idea is to let this sit in pre-beta channels for a bit and find out if there are any remaining ways we can cause corrutpion. TODO(me): revert this before beta promotion. Bug: 982009 Change-Id: If2faf12e56a54bd7244f08aa940be2ace9781ca4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855199 Auto-Submit: Chrome Cunningham <chcunningham@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Reviewed-by:
Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#704998}
-
Frank Tang authored
https://chromium.googlesource.com/chromium/deps/icu.git/+log/93a34f0..5005010 5005010 Update IANA timezone db to 2019c 181ac4d Add "# COMPONENT" to icu OWNERS file 72f4754 Fix v8 formatRange/formatRange issues Bug: 473288,1004574, v8:9812 Change-Id: Ia73971d9399a0b699bd8940e9b4e3472cec891ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854570Reviewed-by:
Jungshik Shin <jshin@chromium.org> Commit-Queue: Jungshik Shin <jshin@chromium.org> Cr-Commit-Position: refs/heads/master@{#704997}
-
Chris Cunningham authored
debug::Alias did the trick. We were dividing by zero whenever a record with significant duration was saved to an empty bucket. Pretty awful bug. UMA shows this is causing 2% of DB reads to be discarded (assuming this is the sole remaining source of corruption). Bug: 982009 Change-Id: Ie13643a79652163bfaf343259af44141f2a53fc7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854796 Auto-Submit: Chrome Cunningham <chcunningham@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Reviewed-by:
-
Miyoung Shin authored
This CL converts AudioFocusManagerDebug{Ptr, Request} in content and services to the new Mojo type. Bug: 955171 Change-Id: I9b219438be413d57b0c97e635d39b48d8a2352b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849734 Commit-Queue: Miyoung Shin <myid.shin@igalia.com> Reviewed-by:Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#704995}
-
Jay Harris authored
Previously, it was available on all pages, regardless of whether they were considered secure. Policy for new web apis is to only expose them in secure contexts. Bug: 1013493 Change-Id: Id2c810309d4b21554b2ab11300d959a0bcf31102 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855149 Commit-Queue: Jay Harris <harrisjay@chromium.org> Commit-Queue: Matt Giuca <mgiuca@chromium.org> Auto-Submit: Jay Harris <harrisjay@chromium.org> Reviewed-by:
Matt Giuca <mgiuca@chromium.org> Cr-Commit-Position: refs/heads/master@{#704994}
-
Mikolaj Walczak authored
Send a wayland event to Android when user requests a density change (CTRL +/CTRL -/CTRL 0) on ARC++ application. BUG=b:142100473 TEST=`adb shell logcat -s libwayland-client:*' Change-Id: I550557eeb017fb24eef83cc09a7b0d809462d7b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846629 Commit-Queue: Mikolaj Walczak <walczakm@google.com> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#704993}
-
Ken Rockot authored
ScopedFeatureList is unsafe to use after browser threads have been started. This constraint will imminently be enforced by DCHECK to prevent further erroneous usage from landing. This CL corrects usage within Safe Browsing, SSL, and Policy related browser tests. This is split from a larger CL where in some rare cases, correction was too complex to resolve before landing the DCHECK, so corresponding test(s) may be disabled instead of fixed. Bug: 846380 Change-Id: Ie1d4e9241c53e0e8fe4ec504508f3d51dc9c1d6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850733 Commit-Queue: Ken Rockot <rockot@google.com> Reviewed-by:
Emily Stark <estark@chromium.org> Reviewed-by:
Nathan Parker <nparker@chromium.org> Reviewed-by:
Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#704992}
-
Sergey Ulanov authored
https://chromium.googlesource.com/angle/angle.git/+log/8ba50490174a..6950a87f9054 git log 8ba50490174a..6950a87f9054 --date=short --no-merges --format='%ad %ae %s' 2019-10-11 sergeyu@google.com [Fuchsia] Exclude libvk_swiftshader.so on Fuchsia 2019-10-11 timvp@google.com Vulkan: Prevent Creating ES 3.0 Context if Min. Caps. Not Met 2019-10-11 jie.a.chen@intel.com Fix the missing global memory barriers 2019-10-11 m.maiya@samsung.com Vulkan: Enable GL_OES_EGL_image_external_essl3 Created with: gclient setdep -r src/third_party/angle@6950a87f9054 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/+/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_optional_gpu_tests_rel TBR=geofflang@google.com Bug: None Change-Id: I535753ef5e55648b3a6b359f6312e591b76ddf39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855121Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
-
Makoto Shimazu authored
This CL converts base::Bind to BindOnce or BindRepeating, and also changes relevant base::Callbacks or base::Closures to appropriate types. This CL is split from https://crrev.com/c/1831621. This CL was uploaded by git cl split. R=dullweber@chromium.org Bug: 1007760 Change-Id: I067c7bb1680cb0c7cc72d9252d3075cf73aa5503 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849537Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Auto-Submit: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#704990}
-
Wenbin Zhang authored
In order to save CQ capacity, system_health_smoke_tests.py checks the story versions to make sure that we only run the latest version. The version check happens when loadng all the stories. When it fails, the try job shows all shards as failed, instead of reporting the correct info. Hers's an example from the bug: https://ci.chromium.org/p/chromium/builders/try/android-marshmallow-arm64-rel/369559 Since this is more a configuration issue, we now change it to be reported at an earlier stage, i.e., in PRESUBMIT. Bug: 1006771 Change-Id: I53882078a4784b460b2add78725ea18e8bfffddd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850353 Commit-Queue: Wenbin Zhang <wenbinzhang@google.com> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#704989}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/1ff0c181bb37..ee8e9c15222c git log 1ff0c181bb37..ee8e9c15222c --date=short --no-merges --format='%ad %ae %s' 2019-10-11 cepheus@frii.com Fix #1924: Promote SPV_EXT_physical_storage_buffer to KHR when required. Created with: gclient setdep -r src/third_party/glslang/src@ee8e9c15222c If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,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/+/master/autoroll/README.md TBR=radial-bots+chrome-roll@google.com,geofflang@google.com Bug: None Change-Id: Idad3ac27a5d2b2722cb0be533850a510c27b45a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855122Reviewed-by:
-
Julie Jeongeun Kim authored
This CL converts NetworkServiceClient from network_service.mojom to new Mojo types using PendingRemote, PendingReceiver, Remote, and Receiver. Bug: 955171 Change-Id: If04d706c02e97a4ddd647a61647865dc35dc4563 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847469Reviewed-by:
Naoki Fukino <fukino@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Julie Kim <jkim@igalia.com> Cr-Commit-Position: refs/heads/master@{#704987}
-
Christopher Cameron authored
This was the result of an infinite loop wherein - RWHVMac::OnFirstResponderChanged(true) would eventually call - (bunch of views::Views stuff) - RWHVMac::Focus() - Making the RWHVCocoa first responder, calling - RWHVMac::OnFirstResponderChanged(true) Early-out of redundant calls to RWHVMac::Focus, to break this loop. Bug: 998123 Change-Id: Iacf9abb6b03c07d11bd1168a7d9d7459a69fc554 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1848893Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#704986}
-
Hayato Ito authored
This reverts commit 8f8c19f0. Reason for revert: flakiness again See https://bugs.chromium.org/p/chromium/issues/detail?id=1000251#c25 Original change's description: > Revert "[Sheriff] Disable BookmarkBarInvisibleOnShutdown on Linux" > > This reverts commit 2e452bbf. > > Reason for revert: https://crbug.com/1000251 is fixed. > > Original change's description: > > [Sheriff] Disable BookmarkBarInvisibleOnShutdown on Linux > > > > TBR=weidongg@chromium.org > > > > Bug: 1000251 > > Change-Id: I8e3372766ab9e560c9f47f7c2f8292ebc8af644c > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782637 > > Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org> > > Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#692666} > > TBR=jdoerrie@chromium.org,weidongg@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 1000251 > Change-Id: Id9af5a221f5ca04873ce30737c2a9be58afd9fb3 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844854 > Reviewed-by: kylechar <kylechar@chromium.org> > Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org> > Commit-Queue: kylechar <kylechar@chromium.org> > Cr-Commit-Position: refs/heads/master@{#703303} TBR=kylechar@chromium.org,jdoerrie@chromium.org,weidongg@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1000251 Change-Id: I5f798d35aee20756268151c510c27a7a5bcf5515 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855245Reviewed-by:
-
Yoshifumi Inoue authored
This patch implements |NGFragmentItem| version of selection painting by using |NGInlineCursor| to share logic with |NGPaintFragment| version. Bug: 982194 Change-Id: I44bd0e1b93db611fb03459179dda0bf5d350167d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832843 Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
-
Jeremie Boulic authored
When creating new folders from the directory tree, the new entry was sometimes added in the wrong spot due to the way labels were compared. The folders were then immediately reordered, causing the new folder to lose its renaming state with the corresponding input box. Issue fixed using the util.compareName function. Test to be added. Bug: 1004717 Change-Id: I1005e1061b099b195ea87d4b50b0a121f17d593b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855145 Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#704983}
-
