You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v0.3.9 — Model panel UX, first-open flash fix, and mobile layout
Fix the composer model panel flashing at the wrong position the first time it opens: opening replaces the laid-out trigger with an absolutely positioned panel, and the positioning effect ran in useEffect, so the browser had already painted an initial left: 0 frame before the measurement and compensating offset were written. It now uses useLayoutEffect, which measures before paint. A second open rarely showed it because the measurement was already available.
Fix the settings card overflowing its bounds on narrow screens, which needed horizontal dragging to read: the layout was written entirely as inline style objects, and an inline style cannot carry a media query, so the fixed widths and multi-column grids never reflowed. The settings layout now lives in settings.module.css and reflows on the same breakpoints dsh-web-mobile uses: ≤1023px releases the badge cluster's fixed track, ≤767px collapses paired fields to one column and gives the 1M switch its own row, and ≤480px stacks every label above its control and drops the 136/140/180px floors and the 154px badge track. Pinned to a 280px card the context-length and input-capability rows — the two that used to stick out — now fit, and 320px and above are unchanged. The rules only ever touch this plugin's own classes and use no !important, so they cannot fight dsh-web-mobile or any other plugin that rewrites the core UI.
The model capability panel (模型能力与档位) no longer jumps to the top after a save: the refresh a save triggers keeps the current model list mounted (the loading placeholder now appears only on the first read, before anything is loaded), so the scroll position and the row you just edited stay in place.
The success notice is now a floating badge anchored to the settings panel's top-right corner instead of an inline pill in the page title. It uses position: sticky so it stays pinned to the panel's right edge and visible no matter how far you scroll within the panel, and it fades out on its own after about 3 seconds (any field edit clears it, so a later save re-shows it and restarts the countdown).
The context length field now accepts k (any case) as a ×1024 multiplier, so 64k means 65536; the stored value is still an integer and the validation message was updated to match.