stuartmorgan-g

/cc @jmagman for thoughts on the above.

> Will this actually be rejected by Apple in the review process if it is not addressed? > Please let me know if you have any actual experience. Individual experience...

@l619534951 It sounds like you want https://github.com/flutter/flutter/issues/136314. This issue is is about calls to the Windows embedding APIs in native code.

Can we prioritize this ASAP, given https://github.com/flutter/flutter/issues/149826 ? Running flutter/packages tests against something that isn't what the vast majority of users will be using isn't ideal. And longer term, I...

> The Dart `Uri` class does not recognize most schemes specially. The `mailto:` scheme is treated the same as any other scheme, so the query part is encoded using [URL...

(Also, perhaps [the encodeComponent docs](https://api.dart.dev/stable/2.12.4/dart-core/Uri/encodeComponent.html) could be updated in the short term; currently they say "For encoding the query part consider using encodeQueryComponent." which is *actively misleading* advice for any...

The simplest safe solution I can see at this point to use Uri for anything that has query parameters but isn't an http* URL is to manually re-implement what `queryParameters`...

Can you comment on the possiblity of doing one of the two small changes I suggested above (a new named constructor for non-web Uris, or a breaking change for the...

> A new constructor which does only rudimentary normalization (and the `normalize()` would have to do full normalization) could be an option. I'm confused; I don't think this issue has...

To elaborate on the background here, as an illustration of the use case I'm trying to solve: the `url_launcher` plugin for Flutter takes a URL (currently as a `String`, but...