Unplanned
Last Updated: 07 Dec 2023 14:04 by Ray

Steps to replicate the issue:

  • Set the computer's Time Zone to CST (Central Standard Time) which is UTC -6:00.
  • Enable Daylight Saving
  • Open VS and create a new Page with a DatePicker in it (basic settings)
  • Select the date "4/1/2023" and picking the time "2:00 AM" jumps to "3:00 AM"

Important: for the Time Zone changes to have effect, the Visual Studio solution has to be closed/re-opened.

Unplanned
Last Updated: 29 Mar 2019 12:38 by ADMIN
When the DatePicker is with enabled WAI-ARIA support, Jaws reads "link 11" instead of the selected date "Monday, March 11, 2019".
Unplanned
Last Updated: 08 Apr 2020 15:43 by ADMIN

Hi,

For the date picker and it's family of controls (time picker, date time picker), when using bootstrap skin, lightweight rendering and RTL page, the buttons for the picker are displayed on the wrong side of the control (the right side) instead of being displayed on the left side. I know this can be fixed using some CSS but although the html controls are in order (text and then button both in a container with RTL), the button is stuck to the right side somehow

please advise

Unplanned
Last Updated: 16 Sep 2020 11:27 by ADMIN
Created by: Neale Hayes
Comments: 0
Category: DatePicker
Type: Bug Report
0

1) There is no element with the id or name as the value of the aria-controls attribute of the dateinput button with enabled ARIA support. 

2) The aria-valuemin and aria-valuemax attribute are not valid on role=textbox

To fix these, the following workarounds can be used

Option 1: OnClientLoad event of the DateInput element inside the DatePicker

function DatePickerOnClientLoad(sender) { setTimeout(function () { $telerik.$(sender.get_element()).parent().find("[role=button][aria-controls]").removeAttr("aria-controls");
$telerik.$(sender.get_element()).removeAttr("aria-valuemin").removeAttr("aria-valuemax") }) }

 

Option 2: using Sys.Application.Load event

function pageLoadHandler() {
    $telerik.$("[role=button][aria-controls]");
    $telerik.$("[role=textbox]").removeAttr("aria-valuemin").removeAttr("aria-valuemax");
    // Sys.Application.remove_load(pageLoadHandler);  
}
Sys.Application.add_load(pageLoadHandler);

 

 

 

Unplanned
Last Updated: 09 Mar 2023 09:35 by Sarkis

We are in the process of upgrading our controls to Telerik. We had noticed a behavior that we did not want to happen, this was related to DatePicker control changing the value of the date if incorrect format was entered, we solved this by having EnableSmartParsing to false in our Telerik Theme so that it applies to all DatePicker controls.

Now we have some instances of date controls that are defined with specific DateFormat/DisplayDateFormat like below:

<telerik:RadDatePicker ID="dpId" DateInput-DisplayDateFormat="y" DateInput-DateFormat="y" runat="server"></telerik:RadDatePicker> or 

<telerik:RadDatePicker ID="dpFrom" DateInput-DateFormat="MM/yyyy" DateInput-DisplayDateFormat="MMM, yyyy" runat="server"></telerik:RadDatePicker>
Now since we have the below set in a theme these controls will also pick up the global properties, and it looks like having DateInput-EnableSmartParsing="false" along with any different DateFormat/DisplayDateFormat is always rejecting the value being entered (error is shown as wrong format being entered with exclamation mark). Is this due to limitation of having EnableSmartParsing="false" ? setting this to true resolves the issue for these controls, i just want a confirmation if this is by design and what sort of workarounds there are?
<telerik:RadDatePicker runat="server"
  DatePopupButton-Visible="false" 
  PopupDirection="BottomLeft" 
  ShowPopupOnFocus="true" 
  DateInput-EnabledStyle-HorizontalAlign="Left" 
  DateInput-EnableSmartParsing="false"  
  MinDate="0001-01-01">
</telerik:RadDatePicker>