Intermittent findings and dynamic content: identity strength for repeated controls
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 39/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- playwright, testing-qa, typescript
- Domain
- accessibility, devtools, testing
Research direction
The issue describes row-scoped control keys, a two-scan baseline stability pass, and operator guidance, but names no files or tests. Start by locating the baseline scanner, element-key generation, and documentation for data-dependent screens. Done means repeated controls retain separate identities, intermittent findings are marked, and operators have guidance; verify with the relevant scanner tests.
Written by the indexing model from the issue text.
Description
What
On a live application, collapsed identities for repeated controls (icon buttons per table row, kebab toggles per row) carry counts that track how many rows the page happens to show. The floor records those counts; runs against an unchanged codebase then see headroom or growth depending on live data.
Separately, a tooltip opened by the scanner's own keyboard walk was still in the DOM during its fade-out when axe ran and produced a new region finding on an unchanged page, one run in five. A bounded settle for transient popovers now runs between the walk and the providers.
Direction
- Stronger element keys for row-scoped controls (row identity plus control role) so identities do not collapse across rows.
- A stability pass at baseline that scans twice and records only findings present both times, marking the rest as intermittent.
- Guidance for operators on data-dependent screens.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 48m
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from usabl-dev/usabl
-
area: engine bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdictOpenarea: assistants bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area: engine bug security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not sharedOpenarea: overlay bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
area: engine enhancement performance
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
数据界面的横向滚动条缺失Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zilliztech/attu#1037 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#181212 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apify/apify-mcp-server#1684 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Automattic/data-liberation-agent#953 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
siteboon/claudecodeui#1642 ·
Maintainers usually reply within 5 days