dotnet/aspnetcore

Blazor: bind-value-oninput or bind does not work with contenteditable divs

Open

#9,974 opened on May 4, 2019

View on GitHub
 (24 comments) (69 reactions) (2 assignees)C# (10,653 forks)batch import
Pillar: Complete Blazor WebPriority:2affected-fewarea-blazorenhancementfeature-blazor-component-modelfeature-razor.languagehelp wantedon-roadmapseverity-nice-to-have

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

bind-value-oninput or bind does not work with contenteditable divs

Bug Description

In the below code, the expectation is as and when I edit the div content I need to update the model so that I can then save it back to Database.

To Reproduce

Steps to reproduce the behavior:

  1. Using the latest preview version of ASP.NET Core 3
  2. Run the below code <div contenteditable="true" bind-value-oninput="@contentEditableText"> You can Edit this Text </div> @contentEditableText @functions { string contentEditableText = "You can Edit this Text"; }
  3. As I Type something in the editable div, I need to see the same reflected in the body, but it does not happen that way. The OnChange event does not fire automatically.

Expected behavior

OnChange Event needs to fire and changes in editable div should be bound to the model.

Screenshots

Contributor guide

Research direction
Investigate how Blazor's two way binding (`bind`) and `bind value oninput` work with `contenteditable` elements. Look at the source code for event handling in Blazor's renderer to understand why the `oninput` event is not firing for contenteditable divs. Check if there is a workaround using `@oninput` event with JS interop.
Tech stack
csharp
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Blazor
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65