ViewStyleProps backfaceVisibility

[asklar]

Set backfaceVisibility='hidden' on a square with text, it's a no-op. Rotate the item 180 degrees and see the text reversed (should not be shown)

[asklar]

looks like this was an issue for Android until recently. See here facebook/react-native#15970

[chrisglein]

Comp supports this but we believe XAML does not. Either needs us to go directly to Comp or add support to XAML in WinUI3.

[kmelmon]

A possible solution here would be to stop using the "facade" animation properties and instead animate the underlying Composition Visual directly, by using ElementCompositionPreview.GetElementVisual(). This has the advantage of going further downlevel as well, but has a possible disadvantage: GetElementVisual is the "old" way of doing animations and isn't compatible with facades. Stephen Peters pointed out that the WinUI controls use facades on Content controls, so if someone were to wrap a WinUI control and also wrap the Content that goes inside the WinUI control, those controls will be locked into using facades. We don't currently have any such controls but it could happen someday.

From email conversation:

Keith says:
Thanks for pointing that out, Stephen! The problematic scenario would come up if these all happen:

1. A new RNW control is created that wraps a WinUI control.
2. The WinUI control uses facades on “itself”.
3. The RNW app author uses the RN transform property on one of these wrapped controls.
   I don’t believe have wrapped any WinUI controls yet. But we could someday. I am mostly interested in Roslyn analyzer for NativeModuleBase #2 at this point. Stephen can you confirm if this is the case? Ie do we have any controls that use facades on the app-facing, “outermost” UIElement?

If the above can all happen, maybe we can just create an additional UIElement to parent the WinUI control.

Stephen says:
We don’t but we do have some controls which use facades on content put into their content presenter (I’ve argued that this is a mistake before but we’ve never fixed it) So if you wrapped one of these WinUI controls, exposed the content property and then the app author animates the content you could hit the issue.

[chrisglein]

Not something we plan to address on the Paper renderer as we move towards Fabric.
Fabric API completion is tracked here: #11144