| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(vscode-chat): honor chat font family + make input monospace Reported: chatEditor.fontFamily had no effect on the chat webview, and the input box rendered in the non-monospace UI font. Root cause: VS Code does NOT inject chatEditor.fontFamily into third-party webviews (only a fixed allow-list of CSS vars incl. --vscode-editor-font-family = editor.fontFamily is delivered), and .message-input used font-family: inherit (UI font). - Input box now uses --app-monospace-font-family (unified with code blocks). - New atomcode.chat.fontFamily setting (en + zh-cn). The provider resolves the chat font (atomcode.chat.fontFamily > chatEditor.fontFamily, else fall through to the editor.fontFamily CSS default), sanitizes it for safe CSS inlining, and injects it into the webview HTML via a stable <style id="atomcode-chat-font"> element. - Config changes apply LIVE (a chromeFont postMessage edits that same style rule) without reloading the active chat; the shared style element means a cleared setting truly reverts (an inline removeProperty could not clear a stylesheet rule). Note: the separate path-truncation report is already fixed on main (.tool-name-secondary wraps); it just needs the next extension release. Build outputs (webview/webview.{js,css}) are gitignored; regenerated on build. tsc clean, webview rebuilds, 15/15 webview tests pass. Not machine-verified in a live VS Code host. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Provider-URL: https://gitcode.com/atomgit_atomcode/atomcode | 3 个月前 |