Prevent ZeuZ AI browser extension's DOM collection from changing browser state

[nasif-z]

Bug description

• Running the same TC in debug mode could fail even though it completed successfully in deploy mode.
• Page was automatically scrolling down in debug.

Root cause

• Debug mode calls send_dom_variables() for AI context collection.
• send_dom_variables() used getattr() while inspecting non-JSON shared variables.
• getattr() can execute Selenium WebElement properties (e.g. WebElement.location_when_scrolled_into_view) and change browser scroll state.

Solution

• Only call send_dom_variables() when Inspector.ai_plugin is enabled.
• Use inspect.getattr_static() while collecting non-JSON attribute type metadata so properties are not executed.

[riz-hossain]

🔎 ZeuZ PR Review

Open the full report in ZeuZ: Review findings and apply suggestions

Overview	Value
Agents	✅ 4 completed
Suggestions	💡 2

Agent breakdown

→ General Review

Status: ✅ Completed
Suggestions: 0 suggestions

No blocking issues found; the change correctly avoids triggering browser-mutating attribute access during debug DOM collection and gates it behind the AI plugin setting.

→ Security Review

Status: ✅ Completed
Suggestions: 0 suggestions

No security findings in this PR diff. The change narrows DOM collection to the AI plugin path and avoids triggering attribute access side effects, which is a safety improvement rather than a risk.

→ Performance Review

Status: ✅ Completed
Suggestions: 0 suggestions

No material performance regressions found in the PR diff; the new guard reduces debug-time DOM collection, and the fallback attribute inspection change is confined to the non-JSON path.

→ Testing Review

Status: ✅ Completed
Suggestions: 2 suggestions

The PR fixes a behavioral bug in debug mode, but there’s no regression coverage for either the new ai_plugin gate or the non-mutating attribute inspection path.

Open ZeuZ to inspect full findings, continue an agent conversation, or apply safe patch suggestions.