https://learn.microsoft.com/en-us/answers/questions/573925/blazor-mouse-events-and-mouse-capture does not include @rendermode on line 2

[Tandry]

Description

The code does not work as presented. Code requires @rendermode InteractiveAuto below @page in order to work properly.

[Enter feedback here]

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/event-handling?view=aspnetcore-9.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/event-handling.md

Document ID

5e8ef502-ccf9-659d-f25a-0f8f3c75f6e0

Article author

@guardrex

Related Issues

[github-actions]

🍂🎃🏮 OOF: Back on Monday, 12/2 🥧☕🍂

Stand by! We're out of the office for the Thanksgiving holiday 🦃.

A green dinosaur 🦖 will be back on Monday (12/2) to assist.

[guardrex]

Hello @Tandry ... That's true for all of the examples across the Blazor doc set that apply generally Blazor. Note that for Blazor WebAssembly, the app is always interactive and doesn't state a render mode; and unless otherwise stated, examples apply to Blazor WebAssembly, too. We also assume that devs had read the Render Modes article, which is early in the table of contents, before reaching these other articles and understand that no component example for Blazor Web Apps that requires interactivity is going to exhibit interactive behavior without an interactive render mode. For these reasons, we'll continue with the current approach for coverage.

[guardrex]

BTW ... It's also covered in the Fundamentals > Overview article in this section ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/?view=aspnetcore-9.0#static-and-interactive-rendering-concepts

[Tandry]

Luke, The point is that there are no references to those articles from where the code is. The code, as copyable from the documentation, does not work - that's a fact. People like me, new to Blazor, are accessing these pages and copying code. The user experience - which is the only thing that matters here - is that Microsoft is supplying unworking code. That's enough to sway people not to pursue working with Blazor right there, and I doubt that's what you want. Other organizations supply working code. Relying on tribal knowledge or saying "well, you should be using the documentation this other way" isn't acceptable. Users (such as myself) use documentation the way we use documentation and the product MUST change to suit the usage pattern of the customer. Given the existence of hyperlinks, there's absolutely no reason not to place something in the documentation to the effect of, "The working of this code sample is affected by the current @rendermode, which may be set elsewhere in the code. Documentation on @rendermode can be reviewed at <http...." I highly recommend changing the current policy to assist customers in consuming these documents. Most won't take the time to open a ticket and respond, they'll just badmouth on social media. I'm hoping my words will have a positive effect and help other folks who may, such as in my case, want to stick with C# instead of learning JavaScript, do so with Blazor. Unfortunately, right now, my experience isn't positive at all. Thanks for your time, Steve

…

On Fri, Nov 29, 2024 at 12:50 PM Luke Latham ***@***.***> wrote: BTW ... It's also covered in the *Fundamentals* > *Overview* article in this section ... https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/?view=aspnetcore-9.0#static-and-interactive-rendering-concepts — Reply to this email directly, view it on GitHub <#34248 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIRWUSXSHMYAUJ6S5QIELXL2DDHTDAVCNFSM6AAAAABSXWMXAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBYGY2TGNRZG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>