commit | 3e40e3e6f8eb90d0a729ce549cd31b1e39938165 | [log] [tgz] |
---|---|---|
author | Chris Lu <thegreenfrog@chromium.org> | Wed May 01 15:53:26 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 01 15:53:26 2024 |
tree | 29797858a6030a6ada4e01e48b915c8c9157ae7c | |
parent | 037e0a4b6161c381d85d153fb9b5b8f38d891760 [diff] |
[ios] Fix MagicStack UI Breakage when Toggling Feed off This issue is result of the MagicStackCollectionView pulling in the safe area insets when it never is within the safe area. For some reason, when toggling the feed off, the MagicStackCollectionView receives safe area insets, even though its final position is well outside of the safe area. By setting UIContentInsetsReferenceNone to the UICollectionViewCompositionalLayoutConfiguration, the items are not inset to safe area insets. (cherry picked from commit 54807a190664eee381f8332d3331f96f7959dd1f) Fixed: 333745588 Change-Id: I4e60fe6d555de2a7a953df96559268f0f50d5a61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5474384 Reviewed-by: Scott Yoder <scottyoder@google.com> Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1293809} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5505873 Auto-Submit: Chris Lu <thegreenfrog@chromium.org> Commit-Queue: Scott Yoder <scottyoder@google.com> Cr-Commit-Position: refs/branch-heads/6422@{#553} Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.