chrometools-mcp 3.1.7 → 3.2.4

package/CHANGELOG.md

@@ -2,6 +2,94 @@
 
 All notable changes to this project will be documented in this file.
 
+## [3.2.4] - 2026-01-27
+
+### Performance
+- **Compact APOM format** — Reduced analyzePage output size by ~70%
+  - Containers now use `"tag_id": [children]` format (instead of `{id, tag, selector, children}`)
+  - Selectors removed from output (registered internally for getElementDetails/click/type)
+  - Bottom-up pruning removes container branches without interactive elements
+  - Example: Google Search reduced from ~33K tokens (281 elements) to ~10K tokens (~80 elements)
+  - `includeAll: true` retains full format with selectors for debugging
+
+### Removed
+- **getElement tool** — Redundant tool replaced by analyzePage (55 → 54 tools)
+
+## [3.2.3] - 2026-01-27
+
+### Removed
+- **Reverted experimental features** — Removed `resolveComponentPaths` and `detectFrameworks` due to technical limitations
+  - Component path resolution was unreliable across different build configurations
+  - Framework detection removed from analyzePage tool
+  - Simplified codebase and improved performance
+
+## [3.2.2] - 2026-01-27
+
+### Fixed
+- **APOM ID resolution** — Fixed element ID lookup in `click` and `type` tools
+  - Added CSS selector generation to APOM tree elements
+  - Both interactive and container elements now include `selector` field
+  - APOM IDs (e.g., `textarea_25`, `button_45`) now work correctly with click/type tools
+- **Improved click reliability** — Enhanced click method with fallback strategies
+  - Primary method: standard Puppeteer click
+  - Fallback 1: scroll element into view and retry click
+  - Fallback 2: JavaScript click for hidden/overlapping elements
+  - Fixes issues with Google Search button and similar elements
+
+## [3.2.1] - 2026-01-27
+
+### Changed
+- **Unified element analysis tools** — Merged `analyzeElementById` into `getElementDetails`
+  - `getElementDetails` now has optional `analyzeChildren` parameter
+  - Set `analyzeChildren: true` to get children tree structure
+  - Simplified API reduces tool count and improves consistency
+  - Children analysis includes same `includeAll` and `refresh` options
+
+### Removed
+- **`getElementByApomId`** — Removed deprecated method (use `getElementDetails` instead)
+- **`analyzeElementById`** — Merged into `getElementDetails` with `analyzeChildren` parameter
+
+## [3.2.0] - 2026-01-27
+
+### Added
+- **New tool: `getElementDetails`** — Get comprehensive details about element by APOM ID
+  - Returns bounds, CSS selector, position, attributes, computed styles
+  - Use when `analyzePage` output is simplified and full element info is needed
+- **New tool: `analyzeElementById`** — Analyze children elements starting from specific APOM ID
+  - Useful for analyzing specific page sections without re-analyzing entire page
+  - Supports `includeAll` and `refresh` parameters
+
+### Changed
+- **Optimized `analyzePage` output** — Significantly reduced token usage
+  - Parent/container elements now show only `tag` and `id` (minimal info)
+  - Interactive elements no longer include `bounds` and `selector` in main output
+  - Use `getElementDetails` to get full information when needed
+  - ~50-70% reduction in output size for typical pages
+- **Improved cursor:pointer detection** — Only detects explicitly set cursor, not inherited
+  - Filters out inherited `cursor:pointer` from parent elements
+  - Reduces false positives in interactive element detection
+  - More accurate identification of clickable elements
+
+### Deprecated
+- **`getElementByApomId`** — Use `getElementDetails` instead (same functionality, clearer name)
+  - Filters out Angular dynamic classes (e.g., `_ng*`)
+  - Prefers stable class names for more reliable selectors across page loads
+
+## [3.1.8] - 2026-01-27
+
+### Changed
+- **Enhanced interactivity detection in analyzePage** — Improved detection of JavaScript-enabled interactive elements
+  - Added detection of elements with `cursor: pointer` CSS property
+  - Added detection of elements with JavaScript `addEventListener('click')`
+  - Added detection of elements with `onclick` property set via JavaScript
+  - DIV and SPAN elements with click handlers now correctly detected as interactive
+  - Added `interactivityReason` metadata field showing why element was marked interactive
+  - Reasons: `native-html`, `aria-role`, `onclick-attr`, `onclick-prop`, `cursor-pointer`, `event-listener`, `tabindex`, `contenteditable`
+
+### Performance
+- Optimized `markInteractiveElements` to skip event listener checks during bulk scan (performance)
+- Event listener detection only runs for individual element type determination
+
 ## [3.1.7] - 2026-01-27
 
 ### Fixed