Move move events on widgets displayed via WidgetComponent will be offset in Standalone

It appears the custom hit testing logic of WidgetComponent handles click positions well via UWidgetComponent::GetHitWidgetPath adding virtual mouse coordinates to the arranged widget, but mouse movements aren't corrected in the same way. This can be remedied by disabling Slate's Fast Widget Paths, which causes FWeakWidgetPath::ToWidgetPath to call into WidgetComponent's TranslateMouseCoordinateFor3DChild to get the proper cursor position, but this causes mouse clicks to offset in the opposite direction. Ideally both clicks and movements would report the same cursor positions, so widgets like the slider can function properly in this scenario.

• Create a widget with a slider. Add it to the world via a widget component. Enable "Receive Hardware Input"
• Start PIE, and note that you can slide the slider as expected
• Launch in Standalone and move the window to the top left corner. Note that the slider works as expected
• Move the window elsewhere on your monitor. The slider can still be clicked to jump the thumb to certain positions, but sliding is offset

I am not able to find world outliner how to enable it?

How can i modify the param name in EQS node

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

How to achieve HLSL Multiple Render Target in Material blueprints?

How to properly terminate the DoWork thread function in FAsyncTask?

How does UMG set overlapping layouts?

Does the pivot parameter setting in the actor's userinterface property relate to the Widget's anchor layout?

Why doesn't the collision diminish when the collision radius decreases?

How to convert the datasmith scene file to BluePrint. Create animations in BluePrint.

How does TextureRenderTarget2D get TArray<uint8> type data?