Chris Glein

I just tried creating a fresh 0.73.8 project with these steps: ``` npx react-native@latest init blankApp --version "latest" cd blankApp npx react-native-windows-init --overwrite npx react-native run-windows ``` And it built...

So glad to hear you're unblocked! You ran the dependency script and it ran clean (all green checks)? If so then this may be a problem with the dependency script...

> This doesn't seem within the scope of the initial 0.62 release. Flagging for retriage. We should backport this to 0.62 after release as its non-breaking and there's a customer...

If we need to flip the mouse wheel direction and the platform doesn't support this, then this may turn into a WinUI3 ask. @rectified95 let us know what recommendation you...

So the issue is with the `intl` implementation that was copied from Chakra, and we should be calling the native Windows APIs. But that introduces a support difference in Windows...

On UWP RNW we implemented this with a negative scale transform. Which... had quirks, but mostly got the job done. But we probably just need that same sort of fix...

There's custom handling for the known parts of the headers, but I thought the rest were passed through as a property bag. @JunielKatarn is that accurate? Is there any handling...

Thanks for the great detail on this bug report. Potentially could have been affected by this PR: https://github.com/microsoft/react-native-windows/pull/10712 Certainly though this shouldn't crash. Thanks for the set of suggested fixes.

> However, the question I wasn't able to answer, and whether it's expected behavior, is why `YGNodeLayoutGetWidth ` or `YGNodeLayoutGetHeight` return `NaN` (as opposed to something like 0) for such...

@JunielKatarn Any immediate ideas?