seemore 1.8.2 → 1.8.4

package/package.json

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

package/src/app/mdx/Pdf.tsx

@@ -1,4 +1,4 @@
-import type { ComponentProps } from 'react';
+import { useEffect, useState, type ComponentProps } from 'react';
 import { FileText } from 'lucide-react';
 
 /**
@@ -10,14 +10,30 @@ import { FileText } from 'lucide-react';
  * on a `<span>` gets the same layout with none of that.
  *
  * `pdfjs-dist` is roughly a megabyte, which is a poor trade for a docs site. The accepted
- * cost is that most mobile browsers degrade `<embed>` to a blank box, since they don't
- * support inline PDF plugins. There's no reliable JS-free way to detect that, so the CSS
- * in globals.css hides the embed and expands this link into a full card under
- * `(pointer: coarse)` — touch devices are the same population that lacks embed support.
+ * cost is that some environments degrade `<embed>` to a blank box, since they don't support
+ * inline PDF plugins — most mobile browsers, but also the VS Code extension's webview, whose
+ * bundled Electron/Chromium doesn't ship Chrome's PDF viewer extension despite reporting a
+ * fine pointer. The CSS `(pointer: coarse)` fallback in globals.css only catches the first
+ * group. `navigator.pdfViewerEnabled` (Chromium/Firefox's direct feature check) would be the
+ * clean way to catch the second, but the Electron build VS Code ships predates that API, so
+ * `'pdfViewerEnabled' in navigator` is false there too and never flips it. Instead this reuses
+ * the same signal `ExternalLinkBridge.ts` uses for the identical webview: the site only ever
+ * runs inside a nested, cross-origin iframe when the VS Code extension put it there (see
+ * `panelHtml.ts`), so `window.parent !== window` is a reliable stand-in.
  */
 export function Pdf({ src, title, ...props }: ComponentProps<'embed'> & { src: string }) {
+  const [unsupported, setUnsupported] = useState(false);
+
+  useEffect(() => {
+    const noPdfViewerApi = 'pdfViewerEnabled' in navigator && !navigator.pdfViewerEnabled;
+    const embeddedWebview = window.parent !== window;
+    if (noPdfViewerApi || embeddedWebview) {
+      setUnsupported(true);
+    }
+  }, []);
+
   return (
-    <span className="seemore-pdf">
+    <span className={unsupported ? 'seemore-pdf seemore-pdf-unsupported' : 'seemore-pdf'}>
       <embed src={src} type="application/pdf" title={title} {...props} />
       <a className="seemore-pdf-fallback" href={src} download>
         <FileText className="seemore-pdf-fallback-icon" aria-hidden="true" />

package/src/app/styles/globals.css

@@ -438,7 +438,10 @@
   }
 
   /* Most touch browsers can't render `<embed type="application/pdf">` at all, so the box
-     above sits blank. Hide it there and promote the download link into the primary UI. */
+     above sits blank. Hide it there and promote the download link into the primary UI.
+     `.seemore-pdf-unsupported` is the same fallback, applied via JS (see Pdf.tsx) for
+     environments — Electron webviews included — that fail the same way despite a fine
+     pointer, so both selectors share these rules. */
   @media (pointer: coarse) {
     .seemore-pdf embed {
       @apply hidden;
@@ -452,6 +455,18 @@
       @apply size-6;
     }
   }
+
+  .seemore-pdf-unsupported embed {
+    @apply hidden;
+  }
+
+  .seemore-pdf-unsupported .seemore-pdf-fallback {
+    @apply mt-0 flex-col items-start gap-1 rounded-lg border border-fd-border bg-fd-card px-4 py-4 hover:border-fd-primary/60;
+  }
+
+  .seemore-pdf-unsupported .seemore-pdf-fallback-icon {
+    @apply size-6;
+  }
 }
 
 /* Unlayered, deliberately: fumadocs' `max-h-[460px]` utility lives in Tailwind's utilities