You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Standardize primary button styles across the plugin #191
Audit every primary action in the plugin and apply one consistent visual treatment. Primary buttons must use the approved blue background, white text, and white icons where icons are present.
Requirements
Define shared primary, secondary, destructive, disabled, loading, hover, active, and focus states.
Replace browser-default or conflicting button styles in dialogs, panels, cards, profile actions, presets, dictionary, translation, navigator, and footer controls.
Ensure icon and text alignment, readable contrast, and a minimum usable touch target.
Preserve semantic button behavior and disabled/loading states.
Acceptance criteria
All primary actions share the same tokens and interaction states.
Blue/white contrast remains readable in light, dark, forced-colors, and high-zoom contexts.
No host-page CSS leaks into plugin buttons and plugin styles do not leak into host controls.
Focus-visible indicators remain clear and keyboard activation works.
Completed in PR #198 (commit 872a5cf, docs/tests 0234149): standardized primary (.arap-btn-primary #1d4ed8 blue with #ffffff text and icon strokes), secondary, danger, and ghost buttons across panels, cards, footer reset, Read Aloud, and modals.
Activity
prabothcharith commentedon Nov 16, 2026
Completed in PR #198 (commit 872a5cf, docs/tests 0234149): standardized primary (.arap-btn-primary #1d4ed8 blue with #ffffff text and icon strokes), secondary, danger, and ghost buttons across panels, cards, footer reset, Read Aloud, and modals.