Might not be a module issue, maybe to do with Fullcalendar itself..

In Chrome the month view rows are very long (see attachment) when there is a item in the calendar.. For empty rows the length is normal..

Any ideas?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

faite’s picture

Yeh I have the same thing happening..think it must be a fullcalendar issue and not so much the module

tim.plunkett’s picture

Status: Active » Closed (won't fix)

Yes, I've seen this in certain browsers as well, and this is a bug in the plugin.
See http://code.google.com/p/fullcalendar/issues/list for the plugin's issue queue.

wipeout_dude’s picture

For anyone that finds this thread.. I solved it but using fullcalendar 1.4.11 which suggests that the 1.5.x branch is where the problem is introduced..

I have looked at the full calendar issue queue and cant see this issue reported so not sure why no-one else has come across it..

calefilm’s picture

Wow. Thanks for pointing that out Wipeout. Solved my issue.

LizD’s picture

Do you mean the jQuery plugin version or the Drupal module?
Nevermind - I got it - its the jQuery plugin and it definitely fixes the issue. Thanks!!!!

wipeout_dude’s picture

Status: Closed (won't fix) » Needs work

For anyone that comes across this thread.. The issue is still present in the 1.6.x versions of the plugin..

For future plugin compatibility it seems that the fullcalendar module might need adapting because the plugin demos on the plugin page don't appear to have the issue in chrome (although I don't know which version of the plugin is being used on the demos) as it does when being used by the drupal module..

mariacha1’s picture

Issue summary: View changes

I found this issue to have to do with my theme, which was applying a css transition to all link elements:

a {
  text-decoration: none;
  -moz-transition: all 0.2s linear;
  -webkit-transition: all 0.2s linear;
  transition: all 0.2s linear;
}

This means that all transitions on links are done slowly (so all hovers take a bit of time to change for example).

In Safari, the combination of a css transition AND javascript-altered links lead to the extra spacing between each event. It's like Safari isn't finding the correct height or width of the event while it's transitioning.

Anyway, you can fix this by adding this to one of your theme's css files:

a.fc-event {
  transition: none;
}