explore use cases for single input modality use cases of interest invoker
Open
Nobody has claimed this yet.
command-invokers
interest-invokers
needs-triage
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
https://github.com/openui/open-ui/issues/872 kicked off a discussion about how interest invokers are multi-modal (focus/hover) and sometimes that's not applicable.
We should try to discover use cases where that isn't applicable. Two mentioned:
- Menus where you'd want sub-menus to open on hover, but not focus
- Carousels where you'd want the list of pages to rotate with focus, but not with hover (https://github.com/openui/open-ui/issues/1030).
We should prototype these out and see what primitives are missing and how we can address these.
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 reading the discussion in issues 872 and 1030, then examine the menu and carousel use cases described here. Prototype the single-modality interactions and document which primitives are missing and how they could address the cases; done means the use cases and resulting requirements are clear.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100