platform-guideline 1 linked patterns checked
Google Maps JavaScript API: Info Windows
Documents map info windows as popup content attached to markers or latitude/longitude positions, with dialog exposure for screen readers.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Map view | Choose Map view when spatial relationship, proximity, coverage, route, region, or real-world placement changes the user's decision. | Markers, shapes, routes, clusters, and overlays represent explicit coordinates, features, or geographic areas, not decorative positions. | Google documents info windows as popup content attached to markers or coordinates and exposed as dialogs. |
Comparisons supported by this source
- Map view vs list view vs calendar view vs table
Google documents info windows attached to markers or map coordinates and exposed as dialogs.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Google. Last checked: .