stuartmorgan-g

> Is there still a conversion in progress? I guess the original federated plugin changes are done? This isn't about federation, it's about https://github.com/flutter/flutter/issues/93732 which is still in progress.

Triage update: iOS webview conversion is still in progress, so this still blocked for the moment.

The Dart conversion is complete, but in the meantime we found https://github.com/flutter/flutter/issues/94051 which blocks this, since we currently implement WebViewPlatformCallbacksHandler in our implementations, making changes to it breaking changes. We're...

Status update from triage: this is still blocked, but we hope to have it unblocked soon.

What's the status of this PR? Is this ready for another round of review?

Okay thanks, I'll go ahead and mark this as a draft for now so it won't show up in triage sweeps, and you can mark it as ready for review...

Sorry for the delay in looking at the error you mentioned; unfortunately the logs have expired so I can't see what the failure was. There are also a lot of...

It looks like the native code implementing the Pigeon interface isn't compiling in this version.

> but I'm not familiar enough with web development to know which is better as the default. It depends entirely on the use case. If it's loading arbitrary web content...

Yes, since making it configurable will require various Dart-side changes, it's blocked on the in-progress reworking of the plugin's Dart code (both platform interface and iOS implementation).