Events being shifted down when more than one on a single day

65 views
Skip to first unread message

chirag...@contextmediainc.com

unread,
Feb 19, 2013, 1:21:25 AM2/19/13
to jquery-wee...@googlegroups.com
I'm using jquery-week-calendar v2.0-dev and when I show two events on the same day, the second event shows the wrong time. See attachment. When I grab the bottom of the first event with the mouse and start resizing, the second event suddenly appears. I have checked all my .js and .css files against the demo in weekcalendar.html. And everything matches. Anyone have any ideas? Thanks! Chirag
ab0ee748-77d3-11e2-9eae-0d4b1bd01668.png

Brian Shaver

unread,
Feb 19, 2013, 9:33:59 AM2/19/13
to jquery-wee...@googlegroups.com
Chirag,
I believe this a problem I've seen reported previously. Here is the solution I've suggested in the past. Brian..

This sounds very similar to an issue I've run into a couple times where the CSS position property on the .wc-cal-event elements gets set to relative instead of absolute. You might try adding a rule like this to your stylesheets:
.wc-cal-event {
  positionabsolute !important;
}
Thanks,
Brian..

On Tue, Feb 19, 2013 at 1:21 AM, <chirag...@contextmediainc.com> wrote:
I'm using jquery-week-calendar v2.0-dev and when I show two events on the same day, the second event shows the wrong time. See attachment. When I grab the bottom of the first event with the mouse and start resizing, the second event suddenly appears. I have checked all my .js and .css files against the demo in weekcalendar.html. And everything matches. Anyone have any ideas? Thanks! Chirag

--
You received this message because you are subscribed to the Google Groups "jquery week calendar" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jquery-week-cale...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

chirag...@contextmediainc.com

unread,
Feb 19, 2013, 2:19:56 PM2/19/13
to jquery-wee...@googlegroups.com
Brian, thanks! I already had the absolute position, but the `!important;` was also necessary

Reply all
Reply to author
Forward
0 new messages