A filed note stays filed, and the handles are asked for

Three things that all came from chapters being thought through too late.

A note put into a chapter came back out of it a few seconds later. The
server had it right the whole time; every sync rebuilds the local copy
from the server's answer, and the function doing that never carried
chapter_id — so each sync handed back a note belonging to no chapter and
the notebook took it in again. The bin's query left the column out too,
which would have unfiled anything restored from it.

A separator drawn in a notebook vanished when a chapter was opened.
"Which chapter is open" and "which list is on screen" were one value.
Opened beside or below, the list still shows the notebook — but
everything around it had switched to the chapter, so the notebook's own
separators were filtered away and a drag among its rows was measured
against the chapter's notes, found nothing, and did nothing.

And where a new note lands is now visible and yours to choose: pressing
in either place makes it the one being worked in, marked with a line
along its top and the word "here", and the + button names it.

Rearranging becomes a mode, switched on beside the sort menu — until
then no row wears a grip and none can be dragged. Filing a note is back
in the row's own menu, where starring and exporting already are; the
button that had appeared in every row is gone with its dialog. The
account panel closes with Escape.

Thirteen suites green: 335 browser checks, 241 unit tests.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
marcandClaude Opus 5 committed 2026-08-12 16:59:29 +02:00
1 parent 4bb86bc5ac
commit b2a5f051fe
12 files changed
+406 -291

No files matched your search

+17 -2
View File
@@ -35,6 +35,18 @@ try {
await p.waitForTimeout(300);
await p.locator(`[data-sort-option="${mode}"]`).click();
await p.waitForTimeout(900);
/* Rows are only draggable while rearranging is switched on — the handles
are asked for rather than standing in every row. The suite drags a lot,
so it turns the mode on with the order it belongs to. */
if (mode === "manual") await startMoving();
};
const startMoving = async () => {
const toggle = p.locator("[data-reorder-toggle]");
if ((await toggle.count()) && (await toggle.getAttribute("data-reorder-toggle")) === "off") {
await toggle.click();
await p.waitForTimeout(500);
}
};
/* ── three notes, made in a known order ── */
@@ -280,7 +292,7 @@ try {
});
check(exported, "downloads can be captured");
await p.getByTitle("Export").click();
await p.getByTitle("Export", { exact: true }).click();
await p.waitForSelector("[data-export-dialog]", { timeout: 10000 });
await p.waitForTimeout(600);
await p.locator("[data-export-dialog]").getByRole("button", { name: /Markdown/ }).click();
@@ -486,7 +498,10 @@ try {
const beforeTouch = await titles();
// The last row onto the first, so the order cannot come out the same by luck.
const rowCount = (await titles()).length;
check((await p.locator("[data-reorder-grip]").count()) >= rowCount, "every row has a grip to take hold of");
check(
(await p.locator("[data-reorder-grip]").count()) >= rowCount,
"with rearranging switched on, every row has a grip to take hold of"
);
await touchDrag(rowCount - 1, 0);
await p.waitForTimeout(2000);
check(