-
-
Notifications
You must be signed in to change notification settings - Fork 45
Android 15 Edge to Edge support #2988
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
📝 WalkthroughWalkthroughThis pull request updates the Possibly related PRs
Suggested labels
Suggested reviewers
Tip ⚡🧪 Multi-step agentic review comment chat (experimental)
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
⏰ Context from checks skipped due to timeout of 90000ms (1)
🔇 Additional comments (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
48f247e to
3976022
Compare
|
@avazirna I think it will be cruicial for you to test this on various layouts for this PR to be merged. I am concerned how this behaves on for example list or scrolling layouts, fragments with their own view etc. Also seems like there are a bunch of other considerations in https://developer.android.com/develop/ui/views/layout/edge-to-edge that we need to account and test for ? |
Yes, @shubham1g5, I spent a great deal of time testing this, but there can be aspects to polish. I will add some screenshots to make this more clear. |
|
Thanks for confirming @avazirna . Can you add a QA note to this PR along with a list of things that QA should test for this change as well and devices they should use. I think it's important for QA to know of this upcoming change beforehand as it's not in the QA's plans currently and might affect the timelines on the release signifcantly. |
| } | ||
| } | ||
|
|
||
| public int getRootViewId() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- this should be an abstract method as activities must implement this.
- On Connect, a single activity host multiple fragments with their own views. Is there no generalised way to get a root view of the current screen instead of assigning IDs to the xml layouts ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shubham1g5 I switched to content view
f15696f to
4f4aeaa
Compare
|
@damagatchi retest this please |
| import androidx.appcompat.app.AppCompatActivity; | ||
| import androidx.core.view.WindowInsetsControllerCompat; | ||
|
|
||
| public class NoCommCareActivity extends AppCompatActivity { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think we should have CommCareActivity also extend from this so that we only put this logic in one place, also might make sense to name it CommonBaseActivity if we do that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's a cleaner option - Refactor
shubham1g5
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a suggestion but nothing blocking.
3d4fbf5 to
27de8a2
Compare
Product Description
This PR makes the necessary changes to ensure compatibility with Android 15 Edge-to-edge mode. This consisted mainly of assessing the window insets and then adjust the padding of the system content view. The impact to the UI is:
Safety Assurance
Safety story
These changes will have to go through regression testing.
Labels and Review