DHTMLX
Start Building Professional
Start Building Professional
Web Apps Today
| Categories | Question details Back To List | ||||||||||||||||||||
Problem with sensitive range Hi, look at a sample dhtmlxCalendar/Initialization and Settings/Setting sensitive range. Even when a sensitive range is set those inactive days outside of the range can still be selected. This is incorrect behavior, isn't it? Answer posted by Alex (support) on Mar 19, 2009 10:32 Hello, Could you please provide more details? http://dhtmlx.com/docs/products/dhtmlxCalendar/samples/initialization/calendar_sensitive.html what range must be set and what date can be still selected ? Answer posted by Tession on Mar 19, 2009 13:50 You can set any range it doesnt matter. I attached a picture from the web documentation. I first selected day 26 then 27, the cursor is hovering day 26 which has borders and day 27 is currently selected. Both days are outside of the range. When any other day inside or outside is selected, the color of 26 changes the same as other insensitive dates, 27 turns the same as other sensitive dates. Same happens with any date that is selected next. So those dates outside of range should be unselectable. Attachments (1)
Answer posted by Alex (support) on Mar 20, 2009 02:51 The issue has been reproduced. We'll send you the fix today. Answer posted by Alex (support) on Mar 20, 2009 05:01 Please, try to use attached file instead of the original. It must fix both problems that you've found. Attachments (1)
Answer posted on Mar 23, 2009 01:35 It fixes the problem with selected date indicator when a month is changed but not the problem with sensitive range. When user clicks a date outside of the defined range the selected date indicator does not show anymore but the selected date changes, onclick event is still called and getFormatedDate still returns a new date. So those dates should be totally inactive, i.e. onclick should not be called (or do anything), selected date should not change etc. Answer posted by Alex (support) on Mar 23, 2009 05:42 The problem has been confirmed. We have attached the fixed file. Attachments (1)
|
