# Workaround for UE-173626?

**URL:** <https://forums.unrealengine.com/t/workaround-for-ue-173626/749571>\
**Category:** UI\
**Tags:** unreal-engine, bug-report, question\
**Created:** [January 15, 2023, 2:29am UTC](https://forums.unrealengine.com/t/workaround-for-ue-173626/749571 "2023-01-15T02:29:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Clonkex](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Clonkex](https://forums.unrealengine.com/u/Clonkex)\
**Post date:** [January 15, 2023, 10:39pm UTC](https://forums.unrealengine.com/t/workaround-for-ue-173626/749571/4 "2023-01-15T22:39:05Z")

</div>

Aha. I believe this is the primary ticket for this issue: [Unreal Engine Issues and Bug Tracker (UE-166377)](https://issues.unrealengine.com/issue/UE-166377)

According to [this post](https://forums.unrealengine.com/t/widget-interaction-component-press-pointer-key-broken/695305/8) (which the commenter has also posted in a few other relevant threads I found) the issue is due to [this commit](https://github.com/EpicGames/UnrealEngine/commit/dad870090760393fc04848f3a680ea121a126069). The first comment matches my experience (that it’s flushing the input). I guess I will try to build from source so I can attempt to revert that change.

I notice the commit description mentions a Jira ticket with `FORT` in the name, so I guess the change was made because of a Fortnite issue. I’ve only played Fortnite once, back before it was a BR, so I can’t say whether they make use of in-world UI elements and WidgetInteraction components.

---

_[View the full topic](https://forums.unrealengine.com/t/workaround-for-ue-173626/749571)._
