Rank 1
Iron
Hello everyone,
Here are the highlights of the new online resources we published this week from 20 Oct 2025 to 27 Oct 2025:
Article: https://www.telerik.com/blazor-ui/documentation/upgrade/rendering-changes/9-0-0
Summary:
This article documents the rendering changes in Telerik UI for Blazor
9.0.0, including updates to component DOM structure and CSS class names
that can affect styling and selectors. Use it to identify breaking
changes, update custom CSS and UI test selectors, and apply the
component-specific migration steps after upgrading.
Article: https://www.telerik.com/blogs/blazor-vs-javascript-blazor-right-choice-next-project
Summary:
This article compares Blazor vs JavaScript frameworks and gives you
practical decision criteria based on team skills, app requirements,
performance, hosting, and SEO. It explains Blazor WebAssembly and Blazor
Server trade-offs (payload size, startup time, latency, persistent
connections, offline support) versus React/Angular/Vue and the broader
JavaScript ecosystem, and outlines when to choose Blazor for end-to-end
.NET and code sharing versus JavaScript for minimal bundles and access
to front-end libraries.
Feel free to check them out and share your thoughts!
The Telerik Team
---------------------------------------------------------------------------------------------------------------------------------------------------------
Hello everyone,
Here are the highlights of the new online resources we published this week from 13 Oct 2025 to 20 Oct 2025:
Article: https://www.telerik.com/blazor-ui/documentation/knowledge-base/grid-access-gridsearchbox-value
Summary: The article shows how to get the current search text from the Telerik UI for Blazor GridSearchBox so you can use it in custom logic. Capture it by binding GridSearchBox.Value or handling ValueChanged in the Grid toolbar; for OnRead/server binding, extract the quick-search term from GridReadEventArgs.Request.Filters (the OR composite filters produced by the search) or from the grid state via OnStateChanged.
Article: https://www.telerik.com/blazor-ui/documentation/knowledge-base/dockmanager-add-content-pane-footer
Summary: Add a sticky footer to a Telerik UI for Blazor DockManager ContentPane by wrapping the pane content in a full-height container and using CSS (flex column or grid) so the main area scrolls while the footer stays pinned to the bottom across docked, floating, and tabbed states. The article shows the pane content structure and required styles (height: 100%, overflow, borders) to place actions or status info in the footer without affecting the DockManager layout.
Article: https://www.telerik.com/blazor-ui/documentation/knowledge-base/scheduler-add-hyperlinks-in-appointments
Summary: Learn how to add clickable hyperlinks inside Telerik UI for Blazor Scheduler appointments by rendering anchor tags in the appointment template and binding them to a URL field. The article shows how to prevent the Scheduler’s edit/drag behavior from intercepting clicks (e.g., with @onclick:stopPropagation and optionally @onpointerdown:stopPropagation or draggable=false) and how to open links safely in a new tab.
Article: https://www.telerik.com/blazor-ui/documentation/api/telerik.blazor.components.schedulerrecurrenceeditmode
Summary: SchedulerRecurrenceEditMode is an enum in Telerik.Blazor.Components that tells the Blazor Scheduler whether an operation targets a single occurrence, the entire series, or the following occurrences of a recurring appointment. Use it in your Scheduler CRUD event handlers and data logic to apply edits and deletes to the correct set of items, including when you replace the built-in recurrence prompt with custom handling.
Feel free to check them out and share your thoughts!
The Telerik Team
---------------------------------------------------------------------------------------------------------------------------------------------------------
Hello everyone,
Here are the highlights of the new online resources we published this week from 06 Oct 2025 to 13 Oct 2025:
Article: https://www.telerik.com/blogs/blazor-basics-using-local-storage-save-restore-form-input
Summary: You will use IJSRuntime to interact with browser localStorage, serialize your form model to JSON, and hook EditContext.OnFieldChanged and OnAfterRenderAsync to save and restore Blazor form input. The article walks through wiring an EditForm to persist changes as users type, repopulate values on first render (including Blazor Server after prerender), and clear storage on submit, with guidance on key management, debouncing, and avoiding sensitive data. Apply this to keep form state across reloads and navigation in Blazor WebAssembly and Server.
Feel free to check them out and share your thoughts!
The Telerik Team