Cannot Edit Content After Inserting A Video

[Brian Pautsch]

Start with no content in the editor and insert a video, audio or image. When it completes, you cannot type more content or put the cursor in the edit area. This only occurs when LayoutOption or Display is Break.

<RichTextEditorAudioSettings LayoutOption="DisplayLayoutOptions.Break" />
<RichTextEditorImageSettings Display="ImageDisplay.Break" />
<RichTextEditorVideoSettings LayoutOption="DisplayLayoutOptions.Break" />

Example: https://www.loom.com/share/14389bf3452a4128bf0116b8cbfd9c05

Attached is an example you can run. Be sure to set the key in Program.cs.

Attachment: SFIssues20260226_e83e50bd.zip

[Brian Pautsch]

Any updates?

[Vinitha Jeyakumar]

Hi Brian Pautsch,

We have considered the reported issue "Cannot type after inserting audio or video into the RichTextEditor " as a bug from our end, and the fix for the issue will be included in our upcoming weekly patch release scheduled for the end of March 2026

Now you can track the status of the reported issue through this feedback,

https://www.syncfusion.com/feedback/73014/cannot-type-after-inserting-audio-or-video-into-the-richtexteditor

Regards,

Vinitha

[Brian Pautsch]

Vinitha - Is this still planned for release today or tomorrow?

[Vinitha Jeyakumar]

Hi Brian,

We have included the fix for the reported issue "Cannot type after inserting audio or video into the RichTextEditor" with our weekly patch release version 33.1.46. Please upgrade your package to the latest version to resolve the issue from your end.

Release Notes: https://blazor.syncfusion.com/documentation/release-notes/33.1.46?type=all#rich-text-editor

Root Cause: 

The reported issue occurs because only a space was added next to the audio and video elements after insertion.

Regards,

Vinitha

[Brian Pautsch]

We see the updates to the individual components, but the Core is still  33.1.45.

This is preventing the components from getting upgraded.

NUGET UPDATE ERROR:

CURRENTLY INSTALLED:

Notice the Core doesn't have a 33.1.46 available to upgrade to.

[Brian Pautsch]

Please advise

[Brian Pautsch]

ISSUES!

We see the Syncfusion.Blazor.Core nuget package is out there now.

We upgraded to v33.1.46 and now BOTH "Inline" and "Break" mode cause issues. It's now worse than before.

Same issue: When we upload an image or audio or video in an empty RichTextEditor area, we can no longer edit anything. You cannot place the cursor anywhere.

Please expedite this fix.

[Vinitha Jeyakumar]

Hi Brian,

We were unable to reproduce and analyze the behavior at our end. After upgrading to the latest V33.1.46, the issue was resolved successfully. We recommend trying the following steps on your side:

Suggested Actions

1. Clear browser cache and hard refresh
• This helps ensure that no older scripts or styles are being loaded.
2. Clear NuGet cache and restore packages
• You can run:
  
  

  dotnet nuget locals all --clear

  dotnet restore

  
  

  
  
3. Rebuild and run the application again.

After performing the above steps, uploading an image, audio, or video into an empty RichTextEditor works as expected, and the cursor can be placed normally in both Inline and Break modes.

We have also attached a video illustration for your reference.

Regards,

Vinitha

Attachment: screencapture_(22)_af370908.zip

[Brian Pautsch]

I found the issue:

When using the built-in "Insert Audio" or "Insert Video", I see your code adds a " " after the media. This allow the cursor to be placed in the editor.

But when we execute a command, it does not. We are executing these commands:

await _rteMessage.ExecuteCommandAsync(CommandName.Audio, new AudioCommandsArgs() { Url = value });

await _rteMessage.ExecuteCommandAsync(CommandName.Video, new VideoCommandsArgs() { Url = value });

where "value" is a URL.

[Vinitha Jeyakumar]

Hi Brian,

We attempted to reproduce the reported issue based on the details you shared. However, we were unable to observe the behavior you described while inserting audio and video using the ExecuteCommand API.

For your reference, we have prepared a sample along with a video illustration demonstrating the expected behavior.

To further investigate this issue, could you please share the exact steps to reproduce the problem? Additionally, providing a video illustration and a simple, runnable sample that reproduces the issue, or modifying the attached sample with the issue-reproducing code, would greatly help us analyze the scenario in detail and assist you more effectively.

Regards,

Vinitha

Attachment: SFIssues_fixed_d582ecf3.zip