[google_maps_flutter_web] Fix consumeTapEvents for Circles, Polygons & Polylines (#173921)

[surajrathod007]

This PR fixes a bug in google_maps_flutter_web where consumeTapEvents = false was still consuming tap events for Circle and Polygon overlays.

Previously, even when consumeTapEvents was set to false, taps on circles or polygons would prevent events from reaching the map beneath them. With this fix, the behavior is now consistent with mobile platforms — taps pass through when consumeTapEvents = false.

Fixes flutter/flutter#173921

Version and Changelog

• Bumped version: 0.5.12+2 → 0.5.13
• Added CHANGELOG entry for this fix.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under¹.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩² ↩³

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request addresses a bug where consumeTapEvents = false was not being correctly handled for Circles and Polygons on the web, causing them to consume tap events instead of letting them pass through to the map. The fix involves mapping the consumeTapEvents property to the clickable option in the Google Maps JavaScript API for both circles and polygons. My review includes a suggestion to improve the changelog entry for stylistic consistency and points out that the fix is incomplete as it does not cover Polylines, which are also affected by the same issue.

[mdebbar]

Thanks for fixing this issue!

The fix looks good to me. Would you mind doing the same for Polyline too? That would ensure the fix is applied consistently across all shapes.

[surajrathod007]

Thanks for fixing this issue!

The fix looks good to me. Would you mind doing the same for Polyline too? That would ensure the fix is applied consistently across all shapes.

@mdebbar Thanks for the feedback!

I’ve applied the same fix for Polyline as well, so it’s now consistent across all shapes.
Please let me know if there’s anything else you’d like me to update in this PR.

[mdebbar]

[justinmc]

LGTM 👍 (I saw this on Discord looking for another review, I'm not expert in this package but the changes look good to me.)