Assigned
Status Update
No update yet.
Comments
br...@google.com
br...@google.com
We are building a polygon array with a click event: https://developers.google.com/maps/documentation/javascript/examples/polygon-arrays
However, looking for keyboard accessibility, we are not able to trigger the information dialog using a keyboard similar to how to map markers can be triggered using arrow keys:https://developers.google.com/maps/documentation/javascript/examples/marker-accessibility
Is there something we can do about it?
Thank you!
Map version: 3.49.12
However, looking for keyboard accessibility, we are not able to trigger the information dialog using a keyboard similar to how to map markers can be triggered using arrow keys:
Is there something we can do about it?
Thank you!
Map version: 3.49.12
an...@yahoo.com
Thanks for your suggestion!
We'll be reviewing this for further consideration. Please star this issue to get updates and leave comments for additional information. Please note that starring the issue also provides our product team with valuable feedback on the importance of the issue to our customers.
br...@google.com
✨
an...@yahoo.com
Heres a JSFiddle SCS: https://jsfiddle.net/wnab2ekj/3/
In this code snippet, just making aware that youll need to provide a valid google API map key where I have "INSERT_API_KEY_HERE". Youll also want to take notice that ive explicitly set the version to 3.59. When you run, you should notice that the route is drawn on the map, but the directionsPanel fails to render. This will be due to the issue described above in the ticket from what ive been able to debug by walking the obfuscated direction.js code.
To see the code working, switch the version from 3.59 to 3.58 (or 3.58.11a), and youll notice when run, that the panel and its alternative route suggestions render as expected. I believe it is also worth noting that when provideRouteAlternatives is set to false/omitted, the issue does not occur in 3.59. When this parameter is enabled, then the issue is seen.
Thanks
In this code snippet, just making aware that youll need to provide a valid google API map key where I have "INSERT_API_KEY_HERE". Youll also want to take notice that ive explicitly set the version to 3.59. When you run, you should notice that the route is drawn on the map, but the directionsPanel fails to render. This will be due to the issue described above in the ticket from what ive been able to debug by walking the obfuscated direction.js code.
To see the code working, switch the version from 3.59 to 3.58 (or 3.58.11a), and youll notice when run, that the panel and its alternative route suggestions render as expected. I believe it is also worth noting that when provideRouteAlternatives is set to false/omitted, the issue does not occur in 3.59. When this parameter is enabled, then the issue is seen.
Thanks
br...@google.com
Thank you for providing the details.
The issue has been logged internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications when the fix is released.
Description
1. Select a Origin
2. Select a Destination
3. Hit "OK"
When using the TripPlanner, this sends a request for two locations to Googles DirectionService. When attempting to render the response in the DirectionsRenderer, a NPE/error is thrown in googles direction.js file.
The code is attempting to read the TransitLine.color and TransitLine.text_color, but the values are undefined. According to the documentation, these fields are optional (
The GTFS specification defines a routes.txt file where the route_color and route_text_color are optional fields that map to color and text_color respectively. If they agency doesn't include them, they shouldn't appear in the API response. Some agencies dont provide these fields. The issue is that Google directions.js is trying to render the directions from the response, but because they fields are empty/null, crashing the site.
This issue does not exist in the previous quarterly release version of 3.58.11a. The issue appears to of been introduced in 3.59