D20573 has one issue where the "Select" buttons in the "Merge Duplicates In" dialog are now closing the dialog. We might be missing a JX.pass() / e.prevent() (hopefully) or might need to get slightly more creative in distinguishing between navigation links and javascript magic links.

D20573 will fix this, but perhaps not in the most graceful way possible.

This likely affects other similar dialogs. The fix is to duct-tape something in Quicksand to something in the "click an area to click a link" behavior, most likely.

Quicksand isn't really bound by natural law, but I think that might fix it.

I marked D17919 as fixing this. I can't reproduce it after that change (except: the drag-select behavior isn't converted yet) and we're now Quicksand-aware, although it's possible I'm just not doing the right sequence of operations.

The keyboard reticle has been fixed but the inline reticle is still at large.

I believe this is now resolved by the series of changes attached to T12616. In particular, D17840 introduced Quicksand-aware state to changeset lists.

The keyboard reticle probably has the same issue but we can figure that out later.

Oh, this actually is the inline reticle, not the keyboard reticle.

I believe the resolution of T8151 also resolved this.

Thanks for the report! We were just missing a "/" (Quicksand does not follow redirects, which I think is desirable, although maybe we'll change that eventually) but D17151 should fix this up a little more robustly.

Oh, sorry, I meant: if security.alternate-file-domain was configured, that prevented this problem.

Well, I do not have configured the security,alternate-file-domain.
But it works now for me with this fix :D

I'm reasonably sure that fixes it; let us know if you're still seeing issues after updating.

(This likely would not be reproducible on any instance which has security.alternate-file-domain configured, which is why it wouldn't reproduce here or in the Phacility cluster.)

This reproduces somewhat-reliably for me with Quicksand (Persistent Chat) on.

You are right, I also can't reproduce it on the Phacility instance. I really don't know what do do next ^^

Please take the time to try to reproduce the issue on a Phacility instance, and report back if you can. We have not been able to reproduce the issue with these set up steps. Reproduction steps must includes everything we need to review and fix the issue locally.

{auto-playing-audio WilhelmScream.mp3}

Welcome to the wonderful, spooky world of Quicksand.

T11092 has a lot of discussion, but D16031 will almost certainly prevent this from doing damage. It does not fix the underlying Quicksand issue, but you should get an immediate error instead of confusing/spooky behavior/apparent data loss.

See also:

Thanks for the discussion and for improving the clarity of my request.

I expect we'll do this eventually, but probably not until Workboards v4.

Thanks for the quick fix !