stuartmorgan-g

> the other platforms are already doing something like this to render the video into textures on their respective platforms We expect to introduce platform view versions of playback for...

> Hopefully all platforms will support both rendering into a texture or using a platform view depending on the needs of the app then. That is my current expectation for...

From triage: @ditman What's the status of this PR? Is it blocked by potential SDK changes?

This should be ready to review. There's a lot of code, but I went ahead and did all the methods in one PR since having a hybrid of manual method...

Thank you for your contribution. I'm going to close this PR for now since there are outstanding comments, just to get this off our PR review queue. Please don't hesitate...

> Also, the existing tests will need to have the limit parameter added where needed... I think some of them should be failing as is? See [this test](https://github.com/flutter/packages/blob/38711aca66fa91cff1815839f99e9819f3c27d60/packages/image_picker/image_picker_android/android/src/test/java/io/flutter/plugins/imagepicker/ImagePickerDelegateTest.java#L163), for example,...

Yes, there's a very specific pattern for plugins in particular, where the only way to do end-to-end testing of even most individual methods is to run it in the `integration_test`...

Why is it flagging things in `test/legacy/`?

Is `test/` not exempt from this lint? I would have thought unit tests importing from `src/` would be pretty common.

Thanks, that makes more sense. That one we can ignore since it's a very weird special case (upstream testing of something that's a use case that's only allowed within google3)....