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

explorer: Define the use of the Back button on detail pages #1782

Closed
deuch13 opened this issue May 23, 2024 · 2 comments · Fixed by #1849
Closed

explorer: Define the use of the Back button on detail pages #1782

deuch13 opened this issue May 23, 2024 · 2 comments · Fixed by #1849
Assignees
Labels
module:explorer Issues related to explorer module need:brainstorm Call for participation: group brainstorming is requested to fix this issue need:specs Call for participation: specs are requested to fix this issue

Comments

@deuch13
Copy link
Contributor

deuch13 commented May 23, 2024

Summary

Currently the Back button action sends the user back to the Blocks or Transactions page depending if it's a Block Details page or a Transaction Details page.

In some cases this is not correct as Back refers to where the user navigated from. But if this is the case the button becomes redundant as it emulates the browser back button.

As an example the user could have navigated to a details page from the home page or he could have used the arrows to navigate through the block height in the block details page.

Either we remove the button completely or we give it a new and clear purpose.

@deuch13 deuch13 added need:specs Call for participation: specs are requested to fix this issue need:brainstorm Call for participation: group brainstorming is requested to fix this issue module:explorer Issues related to explorer module labels May 23, 2024
@deuch13 deuch13 assigned deuch13 and laremas and unassigned deuch13 May 23, 2024
@laremas
Copy link
Member

laremas commented May 23, 2024

I would go back to either transaction or block page renaming the button "latest transaction" and "latest blocks", if possible. Text could be to long for mobile views.

I am open to other solutions, let's discuss this.

@laremas
Copy link
Member

laremas commented Jun 12, 2024

After a new discussion we understood that having this button, while the user can do the same action both with back button on browser or just clicking on the blocks/transaction page link in the navbar, is redundant.

So they are now Removed from the table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module:explorer Issues related to explorer module need:brainstorm Call for participation: group brainstorming is requested to fix this issue need:specs Call for participation: specs are requested to fix this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants