Skip to content

Improve context menu on breadcrumbs #1617

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rafaelramalho19 opened this issue Sep 9, 2020 · 0 comments · May be fixed by #2358
Open

Improve context menu on breadcrumbs #1617

rafaelramalho19 opened this issue Sep 9, 2020 · 0 comments · May be fixed by #2358
Assignees
Labels
effort/hours Estimated to take one or several hours exp/intermediate Prior experience is likely helpful good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked topic/design-front-end Front-end implementation of UX/UI work

Comments

@rafaelramalho19
Copy link
Contributor

rafaelramalho19 commented Sep 9, 2020

See conversation on #1599 (comment):

  • We want to disable native right click action and only display webui ones when interacting with breadcrumbs or file list
  • There should be only one context menu at a time
    • if a new one is opened an existing one should be automatically closed
@rafaelramalho19 rafaelramalho19 added need/triage Needs initial labeling and prioritization kind/enhancement A net-new feature or improvement to an existing feature labels Sep 9, 2020
@rafaelramalho19 rafaelramalho19 self-assigned this Sep 9, 2020
@jessicaschilling jessicaschilling added this to the v2.12 milestone Sep 9, 2020
@jessicaschilling jessicaschilling added exp/intermediate Prior experience is likely helpful effort/hours Estimated to take one or several hours good first issue Good issue for new contributors help wanted Seeking public contribution on this issue P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/design-front-end Front-end implementation of UX/UI work and removed need/triage Needs initial labeling and prioritization labels Sep 9, 2020
@lidel lidel modified the milestones: v2.13, v2.14 Apr 13, 2021
@SgtPooki SgtPooki moved this to To do in IPFS-GUI (PL EngRes) Jul 19, 2022
@SgtPooki SgtPooki added P3 Low: Not priority right now and removed P1 High: Likely tackled by core team if no one steps up labels Dec 2, 2022
@SgtPooki SgtPooki removed this from the v2.14 milestone Dec 2, 2022
@SgtPooki SgtPooki moved this from Needs Grooming to Planned / Backlog in IPFS-GUI (PL EngRes) Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours exp/intermediate Prior experience is likely helpful good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked topic/design-front-end Front-end implementation of UX/UI work
Projects
No open projects
Status: Planned / Backlog
Development

Successfully merging a pull request may close this issue.

4 participants