seemore 1.2.0 → 1.3.1

package/README.md

@@ -103,7 +103,7 @@ Install **seemore** from the [VS Code Marketplace](https://marketplace.visualstu
 
 ## Edit your files from the browser
 
-The preview is not just for reading — it is the fastest way to fix what you are reading. Double-click any paragraph, heading, list item, quote or table cell and it opens in a small editor holding that block's **Markdown source**: `**bold**` stays `**bold**`, links stay links, tables stay tables. Fix the text and hit **Save** and the change is written to the file on disk. Nothing is written until you say so: clicking away leaves the editor open rather than saving behind your back. It works the same in the VS Code panel, which runs the same dev server.
+The preview is not just for reading — it is the fastest way to fix what you are reading. Double-click any paragraph, heading, list item, quote or table cell and it opens in a small editor holding that block's **Markdown source**: `**bold**` stays `**bold**`, links stay links, tables stay tables. Fix the text and hit **Save** and the change is written to the file on disk.
 
 Inline editing is for local previews only — `seemore build` output is static, so nothing is emitted there. It is on by default in dev; switch it off with the `!` prefix:
 
@@ -113,9 +113,6 @@ export default defineConfig({
 });
 ```
 
-> [!NOTE]
-> The dev server binds to localhost, so only your machine can reach the endpoint that writes. If you serve the site to your network with `--host`, anyone who can open the site can also edit your files — pass `features: ['!content.edit']` when you do that.
-
 ## Publish it to the web
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "seemore",
-  "version": "1.2.0",
+  "version": "1.3.1",
   "description": "Let AI write the Markdown. Let seemore show it better — zero config documentation framework.",
   "license": "MIT",
   "type": "module",

package/src/app/features/edit.tsx

@@ -135,6 +135,32 @@ export function InlineEditor({ entry }: { entry: RouteEntry }) {
     editingRef.current = editing;
   }, [editing]);
 
+  // The editor is a floating box over the page, so a press that lands anywhere else is a
+  // press away from it. That closes the editor only while nothing has been typed — the same
+  // rule the double-click handler uses, so a stray click can never discard an edit; with
+  // unsaved text the box stays put and Save or Cancel decides. The error message counts as
+  // part of the editor: a click on it is a click to dismiss it.
+  useEffect(() => {
+    if (editing === undefined) return;
+
+    const onPointerDown = (event: PointerEvent) => {
+      const target = event.target as HTMLElement | null;
+      if (target === null || saving) return;
+      if (target.closest('.seemore-editor, .seemore-editor-error') !== null) return;
+
+      const field = textarea.current;
+      if (field !== null) {
+        const typed = field.value.replace(/\r\n/g, '\n');
+        if (typed !== editing.original.replace(/\r\n/g, '\n')) return;
+      }
+      close();
+    };
+
+    // Captured, so a handler that stops the press on its way up cannot hold the editor open.
+    document.addEventListener('pointerdown', onPointerDown, true);
+    return () => document.removeEventListener('pointerdown', onPointerDown, true);
+  }, [editing, saving, close]);
+
   // The block is hidden rather than removed while it is edited, so the page does not jump.
   // If this component goes away mid-edit — a navigation, a hot reload — put it back.
   useEffect(() => () => editing?.element.classList.remove('seemore-editing'), [editing]);
@@ -228,8 +254,9 @@ export function InlineEditor({ entry }: { entry: RouteEntry }) {
             </span>
             {/*
               `onMouseDown` is prevented on both buttons so focus never leaves the textarea.
-              Taking focus would fire its blur handler, which saves — so a click on Cancel
-              would commit the very edit it is meant to discard.
+              Nothing is committed on blur, but the caret and the selection are: a click on
+              Save that a stale file refuses leaves the text exactly where it was, still
+              typed into and still listening for Escape.
             */}
             <button
               type="button"

package/src/app/styles/globals.css

@@ -303,6 +303,15 @@
     box-shadow: 0 0 0 4px var(--color-fd-muted);
   }
 
+  /* Written as a plain `.dark` rule rather than `dark:` on the `@apply` above: Tailwind
+     wraps a `dark:` variant reached through `@apply` in `:where(.dark, .dark *)`, which
+     carries no specificity of its own and loses the tie to the plain `box-shadow` line
+     and the `bg-fd-muted/40` utility above regardless of source order. */
+  .dark .seemore-editable [data-seemore-pos]:hover {
+    background-color: transparent;
+    box-shadow: none;
+  }
+
   .seemore-editable .seemore-editing {
     @apply invisible;
   }