starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-02-04 05:35:44 +00:00
Code Issues 1.3k Packages Projects Releases 22 Wiki Activity

[PR #2157] [CLOSED] Date picker - Disable automatic display of virtual keyboard - #1925 #3104

New Issue
Open
opened 2026-01-29 18:21:56 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 18:21:56 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/radzenhq/radzen-blazor/pull/2157
Author: @paulo-rico
Created: 5/16/2025
Status: ❌ Closed

Base: master ← Head: date-picker

📝 Commits (4)

  • 29da7aa DatePicker - disable auto virtual keeyboard
  • 91fda2f Merge branch 'radzenhq:master' into date-picker
  • 34153fb Resolve spelling error
  • b1ef762 Example anchor change

📊 Changes

4 files changed (+32 additions, -2 deletions)

View changed files

📝 Radzen.Blazor/RadzenDatePicker.razor (+1 -1)
📝 Radzen.Blazor/RadzenDatePicker.razor.cs (+7 -1)
➕ RadzenBlazorDemos/Pages/DatePickerDisableAutoVirtualKeyboard.razor (+14 -0)
📝 RadzenBlazorDemos/Pages/DatePickerPage.razor (+10 -0)

📄 Description

This PR addresses the following issue - #1925

Just to clarify. The current behaviour of the DatePicker is to show the on-screen keyboard on keyboardless devices as soon as a user has clicked a date in the popup. This can be quite frustrating as, when you have selected a date, you have to click elsewhere on the screen to close the keyboard.

This PR will give the option to disable that behaviour and not display the keyboard.

Regards

Paul

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/radzenhq/radzen-blazor/pull/2157 **Author:** [@paulo-rico](https://github.com/paulo-rico) **Created:** 5/16/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `date-picker` --- ### 📝 Commits (4) - [`29da7aa`](https://github.com/radzenhq/radzen-blazor/commit/29da7aac455626a04e7856ad6ab88ac1b602655a) DatePicker - disable auto virtual keeyboard - [`91fda2f`](https://github.com/radzenhq/radzen-blazor/commit/91fda2f42537ff746ae2c33c18980fcc5e66de46) Merge branch 'radzenhq:master' into date-picker - [`34153fb`](https://github.com/radzenhq/radzen-blazor/commit/34153fb27fdec48afbbec0efbfba3a5af4caca19) Resolve spelling error - [`b1ef762`](https://github.com/radzenhq/radzen-blazor/commit/b1ef76245bf639c8c458b0846b76be6e3203414c) Example anchor change ### 📊 Changes **4 files changed** (+32 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `Radzen.Blazor/RadzenDatePicker.razor` (+1 -1) 📝 `Radzen.Blazor/RadzenDatePicker.razor.cs` (+7 -1) ➕ `RadzenBlazorDemos/Pages/DatePickerDisableAutoVirtualKeyboard.razor` (+14 -0) 📝 `RadzenBlazorDemos/Pages/DatePickerPage.razor` (+10 -0) </details> ### 📄 Description This PR addresses the following issue - [#1925](https://github.com/radzenhq/radzen-blazor/issues/1925) Just to clarify. The current behaviour of the `DatePicker` is to show the on-screen keyboard on keyboardless devices as soon as a user has clicked a date in the popup. This can be quite frustrating as, when you have selected a date, you have to click elsewhere on the screen to close the keyboard. This PR will give the option to disable that behaviour and not display the keyboard. Regards Paul --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-29 18:21:56 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#3104
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?