Repository navigation
Conversation
Respect system insets and floating controls on schedule and permission screens. Stack dense header actions on narrow or font-scaled viewports.
Alexander-Noah
marked this pull request as ready for review
August 26, 2026 10:38
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 2 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Contributor
There was a problem hiding this comment.
审查结论
本次修改将 Android 顶部安全区移到固定页面边界,并按悬浮语音栏的实际位置缩小日历滚动视口;窄屏/大字体下的标题堆叠逻辑与账号操作区约束一致。权限页的可滚动剩余空间、底部手势安全区和长文案伸缩规则也与 #389 的验收契约相符,未发现会导致业务回归或布局目标失效的具体问题。
验证了固定提交范围 21841bc...d567175 的全部 6 个变更文件及其调用关系;git diff --check 通过,GitHub 上的 Frontend (lint, types, build) 检查通过。由于当前工作区未安装可执行的 frontend/node_modules,无法在本地重新运行 Jest/TypeScript/ESLint。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景
Android 设备在窄屏、大字体、刘海屏或手势导航场景下存在以下布局问题:
修改内容
为什么这样修改
仅在滚动内容末尾增加
paddingBottom,不能保证滚动视口始终避开悬浮语音栏。因此改为直接为滚动视口预留底部空间,使内容在整个滚动过程中都不会位于悬浮控件下方。Android 对自动安全区调整的处理与 iOS 不同,因此在页面容器上显式应用 Android 顶部 inset,同时保留 iOS 的自动调整行为,避免重复留白。
标题区域是否需要换行不能只依据物理屏幕宽度。将屏幕宽度除以字体缩放比例后再判断,可以同时覆盖窄屏和系统大字体场景。
验证
npm run typechecknpm run lint:0 errors,1 个未修改文件中的既有 warninggit diff --checkCloses #389