max / makenotwork

Point the library collections refresh at its own panel Second instance of the regression step 1 shipped and step 3 caught the first of. Creating a collection refreshes /library/tabs/collections into #tab-content, which the library conversion made the strip rather than the panel, so adding a collection replaced the whole tab strip with a page of collections. Found by grepping the user dashboard's surfaces before step 5, which is the check the strip conversions want run over every template the panels reach and not only the page being converted.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-08-19 16:55 UTC

Signed with PGP, not checked

Commit: a5106f8510c9db99e3eb5b3eef73b7c56db49949

Parent: 2877f60

1 file changed, +4 insertions, -1 deletion

M server/static/tab-library-collections.js +4 -1

			@@ -1,5 +1,8 @@
1	1		document.getElementById('new-collection-form').addEventListener('htmx:afterOnLoad', function(evt) {
2	2		if (evt.detail.xhr.status >= 200 && evt.detail.xhr.status < 300) {
3		-	htmx.ajax('GET', '/library/tabs/collections', { target: '#tab-content', swap: 'innerHTML' });
	3	+	// `#library-collections`, this tab's own frame. The library strip is
	4	+	// described (`6b24f2df` step 1), so `#tab-content` is the strip itself
	5	+	// and refreshing into it would replace the whole strip with one panel.
	6	+	htmx.ajax('GET', '/library/tabs/collections', { target: '#library-collections', swap: 'innerHTML' });
4	7		}
5	8		});