fix(ratewise): 修復 360px 底部留白死類與 v2 小高度視口鍵盤遮擋(#662、QA-J J-1) - #675
Merged
s123104 merged 1 commit intoJul 7, 2026
Merged
Conversation
- breakpointTokens 新增 slim(≤360px)raw 斷點,main 底部留白改用 slim: 生效類名取代 max-[360px] 死類 - design-tokens 測試改為 postcss+tailwindcss 編譯層斷言,驗證實際產出 max-width:360px 的 84px 規則 - v2 補齊 snug(≤805px)/compact(≤760px)壓縮梯次,360×740/360×800 鍵盤底列不再被固定底導覽遮蓋 - ConverterV2Skeleton 同步梯次;e2e 零捲動矩陣擴 360×740/360×800 並守門 84px 留白 測試:typecheck、vitest 9222 passed、converter-v2 e2e 28 passed、dist CSS 產出驗證 Co-authored-by: Cursor <cursoragent@cursor.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Contributor
|
✅ SEO 審計通過!所有 2026 標準驗證項目都符合要求。
|
This was referenced Jul 7, 2026
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.
Summary
修復兩處小螢幕佈局缺陷(同區域、單一 PR):
max-[360px]死類:repo Tailwindscreens為 object 格式(含 raw 高度斷點),max-[...]任意變體不會產出 CSS——layout.ts的max-[360px]:pb-[calc(84px+...)]是死類,≤360px 裝置底部留白停留 56px;且design-tokens.test.ts以字串斷言反向固化死類。Closes #662
修法
#662:slim 斷點進 SSOT(比照 #660 narrow/xnarrow 模式)
breakpointTokens.screens新增slim: { raw: '(max-width: 360px)' },tailwind.config.ts同步註冊navigationTokens.mainScroll.paddingBottomClass改用slim:pb-[calc(84px+env(safe-area-inset-bottom,0px))]生效類名postcss + tailwindcss編譯層驗證:類名必須實際產出@media (max-width:360px)下的 84pxpadding-bottom規則(同 object screens 條件,死類回歸即紅燈)J-1:v2 壓縮梯次補齊(749px 恆定根因)
根因:v2 佈局(雙列卡、sparkline、4×4 keypad)全部只有
short:(≤700px)一級壓縮;701–805px 高度帶(360×740、360×800 落此區間)無任何梯次生效,佈局採未壓縮的固定高度(鍵高 54px、sparkline 72px、gap-3……),keypad 底緣的文件位置恆為 749px——視口再矮也不縮,735px 以下必被 fixed bottom nav(含 56px main 留白)遮住。非百分比高度問題,是固定高度+梯次覆蓋缺口。補齊兩級(
short:以下既有梯次零變動):snug(新,≤805px)compact(既有斷點,v2 新增消費)ConverterV2Skeleton同步梯次避免載入期跳動。snug於 config 宣告在compact之前,維持「更小視口後蓋」的 cascade 順序。實測(dev 環境量測)
maincomputedpadding-bottom實測 84px(dist CSS 亦確認產出@media (max-width:360px)規則)screenshots/j1-before-360x740.png(+鍵整排被 nav 蓋住)→screenshots/j1-after-360x740.png(4×4 全鍵可見;QA 暫存不入版控,AGT-QA-01)測試
pnpm --filter @app/ratewise exec vitest run:190 檔 9222 passed 全綠converter-v2.spec.tse2e:28 passed(desktop+mobile),零捲動矩陣擴充 360×740/360×800 並新增 ≤360px 寬 84px 留白守門附註
small-viewport-layout-fix)Made with Cursor