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

TH-1334 | Remove back button #756

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

TH-1334 | Remove back button #756

wants to merge 1 commit into from

Conversation

melniiv
Copy link
Contributor

@melniiv melniiv commented Dec 19, 2024

Description

When there is no return url, the back button should be hidden

Issues

Closes

TH-1334

Related

Testing

Automated tests

Manual testing

Screenshots

Additional notes

@terovirtanen
Copy link
Contributor

Events-Helsinki branch is deployed to platta: https://tapahtumat-pr756.dev.hel.ninja 🚀🚀🚀

@terovirtanen
Copy link
Contributor

Sports-Helsinki branch is deployed to platta: https://liikunta-pr756.dev.hel.ninja 🚀🚀🚀

@terovirtanen
Copy link
Contributor

TestCafe result is success for https://liikunta-pr756.dev.hel.ninja 😆🎉🎉🎉

@terovirtanen
Copy link
Contributor

Hobbies-Helsinki branch is deployed to platta: https://harrastukset-pr756.dev.hel.ninja 🚀🚀🚀

@terovirtanen
Copy link
Contributor

TestCafe result is success for https://tapahtumat-pr756.dev.hel.ninja 😆🎉🎉🎉

@terovirtanen
Copy link
Contributor

TestCafe result is success for https://harrastukset-pr756.dev.hel.ninja 😆🎉🎉🎉

@nikomakela nikomakela self-requested a review December 19, 2024 13:07
Copy link
Contributor

@nikomakela nikomakela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACtually, I think we need to reconsider this a bit, because when I tested the current production environment, I found couple of issues.

When using a laptop browser:

  1. Using hero back button, I'm first taken to the right card, the card that I clicked earlier, but then the page scroll is resetted and I'mtaken to top of the page.
  2. If I use browser back button, I'm always taken to the top of the page.

When using laptop in mobile view emulation:

  1. The screen is white for really long and flashes multiple times. Then I'm taken to the top of the page. No matter what go back -feature I'm using.

When using a mobile phone:

  1. The hero back button works as expected and I'm taken to the card that I clicked.
  2. The browser back button always takes me to top of the page.

So, if we try to get rid of the back button, I think we first need to fix these broken features and test this properly.

@karisal-anders
Copy link
Contributor

karisal-anders commented Jan 3, 2025

ACtually, I think we need to reconsider this a bit, because when I tested the current production environment, I found couple of issues.

When using a laptop browser:

  1. Using hero back button, I'm first taken to the right card, the card that I clicked earlier, but then the page scroll is resetted and I'mtaken to top of the page.
  2. If I use browser back button, I'm always taken to the top of the page.

When using laptop in mobile view emulation:

  1. The screen is white for really long and flashes multiple times. Then I'm taken to the top of the page. No matter what go back -feature I'm using.

When using a mobile phone:

  1. The hero back button works as expected and I'm taken to the card that I clicked.
  2. The browser back button always takes me to top of the page.

So, if we try to get rid of the back button, I think we first need to fix these broken features and test this properly.

Looks like there's quite a bit to do before this can be merged. I remove myself as a reviewer to make my review request list more of an actionable TODO-list and this doesn't qualify taking into account also that TH-1334 isn't in the sprint. If this is taken under work later, then review can be requested again.

@karisal-anders karisal-anders removed their request for review January 3, 2025 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants