Currently, the Rich Text field triggers the OnChange event every time a user types a character. This behavior differs from other field types, where the OnChange event typically fires only when the user leaves the field (for example, by pressing Tab or clicking outside the control).

This behavior makes it difficult to implement client‑side logic that depends on meaningful user input completion rather than intermediate keystrokes.

Expected Behavior

Provide an option or configuration to allow the OnChange event for Rich Text fields to trigger only when the field loses focus, similar to standard text fields.

Examples of expected triggers:

• User presses Tab
• User clicks outside the Rich Text field
• User navigates to another control

Current Behavior

The OnChange event fires on every keystroke

Custom JavaScript tied to OnChange executes repeatedly while the user is typing

This can lead to:

• Performance concerns
• Excessive script execution
• Poor user experience
• Difficulty aligning behavior with other field types

Impact

• Inconsistent behavior between Rich Text fields and other Dataverse fields
• Increased complexity in client‑side scripting
• Limited ability to validate or process finalized user input
• Additional development effort to implement workarounds or throttling logic

Suggested Enhancement

Introduce one of the following:

• A configuration setting to control when the Rich Text OnChange event fires
• A new event (e.g., OnBlur / OnFocusOut) for Rich Text fields
• Alignment of Rich Text OnChange behavior with standard text fields

This enhancement would greatly improve consistency, performance, and developer experience.