Context menu can be micro optimalized.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Context menu can be micro optimalized. Copy path is very frequently used fucntion it is almos automatic. for that reason it should be alsway in the same spot so people can memorzy it via mustle memory. Currently sometime is first sometimes second, after open in new tab. I understand reason who new tab is first, but u new tab is alway consientius action. so u can make u UI better by ofestting context menu up. so that copy path is alway in swee spot even if it second
| Field | Value |
|---|---|
| App version | 1.1.16 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 3 (Week 1) |
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
Reproduce the context menu on Windows at the /chat path using app version 1.1.16, and inspect how its item order and placement are determined. Done means Copy path appears in the same preferred position whether Open in new tab is present or absent.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100