chrometools-mcp 3.5.4-beta.0 → 3.5.4

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to this project will be documented in this file.
 
+## [3.5.4] - 2026-02-16
+
+### Fixed
+- **Angular stale DOM in analyzePage** — Added `whenStable()` wait (Protractor-style) before DOM traversal. Prevents reading intermediate DOM state during Angular change detection after user interactions. Zero overhead when Angular is already stable; 3s timeout safety net
+- **Stale element registry** — `window.__ELEMENT_REGISTRY__` is now cleared before each `analyzePage` call. Old APOM IDs from previous analyses no longer point to non-existent elements
+- **False "ELEMENT DETACHED" warning on click** — Click tool no longer reports "handler did NOT fire" when Angular re-renders DOM after a successful click. The scary warning with executeScript workaround suggestions is replaced with a neutral "Click was successful" note
+
 ## [3.5.3] - 2026-02-16
 
 ### Fixed

package/index.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 import {Server} from "@modelcontextprotocol/sdk/server/index.js";
 import {StdioServerTransport} from "@modelcontextprotocol/sdk/server/stdio.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chrometools-mcp",
-  "version": "3.5.4-beta.0",
+  "version": "3.5.4",
   "description": "MCP (Model Context Protocol) server for Chrome automation using Puppeteer. Persistent browser sessions, UI framework detection (MUI, Ant Design, etc.), Page Object support, visual testing, Figma comparison. Works seamlessly in WSL, Linux, macOS, and Windows.",
   "type": "module",
   "main": "index.js",

package/utils/actions/click-action.js

@@ -163,17 +163,11 @@ export async function executeClickAction(page, element, options = {}) {
   }
 
   // Element detached during click (Angular *ngFor + Zone.js)
+  // This is NORMAL for Angular apps: click fires → handler runs → Zone.js triggers
+  // change detection → *ngFor recreates elements → original handle is detached.
+  // The click DID work — detachment is a consequence of successful state change.
   if (elementDetached) {
-    hintsText += '\n⚠️ ELEMENT DETACHED: Element was removed from DOM during click — handler did NOT fire.';
-    hintsText += '\n   Cause: Angular Zone.js triggers change detection mid-click, *ngFor recreates elements.';
-    hintsText += '\n   App fix: add trackBy to *ngFor, or cache array reference instead of returning new one.';
-    hintsText += '\n   Workaround options:';
-    hintsText += '\n   1. Click via executeScript (bypasses Puppeteer element handle):';
-    hintsText += '\n      executeScript({ script: "document.querySelector(\'YOUR_SELECTOR\').click()" })';
-    hintsText += '\n   2. Call Angular component method directly:';
-    hintsText += '\n      executeScript({ script: "ng.getComponent(document.querySelector(\'component-tag\')).methodName()" })';
-    hintsText += '\n   3. Re-analyze page and use new element ID:';
-    hintsText += '\n      analyzePage({ refresh: true }) → click({ id: "NEW_ID" })';
+    hintsText += '\nNote: Element was re-rendered after click (Angular change detection). Click was successful — use analyzePage to see updated state.';
   }
 
   if (hints.suggestedNext.length > 0) {