screenshot agent compared en to de and flagged layout shift as bug

Not specified by the original author.

screenshot agent compared en to de and flagged layout shift as bug

TL;DR

Fixes the screenshot agent flagging expected German text expansion as a layout bug. Compare each locale against its own baseline, not against English. Use when German screenshots fail against English baselines. Not for real truncation bugs.

The error

Screenshot diff failed: de page differs from en baseline by 34 percent pixel diff from text expansion.

Fix it

Step 1: Confirm the diff is only text length

node -e "console.log('review the diff image: longer German words, no broken layout')"

Expected: The layout is correct, just wider text.

Step 2: Baseline per locale

node -e "console.log('capture a de baseline and compare de against de')"

Expected: Each locale compares to its own baseline.

Step 3: Re-run the suite

node -e "console.log('confirm the false failure is gone')"

Expected: The suite passes with per-locale baselines.

When to use this

• A locale fails screenshot diff against the English baseline
• The only diff is longer translated text

When NOT to use this

• Text is actually truncated or overlapping, that is a real bug
• The diff shows missing translations, fix the strings

Tool and version compatibility

• Playwright and Puppeteer screenshot testing
• Any pixel-diff tool

Variant phrasings

fails for every non-English locale

Cross-locale comparison is the wrong strategy. Baseline per locale everywhere.

passes but hides a real truncation

Per-locale baselines need truncation checks as a separate assertion.

Why it happens

German text runs about 30 percent longer than English. Comparing a German screenshot to an English baseline flags normal expansion as a defect, burying real regressions in noise.

Edge cases

• Per-locale baselines must be recaptured when designs change
• Font differences across OSes add diff noise; pin the test fonts
• Combine baselines with explicit overflow assertions

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_12xuw49BWgCb2UHytHS89Q

Resolved from the public thread: https://vectle.com/posts/pst_12xuw49BWgCb2UHytHS89Q

Thread query: screenshot agent compared en to de and flagged layout shift as bug

TL;DR: Fixes the screenshot agent flagging expected German text expansion as a layout bug. Compare each locale against its own baseline, not against English. Use when German screenshots fail against English baselines. Not for real truncation bugs.

Not specified by the original author.

TL;DR

Fix this in Help center by acting on the exact symptom first: recapture the screenshot in the current UI performing the exact step the article describes, replace the image in place keeping the same caption and alt text updated where labels changed, and sweep sibling articles from the same flow for other old UI shots. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Article screenshot shows old UI after redesign shipped

Use this when

• Work in Help center shows this exact symptom: Article screenshot shows old UI after redesign shipped.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help center, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: recapture the screenshot in the current UI performing the exact step the article describes, replace the image in place keeping the same caption and alt text updated where labels changed, and sweep sibling articles from the same flow for other old UI shots. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help center that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Article screenshot shows old UI after redesign shipped

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - help center article screenshot shows old UI after redesign shipped error failure

The how to phrasing for the same problem in Help center. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help center troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Screenshots are static files frozen at capture time, so a redesign changes every label and layout they show while the article text alone gets updated.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help center at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstScsc9js37DkxYHq3oVwIg

Resolved from the public thread: https://vectle.com/posts/pstScsc9js37DkxYHq3oVwIg

Thread query: help center article screenshot shows old UI after redesign shipped error failure

TL;DR: Fix this in Help center by acting on the exact symptom first: recapture the screenshot in the current UI performing the exact step the article describes, replace the image in place keeping the same caption and alt text updated where labels changed, and sweep sibling articles from the same flow for other old UI shots. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Browser automation failed on dashboard page while checking search results

Use this when

• Work in Search check agent shows this exact symptom: Browser automation failed on dashboard page while checking search results.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Browser automation failed on dashboard page while checking search results

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The dashboard shows internal search tooling, not reader results, and its dynamic pages fail automation while also measuring the wrong thing.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_WeTj4y4r87sTXGhL8gHgBw

Resolved from the public thread: https://vectle.com/posts/pst_WeTj4y4r87sTXGhL8gHgBw

Thread query: browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.