Repository navigation
[Flutter Web] Migrate dom shims to a package provided by the Dart sdk when it is available. #113402
Closed as not planned
Description
Because we only implemented the static interop variant of JS interop in Dart2Wasm, we actively migrated all of Flutter / dart:ui from dart:html to custom DOM shims. This bug tracks the effort to deprecate these shims, and replace them with a package provided from the Dart sdk when such a package exists.
Activity
ditman commentedon Oct 20, 2022
Subscribing to this task, plugins/packages will also need to migrate from dart:html / bespoke static interop to this new package, for example:
ditman commentedon Oct 20, 2022
@joshualitt is there a
dart-lang/sdktask to track?[web] Migrate framework to fully use package:web (#128901)
Reland "[web] Migrate framework to fully use package:web (#128901)" (#…
nshahan commentedon Sep 25, 2025
@srujzs
Is this still a long term goal?
srujzs commentedon Sep 26, 2025
I think we ended up going the opposite way with this. We did end up using
package:webbut then decided against it because that means Flutter users are then forced to use a specific version due to the pinning.I believe the plan is to keep the shims and at this point I also believe they've been migrated to extension types. So, this is not planned.
github-actions commentedon Oct 10, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.