hellohuanlin
hellohuanlin
@chunhtai thanks for sharing. This is "Factor 2" listed above, which covers the case for our `pointer_interceptor`. @jmagman we briefly mentioned that `pointer_interceptor` should have been in the engine. Could...
> I don't have any objection to it being moved into the engine, especially if there is framework code that wants to use it. Sorry for the confusion, framework code...
We just need one more approval thanks. @chunhtai @LongCatIsLooong @cbracken
unsubscribing too - please request my review again when it's ready.
@TimHoogstrate Hi, let me know if you have addressed my comments (and my comments on the previously closed PR). I can take another look.
I am checking if this is ready for a second review on iOS part? Feel free to ping me whenever it's ready.
Thanks. I can also do it on Monday if you haven't yet.
> Please follow our [Hotfix documentation best practices](https://github.com/flutter/flutter/blob/master/docs/releases/Hotfix-Documentation-Best-Practices.md). @itsjustkevin The "Impact Description" section seems close to what's recommended in the link: "When a platform view is clipped by multiple paths,...
@RobertOdrowaz Looks like a regression from https://github.com/flutter/packages/pull/9219
This should be resolved after https://github.com/flutter/packages/pull/9418 is landed.