Conversation
There was a problem hiding this comment.
Pull request overview
该 PR 旨在修复微信支付（LiteApp 键盘检测路径）中指纹遮罩/键盘遮罩在键盘收起后无法正确消失的问题，确保 UI 状态能被完整恢复。
Changes:
- 在检测到键盘从“显示”切换到“隐藏”时，同时移除指纹遮罩与键盘遮罩（
keyboardCoverLayout）。 - 在清理保存的状态映射前，先恢复密码区域子 View 的 alpha/clickable 状态，避免残留不可见/不可点击状态。
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
| restoreKeyboardContainerHeight(mKeyboardContainer); | ||
| cancelFingerprintIdentify(); | ||
| // Restore child view states before clearing | ||
| restoreChildViewStates(mKeyboardPasswordLayout, true, mSavedAlphaMap, mSavedClickableMap); | ||
| mSavedAlphaMap.clear(); | ||
| mSavedClickableMap.clear(); |
There was a problem hiding this comment.
In this LiteApp keyboard-hide path you rely on cancelFingerprintIdentify() to stop the biometric flow, but cancelFingerprintIdentify() is a no-op when fingerprintScanStateReady == false and also won’t reset mMockCurrentUser. If the dialog is dismissed while identify is initializing, the mock-user state can remain enabled. Consider either (a) setting mMockCurrentUser = false here and clearing mFingerprintIdentify, or (b) updating cancelFingerprintIdentify() to always call cancelIdentify() regardless of fingerprintScanStateReady.
No description provided.