Uh oh!
There was an error while loading. Please reload this page.
[google_maps_flutter_web]: Adds support for mapTypeControlEnabled, fullscreenControlEnabled, and streetViewControlEnabled. - #12254
Conversation
There was a problem hiding this comment.
Code Review
This pull request adds support for mapTypeControlEnabled, fullscreenControlEnabled, and streetViewControlEnabled to the web implementation of google_maps_flutter. It updates the option translation logic in convert.dart, adds corresponding integration tests, bumps the package version to 0.6.3, and updates the google_maps_flutter_platform_interface dependency to ^2.16.0. There are no review comments, so I have no feedback to provide.
stuartmorgan-g
left a comment
There was a problem hiding this comment.
This needs to be autoformatted on master, per the CI failures.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
stuartmorgan-g
left a comment
There was a problem hiding this comment.
(That was meant to be a request changes.)
…llscreenControlEnabled, and streetViewControlEnabled.
185fbb4 to
871d48aCompareUh oh!
There was an error while loading. Please reload this page.
…llscreenControlEnabled, and streetViewControlEnabled. (flutter#12254) *Part of flutter#11955, flutter#12191 *Part of: flutter/flutter#104111 **Context**: As suggested in the review - flutter#11955 (review), this is a standalone sub-PR separating out just the google_maps_flutter_web changes. ## Pre-Review Checklist **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). 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. [^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.
…er#189983) flutter/packages@8260a1e...6969329 2026-07-24 ionutzubascu@yahoo.com [packages] Migrate all iOS example apps in flutter/packages to UIScene (flutter/packages#12182) 2026-07-23 absarhshah@gmail.com [in_app_purchase] Fixes StoreKit 2 date format does not match in_app_… (flutter/packages#11717) 2026-07-23 269567208+reidbaker-agent@users.noreply.github.com [packages] Add changelog style references to AGENTS.md (flutter/packages#12277) 2026-07-23 ntosarno11@gmail.com [file_selector_android] Surface file-copy failures to Dart instead of crashing (flutter/packages#12107) 2026-07-23 puneetkukreja98@gmail.com [google_maps_flutter] Add support for mapType, fullscreen, and Street View controls on web (flutter/packages#11955) 2026-07-22 engine-flutter-autoroll@skia.org Manual roll Flutter (stable) from ee80f08 to 84fc5cb (5 revisions) (flutter/packages#12273) 2026-07-22 50643541+Mairramer@users.noreply.github.com [camera_avfoundation] Move camera_avfoundation to Darwin (flutter/packages#11847) 2026-07-22 engine-flutter-autoroll@skia.org Roll Flutter from 1ac2e82 to 2a2a79d (22 revisions) (flutter/packages#12272) 2026-07-22 puneetkukreja98@gmail.com [google_maps_flutter_web]: Adds support for mapTypeControlEnabled, fullscreenControlEnabled, and streetViewControlEnabled. (flutter/packages#12254) 2026-07-21 jmccandless@google.com [material_ui] Prerelease setup (flutter/packages#12258) 2026-07-21 kienhantrung@gmail.com [go_router_builder] Allow users to specify onExit as optional (flutter/packages#11151) 2026-07-21 fluttergithubbot@gmail.com Sync release-cupertino_ui-0.0.2 to main (flutter/packages#12265) 2026-07-21 tarrinneal@gmail.com [pigeon] add support for top level consts (flutter/packages#12032) 2026-07-21 49699333+dependabot[bot]@users.noreply.github.com [dependabot]: Bump androidx.activity:activity from 1.12.4 to 1.13.0 in /packages/image_picker/image_picker_android/android (flutter/packages#11253) 2026-07-21 49699333+dependabot[bot]@users.noreply.github.com [dependabot]: Bump cameraxVersion from 1.6.0 to 1.6.1 in /packages/camera/camera_android_camerax/android (flutter/packages#11862) 2026-07-21 49699333+dependabot[bot]@users.noreply.github.com [dependabot]: Bump com.google.guava:guava from 33.5.0-android to 33.6.0-android in /packages/espresso/android (flutter/packages#11864) 2026-07-21 stuartmorgan@google.com [tool] Rename batch change override label (flutter/packages#12263) 2026-07-21 jmccandless@google.com [cupertino_ui] Bump minor to get to 0.0.2, not patch (flutter/packages#12260) 2026-07-21 stuartmorgan@google.com [tool] Support pre-1.0 versions in batch releases (flutter/packages#12257) 2026-07-21 jmccandless@google.com [material_ui] Remove manual version changes (flutter/packages#12253) 2026-07-21 engine-flutter-autoroll@skia.org Roll Flutter from cab057d to 1ac2e82 (23 revisions) (flutter/packages#12256) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC flutter-ecosystem@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Part of #11955, #12191
Part of: flutter/flutter#104111
Context:
As suggested in the review - #11955 (review), this is a standalone sub-PR separating out just the google_maps_flutter_web changes.
Pre-Review Checklist
[shared_preferences]///).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-assistbot 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
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩↩2