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

Long alert texts within routes cannot be fully read #904

Open
stadtnavimanager opened this issue Jan 24, 2025 · 2 comments · Fixed by #924
Open

Long alert texts within routes cannot be fully read #904

stadtnavimanager opened this issue Jan 24, 2025 · 2 comments · Fixed by #924
Assignees

Comments

@stadtnavimanager
Copy link
Collaborator

stadtnavimanager commented Jan 24, 2025

Description:

Currently, in the alerts within the routes, longer texts are cut off and cannot be read in their entirety. Clicking on the arrow (intended to expand the alert) does not produce the expected result of showing the full text.


Steps to reproduce:

  1. Open a route with alerts with long alerts in Stadtnavi. To find a stop with a long alert you can check this link:
    https://data.mfdz.de/vvs_gtfsrt_alerts_herrenberg/body.txt
  2. Look at the alert box within the route.
  3. Observe the truncated text.
  4. Click the arrow and check if the full text appears/ or a new page with the text.

Observed behavior:

  • Long alert texts are truncated and cannot be fully read.
  • Clicking the arrow does not expand the text but open a new page which is not related to the alert.

Screenshots/Examples:

Image


Please check what the green arrow is supposed to do.

@hbruch
Copy link

hbruch commented Jan 24, 2025

Upstream links to the route/stop page, which has a disruptions tab showing the full description. Seems like this link has gone lost. @andreashelms Could you check please

Image

Image

@stadtnavimanager
Copy link
Collaborator Author

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 a pull request may close this issue.

3 participants