1008928: Implemented integration and documentation of Syncfusion RichText Editor within Syncfusion Dialog in Blazor

[KokilaSF4836]

Feature description

1008928 Integration and Documentation of Syncfusion Rich Text Editor within Syncfusion Dialog in Blazor.

Analysis and design

As part of integrating the Syncfusion Rich Text Editor (RTE) inside a Syncfusion Dialog in a Blazor application, the following design considerations were identified:

• Rich Text Editor requires UI refresh when rendered inside a Dialog due to hidden layout during initial render.
• Identified the need to refresh the editor after the Dialog is opened to ensure proper toolbar alignment and sizing.
• Followed Syncfusion‑recommended lifecycle handling for Dialog and RTE components.

Solution description

• Integrated SfRichTextEditor inside SfDialog content.
• Refreshed the Rich Text Editor after the Dialog Opened event to resolve layout and toolbar rendering issues.
• Added clear documentation explaining the correct usage pattern and best practices for using RTE inside Dialog.

Output screenshots

RichTextEditor Inside Dialog

Documentation Preview

Refer the following link for documentation preview

Areas affected and ensured

No areas were affected.

API Changes

No.

Behavioral Changes

No.

Test cases

NA.

Testbed sample location

NA.

Does it have any known issues?

No.

Does it have memory leak?

No.

MR CheckList

• Does it follow the design guidelines? It is mandatory that, we should not move the changes without reading this.
• Did UI automation passed without errors? If it is customer issue, make sure it is included in the IR automation.
• Properly working in Xamarin.Forms previewer.
• Ensured in iOS, Android, UWP and macOS (if supported).
• Have you added API comments if it is new API?
• Does it need localization? If so, update resx file in GitHub.
• Whether we have added new APIs? If so, whether it is as per the guidelines?
• If changes are made in the Xamarin.Forms sample browser project file, whether it is included in the props file too? If not, your sample level changes will not reflect in the application published in the hockey app.
• Have you ensured the changes in Android API 19 and iOS 9?

[SyncfusionBuild]

Build Status: INPROGRESS 🔃
Build Location: 1008928-Dialog-DV

[SyncfusionBuild]

CI Status: FAILURE ❌
Source Compilation: SUCCESS ✅
Failure Reason: CI Failure with violation
Build Location: 1008928-Dialog-DV
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 1
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

[SyncfusionBuild]

Build Status: INPROGRESS 🔃
Build Location: 1008928-Dialog-DV

[SyncfusionBuild]

CI Status: FAILURE ❌
Source Compilation: SUCCESS ✅
Failure Reason: CI Failure with violation
Build Location: 1008928-Dialog-DV
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 1
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

[SyncfusionBuild]

Build Status: INPROGRESS 🔃
Build Location: 1008928-Dialog-DV

[SyncfusionBuild]

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: 1008928-Dialog-DV
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

[KokilaSF4836]

self-review done