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

Case when a stop point doesn't get deleted properly #1487

Open
solita-sabinaf opened this issue Aug 20, 2024 · 0 comments
Open

Case when a stop point doesn't get deleted properly #1487

solita-sabinaf opened this issue Aug 20, 2024 · 0 comments

Comments

@solita-sabinaf
Copy link
Collaborator

solita-sabinaf commented Aug 20, 2024

A bit rare to encounter but still, there is one scenario when stop point deletion doesn't go well. Steps to reproduce:

  1. Open journey patterns' stop points form
Screenshot 2024-08-20 at 13 01 52
  1. Add a new stop point (just so that it's possible to delete one) and fill it with some value, the position in the sequence doesn't matter, just as long as there is one more stop point coming earlier with (important!) all the fields being empty and "pristine"
Screenshot 2024-08-20 at 13 02 32
  1. Delete the empty pristine stop point (any of the those) which is preceding the stop point that had some quay value entered
Screenshot 2024-08-20 at 13 05 54
  1. After "yes" was pressed in the previous step, the dialogue stays visible. In the background can be seen that now there are 2 stop points, so deletion took place
Screenshot 2024-08-20 at 13 05 59
  1. After pressing dialogue's "close" button, the stop point that initially had a quayRef value entered, no longer has the value visible (the stuff visible is the placeholder's default suggestion text). Clicking anywhere outside the quayRef field would result in the quayRef value being cleared away entirely
Screenshot 2024-08-20 at 13 06 07 Screenshot 2024-08-20 at 13 06 11
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

No branches or pull requests

1 participant