Power Platform Community Forum Thread Details

Hello Power Apps Community,

I have identified a bug with the modern Text Input control in a Canvas App. The TriggerOutput property does not control when the OnChange event is triggered.

Environment

Power Apps Studio version: 3.26074.8
Control: ModernTextInput@1.1.1
Affected property: TriggerOutput
Tested input types:
- TextInputType.SingleLine
- TextInputType.Multiline
- TextInputType.Password
- TextInputType.Search

Issue

The TriggerOutput property is intended to define when the OnChange event of the Text Input control is triggered.

However, in ModernTextInput@1.1.1, the OnChange event is triggered only after the control loses focus, regardless of the configured TriggerOutput value.

The following settings were tested:

TriggerOutput.Keypress
TriggerOutput.Delayed
TriggerOutput.FocusOut

All three settings behave like TriggerOutput.FocusOut.

With TriggerOutput.Keypress, the OnChange event should be triggered after every keystroke.

With TriggerOutput.Delayed, the OnChange event should be triggered after the configured internal delay.

Instead, OnChange is triggered only when the user leaves the Text Input control.

Test formula in OnChange

Notify(
    Text(Self.TriggerOutput),
    NotificationType.Warning,
    500
)

Steps to reproduce

Add a modern Text Input control to a Canvas App.
Confirm that the control version is ModernTextInput@1.1.1.
Add the test formula shown above to the OnChange property.
Set TriggerOutput to TriggerOutput.Keypress.
Enter text without leaving the control.
Observe that OnChange is not triggered after a keypress.
Leave the control and observe that OnChange is triggered only after the control loses focus.
Repeat the test with TriggerOutput.Delayed.
Repeat the test with all available TextInputType values.

Actual behavior

OnChange is triggered only when the Text Input control loses focus.

TriggerOutput.Keypress and TriggerOutput.Delayed behave exactly like TriggerOutput.FocusOut.

Changing the TextInputType does not affect this behavior.

Expected behavior

When TriggerOutput.Keypress is selected, OnChange should be triggered after every keystroke.
When TriggerOutput.Delayed is selected, OnChange should be triggered after the defined delay.
When TriggerOutput.FocusOut is selected, OnChange should be triggered when the control loses focus.

Impact

This issue prevents the modern Text Input control from being used reliably for scenarios that depend on immediate or delayed input changes, including:

Live search
Dynamic filtering
Immediate validation
Dependent formulas
Custom component logic

Can anyone confirm whether this is a known issue or a regression in Power Apps Studio version 3.26074.8 or ModernTextInput@1.1.1?

Categories:

Power Apps Pro Dev & ISV

Hi,

Thanks for documenting this so thoroughly. Based on your testing, this does appear to be either a regression or an incomplete implementation in the current version of the modern Text Input control rather than an issue with your app.

I've seen similar reports where the TriggerOutput property is exposed on the control but the OnChange event still behaves as if TriggerOutput.FocusOut is always being enforced. The fact that you've tested multiple TextInputType values and confirmed identical behavior across all three TriggerOutput settings strongly suggests the property isn't being honored by ModernTextInput@1.1.1.

For scenarios such as live search, incremental filtering, and real-time validation, many makers are still relying on the classic Text Input control because its behavior is currently more predictable. If your use case depends on keypress-driven updates, I'd recommend testing the same logic with a classic Text Input control to determine whether the issue is specific to the modern control.

A couple of additional things worth checking:

Does the behavior occur both in Studio Preview and in the published app?
Does creating a brand-new app with a single modern Text Input reproduce the issue?
Is the behavior identical in web and mobile players?

If the results are consistent across those scenarios, I'd consider this a product bug and recommend opening a Microsoft Support ticket or reporting it through the Power Apps Ideas/Issues channels with the reproducible steps you've already provided.

Your reproduction steps are clear and detailed enough that other community members should be able to verify whether they're seeing the same behavior with ModernTextInput@1.1.1.

Thanks & Regards,

Manoj Annavajjala