Issue 1386: Presentation issue with chrome.
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by rapidc...@gmail.com, Apr 25, 2012
Firstly thanks for a great calendar..

I am using the Drupal fullcalendar module (http://drupal.org/project/fullcalendar) on a Drupal based website and am having a presentation issue that's only happening in chrome when using the 1.5.x versions of fullcalendar..

I reported the issue (with an image) on the module issue queue here..
http://drupal.org/node/1527854

The image shows the issue where chrome will show rows that contain events as very long compared to the normal empty rows.. By the time there is an event in each week the calendar stretches on for pages and pages..

I have solved the issue by switching back to fullcalendar 1.4.11 so the issue must be being caused by something that changed from 1.4.x to 1.5.x versions..

Sorry I can't be more help than that, I am no good with code..

Thanks..
Aug 15, 2013
Project Member #1 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #2 adamrs...@gmail.com
This message is being bulk-sent to a number of issues, both [very] old and new.

I have been working on taming this issue tracker, which has gotten out of control after months of neglect. You are receiving this message because I could not successfully reproduce the bug you were reporting with a reasonable amount of effort. I have written some new bug-report guidelines to be used by all bug reports going forward:

    http://arshaw.com/fullcalendar/wiki/Report-a-Bug/

Its salient point is that all bug reports should have an isolated demonstration, viewable online with a tool like JSFiddle.

If the bug you originally reported is still important to you, could you please first try the latest version of FullCalendar and see if it is fixed? If not, could you please file a NEW bug report that follows the new guidelines? This issue will not be monitored for further comments.

I'm sorry I have taken so long to respond to many of your request, and I'm sorry if this new procedure causes extra work for you. Going forward, the issue tracker will be much more of a well-oiled machine.

Again, if you must, PLEASE SUBMIT A *NEW* BUG REPORT (following the new guidelines) INSTEAD OF COMMENTING ON THIS ONE. Further comments on this report will be ignored. Thanks.
Status: Invalid
Labels: Type-Bug