All new drawer
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.1k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 57
Description
Package
v4.x
Description
The drawer used by Nuxt UI is vaul-vue, a project that is not maintained for a long time and has major issues on touch devices. Also Nuxt UI has two separate drawers/slideovers: USlideover and UDrawer.
I would suggest to add a dedicated Drawer to Nuxt UI, or better to upstream Reka UI (so it will be available to a broader audience), that is maintained by Nuxt UI / Reka UI team.
When doing so, either USlideover or UDrawer could be removed in favor of one unified component.
Additional context
vaul-vue, and therfor Nuxt UI Drawer, has major issues on touch devices, see https://github.com/unovue/vaul-vue/issues/36 which is open since march 2024:
The drawer is not scrollable on touch devices because the scrolling collides with closing. You can test on mobile devices here: https://nuxt-ui-drawer.vercel.app/
Reproduction: https://github.com/MickL/nuxt-ui-drawer
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
Start by reviewing the existing UDrawer and USlideover components, the vaul-vue touch-device reproduction, and linked pull request #6691. The intended outcome is a maintained unified drawer or a clear decision to replace one existing component, with touch scrolling no longer conflicting with closing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100