digital-garbageandClaude Opus 5
b62e88f44f
A floating window remembers its position per id, and only the DRAG handler clamped. So a window moved to the right of a wide screen and reopened on a narrow one opened entirely off the viewport: no titlebar on screen to grab, nothing to drag back, and the position remembered -- unrecoverable without clearing localStorage by hand. Reproduced at x=1400 in an 800px viewport. The clamp lives in apply() now, so every path goes through it: opening, restoring a remembered box, coming back from maximised, and the viewport shrinking under an open window. Also guarded for a viewport narrower than the grabbable strip, where the old bound went negative and pushed the window further off rather than back on. jsdom cannot see any of this -- getBoundingClientRect is zeros there, so a window off the right edge measures identically to one in the middle. The three tests are Playwright, and removing the clamp fails two of them. And POST /api/pipeline could not accept an empty pipeline: `slots or default()` resurrects the built-ins, because an empty list is falsy. A client that removed every slot got them handed back. Absent means "use the default"; empty means "there is nothing", and only one of those is a fallback. One of the tests I first wrote for this asserted len(x) < len(y) + 1, which is true of almost anything. It counts the pipeline at every step now and fails if it ever grows. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ComfyUI-FunPack v5 — "Cunning Cranberry"
FunPack v4.0.0 is going to be the latest release of classic FunPack. Next update is another milestone update, or shall I say, a full rework.
Maintenance of current FunPack became a mess — forgetting to add or remove buttons from/to UI, finding functions that don't do anything but still present in the code absolutely randomly, trying to keep the UI neat while it has no strict boundaries on how it should look like, and of course — making it easy for users to understand how FunPack operates and how you can operate it — this is all time, money and token-consuming.
General idea behind the FunPack v5 rework is writing it from scratch, with a new architecture where a feature can't be forgotten, where a wire can't be missed, where one failing module never stops whole process from executing. Loaders and features would tell the UI by themselves what sorts of inputs they need and where to put it — and UI will compose them according to design guidelines it would have. Samplers would become independent from features — if a feature is available and enabled, sampler would call it. If it's not — it gets skipped and doesn't even appear in the UI so it won't confuse you.
Most of this comes from a FunUI backend draft that got shelved after understanding on how much time has to be invested into polishing it. Without a community support and wide usage it would become another dead project only one person in the world needs but no one else.
Come to think of it, FunPack already became something alike, with an exception — this project is more than alive, and while I can, I will support it.
Final goal is to make FunPack an ultimate answer for a novice's question "I don't know how to generate — what do I install and how do I start?" and for a professional's question "I need a UI with all the cutting edge techniques available on day 0 — which one?"
Preparation for the v5 had started.
FunPack v5.0 "Cunning Cranberry" — coming fall 2026.
This branch is a clean start. Classic FunPack lives on main.