| Issue 1430: | Time slot selected incorrectly in day view. | |
| 2 people starred this issue and may be notified of changes. | Back to list |
I found a couple of reports of this issue but no resolution hence reporting it again. In day view when you click on a time slot, it selects a later time slot. Works fine on very early hours (upto 3 am or so) and then the time slot selected moves to 30 to 90 minutes later than what is actually clicked on. I am using the default code and have made no changes. This are the previous reports I found: code dot google dot com/p/fullcalendar/issues/detail?id=631 code dot google dot com/p/fullcalendar/issues/detail?id=1216
Aug 6, 2012
#1
jsneld...@gmail.com
Aug 6, 2012
Another observation: In 'week' view (I should clarify, my last comment was also related to 'week' view) with 24 hours show an 30 minutes slots. Prevision is perfect for the first slot (12:00am-12:30am), about 1 or 2 pixels off for the second slot (12:30am-1:00am), and continues to degrade from there. By the time I click the 10:30pm-11:00pm slot the final slot is actually selected, and when I click either of the final 2 slots nothing happens. Ah ha! I just realised I was using custom styles, and when I removed reference to the stylesheets slot selection returned to normal and perfect. I'll now check out my styles to see what's interfering with fullcalendar.
Aug 6, 2012
I found the problem!
In one of my base/reset stylesheets I have:
body
{
line-height: 1.5;
}
And that's it. Reset the line-height back to '1' in CSS body selector (i.e. body { line-height: 1; } ) and slot selection works perfectly again.
Aug 6, 2012
Thanks for the response, you seem to have analyzed it well. However, following your approach did not help me discover any obvious styling issues. I know its a custom css issue but given that you are likely to have lots of custom css for your website (I use an HTML5 framework that uses <article> and <section> tags) it would be a challenge to pin-point the exact cause. Unless the developers of this wonderful widget could advise on what could cause interference.
Jul 19, 2013
In my case the problem was that I had: table td {padding:4px}, this was causing the issue, I had to reset the padding to 0 ( .myCalendar table td {padding:0} ) and all worked fine after that
Aug 15, 2013
(No comment was entered for this change.)
Status:
Duplicate
Mergedinto: 1035 |
|
| ► Sign in to add a comment |