Help: Bug Report
File bug reports with deterministic steps and expected/actual behavior so maintainers can reproduce and fix quickly.
Prerequisites
- - Confirmed reproducible issue on current package version.
- - Browser/framework/version information.
- - Expected and actual behavior captured clearly.
Step 1: Create a minimal reproduction
Reduce the issue to the smallest setup that still fails.
Minimum report artifacts:
- Failing route/component
- Short reproduction steps
- Console error outputStep 2: Document expected versus actual behavior
Make failure criteria explicit to avoid ambiguity.
### Expected
Focus ring remains visible on keyboard navigation.
### Actual
Focus ring disappears after component rerender.Step 3: Submit bug issue
Open a labeled bug issue with reproduction details and assets.
Bug report URL:
https://github.com/jortega0033/diwa-components/issues/new?labels=bug&title=Bug%3A%20Implementation Notes
- - Attach screenshots, videos, or stack traces when visual state or timing is involved.
- - If regression came from an upgrade, mention previous working version.
- - Link the exact docs page used if behavior differs from documented expectations.
Troubleshooting
- - If maintainers cannot reproduce, share a small public reproduction repository.
- - If bug appears browser-specific, include per-browser comparison details.
- - If issue is intermittent, add explicit timing and interaction sequencing.