My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1711: eventResize and windowResize issues
2 people starred this issue and may be notified of changes. Back to list
Status:  Invalid
Owner:  ----
Closed:  Aug 2013


Sign in to add a comment
 
Reported by andi.l...@gmail.com, Feb 28, 2013
I try to implement a Fullcalendar application based on Rails 3.2, Jquery 1.9 and JqueryUI 1.10 using latest Chromium as browser

Following test cases are re-producible:

Case 1:
Page get loaded, calendar works as aspected. Browser window can be resized HORIZONTALLY multiple times and the calendar fits into its div. The aspect ratio is calculated dynamically getting the width and divided by the height of the parent div in the resizeWindow handler of the calendar.
AFTER the 1st time of a vertically resizing the windowResize handler is not called anymore, no matter if one resize horizontally or vertically.

Case 2
Page get loaded, calendar works as aspected. If one try to resize an event, the windowsResize handler get called and the mouse looses focus on the event . One can point the mouse again on the event and now one can resize the event . However, the windowResize is then dead and is not called when one resize the browser window.

Does anybody observe or have the same issues??

Txs upfront
Jul 29, 2013
#1 es...@inspired.no
can confirm case 2. Window resize results in issue when resizing event.

Example:
$(window).resize(function() {
// stuff
});
Aug 15, 2013
Project Member #2 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #3 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-Defect Type-Bug
Sign in to add a comment

Powered by Google Project Hosting