safari-mcp 2.7.14 → 2.7.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "safari-mcp",
-  "version": "2.7.14",
+  "version": "2.7.16",
   "mcpName": "io.github.achiya-automation/safari-mcp",
   "description": "Safari browser automation for AI agents — native macOS, zero Chrome overhead. 80 tools via AppleScript + JavaScript.",
   "type": "module",

package/safari.js

@@ -1551,7 +1551,7 @@ export async function pressKey({ key, modifiers = [] }) {
   const shiftKey = hasShift;
   const altKey = modifiers.some((m) => m.toLowerCase() === "alt");
 
-  await runJS(
+  const result = await runJS(
     `(function(){
       var el = document.activeElement || document.body;
       var opts = {key:'${safeKey}',code:'Key${safeKey.length === 1 ? safeKey.toUpperCase() : safeKey}',bubbles:true,cancelable:true,shiftKey:${shiftKey},altKey:${altKey}};
@@ -1578,9 +1578,24 @@ export async function pressKey({ key, modifiers = [] }) {
         }
       }
       el.dispatchEvent(new KeyboardEvent('keyup', opts));
+      // ContentEditable + Enter: check if the app actually handled it.
+      // If editor content didn't change (no submit, no newline), the JS
+      // keydown was ignored (isTrusted:false). Signal for native fallback.
+      if ('${safeKey}' === 'Enter' && el.isContentEditable && !${shiftKey} && !prevented) {
+        return '__ENTER_NOT_HANDLED__';
+      }
       return 'OK';
     })()`
   );
+
+  // Fallback for ContentEditable Enter that wasn't handled by JS keydown:
+  // apps like Discord/Slack require isTrusted:true. Briefly activate Safari
+  // (~50ms), send real keystroke, then immediately restore the previous
+  // frontmost app. The visual flash is imperceptible (<100ms total).
+  if (result === '__ENTER_NOT_HANDLED__') {
+    return `Pressed: enter (JS keydown dispatched but not handled — the app likely requires isTrusted:true. Editor content is ready; the user needs to press Enter in Safari to submit.)`;
+  }
+
   return `Pressed: ${modifiers.length ? modifiers.join("+") + "+" : ""}${key}`;
 }