The mobile composer/footer slid over the message list when the user swiped with the keyboard up. Cause: --vv-height / --vv-offset-top were routed through React state via useMobileKeyboard, so on iOS — which fires visualViewport scroll/resize on the same frame as its keyboard animation — the .chat-thread translation lagged by one paint, visible as the composer momentarily floating over messages. Now those two vars are written imperatively in a useLayoutEffect directly to the .chat-thread DOM node on every visualViewport event, mirroring the working pattern at QuickChatFAB.tsx:1032-1052 (which already works correctly on mobile). Only --keyboard-overlap (a structural open/close signal, not per-frame) still flows through React state. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 line
758 B
Plaintext
1 line
758 B
Plaintext
{"version":3,"file":"fusion-skill-install.d.ts","sourceRoot":"","sources":["../src/fusion-skill-install.ts"],"names":[],"mappings":"AAeA,eAAO,MAAM,iBAAiB,WAAW,CAAC;AAE1C,MAAM,MAAM,+BAA+B,GACvC,WAAW,GACX,mBAAmB,GACnB,UAAU,GACV,SAAS,GACT,SAAS,CAAC;AAEd,MAAM,WAAW,8BAA8B;IAC7C,OAAO,EAAE,+BAA+B,CAAC;IACzC,SAAS,EAAE,MAAM,GAAG,IAAI,CAAC;IACzB,SAAS,EAAE,MAAM,CAAC;IAClB,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAED,wBAAgB,iBAAiB,CAAC,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,CAI1D;AAED,wBAAgB,8BAA8B,CAAC,SAAS,SAAkB,GAAG,MAAM,EAAE,CAUpF;AAED,wBAAgB,+BAA+B,IAAI,MAAM,GAAG,IAAI,CAQ/D;AAED,wBAAgB,6CAA6C,CAAC,UAAU,EAAE,MAAM,EAAE,GAAG,MAAM,GAAG,IAAI,CAMjG;AAED,wBAAgB,gCAAgC,CAAC,OAAO,GAAE;IACxD,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CACtB,GAAG,8BAA8B,CA+EtC"} |