Skip to content
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

Navigating Back On IPLD Breadcrumbs Fails #2479

Open
Faolain opened this issue May 7, 2023 · 3 comments
Open

Navigating Back On IPLD Breadcrumbs Fails #2479

Faolain opened this issue May 7, 2023 · 3 comments
Labels
area/webui Issues specific to interaction with ipfs-webui effort/days Estimated to take multiple days, but less than a week exp/beginner Can be confidently tackled by newcomers kind/bug A bug in existing code (including security flaws) need/analysis Needs further analysis before proceeding P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked

Comments

@Faolain
Copy link

Faolain commented May 7, 2023

  • OS: macOS
  • Version of IPFS Desktop [Version 0.27.2 (0.27.2)]
  • Electron Version: '19.1.9'
  • Chrome Version: '102.0.5005.167'

Describe the bug
When trying to navigate back to a parent level inside of the IPLD explorer breadcrumbs, the links cannot be found.

To Reproduce
Steps to reproduce the behavior:

  1. Click on XKCD Archives (or any other IPLD explorer trail) on the Explore Page
  2. Click on any path
  3. Click on another path (to go a level deeper)
  4. Click the breadcrumb in the top level to go back
  5. See error of a path not being found

GIF attached:
ipldexplorer

Expected behavior
You should be able to navigate back to the parent level which you clicked.

Developer Tools Logs:
Screenshot 2023-05-06 at 11 57 38 PM

@Faolain Faolain added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels May 7, 2023
@welcome
Copy link

welcome bot commented May 7, 2023

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@SgtPooki
Copy link
Member

SgtPooki commented May 8, 2023

@Faolain thanks for reporting this bug!

I was able to reproduce this bug on the latest version of IPFS Desktop as well.

It doesn't seem to be occurring at explore.ipld.io so maybe something in webui/desktop is broken.

I will investigate further.

@SgtPooki SgtPooki added need/analysis Needs further analysis before proceeding exp/beginner Can be confidently tackled by newcomers effort/days Estimated to take multiple days, but less than a week status/ready Ready to be worked area/webui Issues specific to interaction with ipfs-webui and removed need/triage Needs initial labeling and prioritization labels May 8, 2023
@SgtPooki SgtPooki moved this from Needs Grooming to Prioritized / Ready for Dev in IPFS-GUI (PL EngRes) May 8, 2023
@SgtPooki SgtPooki added the P1 High: Likely tackled by core team if no one steps up label May 8, 2023
@SgtPooki
Copy link
Member

SgtPooki commented May 8, 2023

Not reproducible in webui (ran locally) either. - i.e. definitely a bug with the bundling of webui inside of ipfs-desktop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/webui Issues specific to interaction with ipfs-webui effort/days Estimated to take multiple days, but less than a week exp/beginner Can be confidently tackled by newcomers kind/bug A bug in existing code (including security flaws) need/analysis Needs further analysis before proceeding P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked
Projects
No open projects
Status: Prioritized / Ready for Dev
Development

No branches or pull requests

2 participants