Modern Controls Text Input

(0) Share

Report

Posted on by MB-15051032-0

It appears that on Modern Tex Input controls, the OnChange event/property is not correctly triggered like the Classic Text Input control, even with `Trigger output` set to `Key press`. I have tested this in both Chrome and Firefox with the same result using a Notify() function. It doesn't trigger unless I change the control focus.

The modern controls also don't work with the SetFocus function.

I am also surprised to find that, for a single line text field, enter doesn't submit the value and cause the field to lose focus (you know, like 99.9% of other apps, web or otherwise). Any legitimate reason for this behaviour?

I was hoping to use Power Apps as a way to create an app that can be maintained by users who have less experience writing code, but given the above I'm now starting to doubt going down this route if I have to use hacky workarounds for basic functionality.

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

Kalathiya 2,151 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello @MB-15051032-0,

Select "Focus Out" in Trigger output and try.

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

---------------------------------------------------------------------------------

📩 Need more help? Just mention @Kalathiya and I’ll be happy to assist.

✔️ If this answer helped you, please tick “Does this answer your question?” so it can be marked as the Verified Answer.

💛 A Like always motivates me to keep contributing!

Was this reply helpful? Yes No
MB-15051032-0 8 on at

Like (0)

Report
Copy link

Link copied!

@Kalathiya Thanks for the suggestion. Unfortunately it still doesn't work as expected.

Based on the following docs, I would have expected the default mode of key press to update on every character change:
https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/controls/modern-controls/modern-control-text-input

This does not appear to be the case.

Does the modern control work as documented for you?

Was this reply helpful? Yes No
Suggested answer

CarlosFigueira Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!
The TriggerOutput property for the modern text input control doesn't affect how the OnChange behavior is called. Instead, it only affects how the output Text property (which can be referenced in other controls) is updated. The documentation calls it out explicitly:

OnChange – How the app responds when the user changes the text. This event fires when the user moves focus away from the control (on blur), not on every keystroke. This improves performance and prevents issues with rapid formula execution.

The screen capture below shows how each possible value for the TriggerOutput property affects the output of the text input control - and that the OnChange trigger is not affected by it.

If you copy these controls into a blank app you should see the same behavior.

- TextInput2: Control: ModernTextInput@1.1.0 Properties: Default: ="Hello" OnChange: |- =Collect(events, $"[{Text(Now(),"hh:mm:ss.fff")}] OnChange: {Self.Text}") TriggerOutput: =Dropdown1.Selected.Trigger X: =40 Y: =78 - Text1: Control: ModernText@1.0.0 Properties: Height: =33 Text: =TextInput2.Text Width: =320 X: =40 Y: =32 - Dropdown1: Control: ModernDropdown@1.0.0 Properties: Default: ={Name:"Keypress",Trigger:TriggerOutput.Keypress} ItemDisplayText: =ThisItem.Name Items: =[{Name:"Keypress", Trigger:TriggerOutput.Keypress},{Name:"Delayed", Trigger:TriggerOutput.Delayed},{Name:"FocusOut", Trigger:TriggerOutput.FocusOut}] X: =40 Y: =133 - Text2: Control: ModernText@1.0.0 Properties: Height: =218 OnSelect: =Clear(events) Text: =Concat(events, Value, Char(10)) Width: =373 X: =423 Y: =32

Was this reply helpful? Yes No
Suggested answer

Vish WR 3,259 on at

Like (1)

Report
Copy link

Link copied!

@MB-15051032-0

OnChange on the modern text input fires on blur (focus loss), not on every keystroke — that's by design, not a bug. TriggerOutput only controls when the Text property updates in other controls, it has nothing to do with when OnChange fires.

So if you need something to react on every keystroke, reference TextInput.Text directly in your formula on another control rather than relying on OnChange. That way it updates live based on whatever TriggerOutput mode you've set.

Was this reply helpful? Yes No
MB-15051032-0 8 on at

Like (0)

Report
Copy link

Link copied!

@CarlosFigueira Thanks for the clarification. Is there a reason behind the design of not having the enter key for single line text input fields not acting as blur / change focus like the tab key does? I think most users would expect an OnChange event when pressing enter as this is the standard for submit.

@Vish WR Thanks for the explanation. Does that make it impossible to react/perform an action when the enter key is pressed? For example, monitor for the enter key and then use SetFocus to force and OnChange event (hacky solution...).

Where would I report the SetFocus function not working on Modern Controls?

Thanks

Was this reply helpful? Yes No