seemore 1.8.3 → 1.8.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "seemore",
-  "version": "1.8.3",
+  "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

@@ -11,17 +11,23 @@ import { FileText } from 'lucide-react';
  *
  * `pdfjs-dist` is roughly a megabyte, which is a poor trade for a docs site. The accepted
  * cost is that some environments degrade `<embed>` to a blank box, since they don't support
- * inline PDF plugins — most mobile browsers, but also Electron-based webviews (VS Code's
- * preview included), which don't ship Chrome's PDF viewer extension despite reporting a
+ * 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, so `navigator.pdfViewerEnabled` — Chromium/Firefox's direct feature check — is used
- * to catch the second by toggling the same fallback via a class instead of a media query.
+ * 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(() => {
-    if ('pdfViewerEnabled' in navigator && !navigator.pdfViewerEnabled) {
+    const noPdfViewerApi = 'pdfViewerEnabled' in navigator && !navigator.pdfViewerEnabled;
+    const embeddedWebview = window.parent !== window;
+    if (noPdfViewerApi || embeddedWebview) {
       setUnsupported(true);
     }
   }, []);