You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When clicking on the "View on Google Maps" link, it opens in the same tab instead of opening in a new tab. This affects user experience as it navigates away from the current website.
Expected behavior
When clicking on the "View on Google Maps" link, it should open in a new tab instead of the same tab. This ensures that users remain on the current website while also accessing the Google Maps location in a separate tab.
Screenshots
CARE.-.Location.2025-02-01.22-49-06.mp4
Desktop (please complete the following information):
OS: [windows]
Browser [chrome]
Version [132.0.6834.111]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
We support Markdown for the Facility description. It is expected behaviour I think if it is not , we need to tweak the description. I think we should structure the description with specific inputs like a heading field, a Google Maps link field, and a general description field, then pass them as a string. When retrieving, we can parse and display them accordingly. Just sharing thoughts . Never-mind !!! 😊
Describe the bug
When clicking on the "View on Google Maps" link, it opens in the same tab instead of opening in a new tab. This affects user experience as it navigates away from the current website.
To Reproduce
Steps to reproduce the behavior:
Click here to reproduce
Scroll down to 'Location Map'
See error
Expected behavior
When clicking on the "View on Google Maps" link, it should open in a new tab instead of the same tab. This ensures that users remain on the current website while also accessing the Google Maps location in a separate tab.
Screenshots
CARE.-.Location.2025-02-01.22-49-06.mp4
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: