7 comments (7 comments)2 reactions (2 reactions)0 assignees (0 assignees)CSS16,580 stars (16,580 stars)500 forks (500 forks)batch import
help wantedv2
Description
I'm not so sure if this is useful. This is totally against good UX.
Contributor guide
- Tech stack
- css
- Domain
- frontend
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 2
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- under 1 hour
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- needs maintainer response
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- None
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 60
- Research direction
- Examine the discussion in the issue comments (7 comments) to understand the debate about the UX implications of adding role="group" to buttons. The maintainer's opinion is not yet clear; look for any consensus or decision in the repository's v2 design guidelines. The change itself is small: adding the role attribute to button groups in the CSS. Consider checking the Pico CSS v2 source for existing role usage.