Help: Bug Report

Prerequisites

• - Issue is reproducible on current package versions.
• - Framework, browser, and OS versions are captured.
• - Expected and actual behavior are written in plain, testable terms.

Step 1: Build a minimal reproducible case

Reduce to the smallest route/component setup that still fails.

Minimum report artifacts:
- Failing route/component
- Short reproduction steps
- Console error output

Step 2: Document expected versus actual behavior

State failure criteria explicitly so QA and maintainers can verify the fix.

### 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 and include repro artifacts.

Bug report URL:
https://github.com/jortega0033/diwa-design-system/issues/new?labels=bug&title=Bug%3A%20

Implementation Notes

• - Attach screenshots, videos, or stack traces for timing and visual defects.
• - If regression follows an upgrade, include the last known good version.
• - Link docs page(s) when observed behavior differs from documentation.

Troubleshooting

• - If maintainers cannot reproduce, share a small public sample repository.
• - If bug is browser-specific, include per-browser comparison output.
• - If intermittent, include timing notes and exact interaction sequence.

Next Actions