- LiteGraph caches a widget's .width the first time it lays a custom-typed
widget out and reuses that cached value on every later draw() call. For a
divider/status/preset widget added before the node reaches its final size,
that cached width goes stale and never updates, making section-divider
lines and the status box stop partway across the node instead of spanning
it, and clipping/unevenly sizing the preset chips. All three shared
widgets now read node.size[0] directly in draw() instead of trusting the
widgetWidth parameter, which sidesteps the stale cache entirely.
- Add a ?v=2 query string to every import of the shared/*.mjs modules.
aiohttp's static file server doesn't send Cache-Control: no-store for
these (unlike the top-level registered extension .js files), so browsers
were free to keep serving an old cached copy even across a hard reload.
A versioned import URL forces a fresh fetch regardless of cache state.
- Add js/shared/{nodes2,canvas_widgets,preset_picker_widget}.mjs: widgets
registered with type "button" get hijacked by ComfyUI's Vue widget
registry (Nodes 2.0), which renders a generic button showing the raw
internal widget name instead of calling our draw(). Dividers/status
boxes now use type "custom" via addCustomWidget, which correctly falls
through to the legacy-canvas bridge in both renderers. The interactive
preset-chip picker is dual-path: canvas+hit-testing in classic mode,
real <button> elements via addDOMWidget in Nodes 2.0 (mirrors how
ComfyUI-Pixaroma solved the same problem for its own widgets)
- Rewire smart_batch_resize.js, smart_resize.js, smart_profile_switch.js,
smart_prompt_controller.js to use the shared factories, removing the
duplicated divider/status/preset-chip code that existed across them
- Fix a save/reload regression found during verification: repositioning
the Nodes 2.0 preset-chip DOM widget into the middle of node.widgets
after configure() has run desyncs Vue's value-to-row binding for every
later widget (values appear shifted by one row, though the saved JSON
itself is correct). The DOM widget is no longer repositioned under
Nodes 2.0; classic mode is unaffected and keeps the original placement
rubz