Negative `icon-padding` usecases
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
Icons might have shadows or have other reasons where 'partial overlap' is okay, whilst 'full on stacking' is not okay. A negative icon-padding would allow some control over the 'amount of stacking' that happens.
Bad stacking:
Good stacking:
## Design Alternatives
Best I can reason *technically* negative `icon-padding` would just work out of the box if the validation wouldn't block it. If that's the case then I would like to ask for the constraint to be removed.
I might be able to get the same behavior using a carefully calibrated point clustering implementation (that's what I am going to do for now), but just wanted to give the feedback that there are many valid usecases for a negative `icon-padding`
Contributor 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.
Research direction
No source files, tests, or entry points are named in the issue. Start by locating the validation for icon-padding and the existing tests for that property; confirm whether accepting negative values enables partial overlap without breaking current stacking behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100