Issue 1549: Window Resize , Events get out of place
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by deepti...@gmail.com, Sep 24, 2012
Hi Adam,

I am using Wijmo splitter. The right pane contains the full calendar (v1.5.3).
When i resize the window , I set panel2 width and refresh the container as shown below.

var conWidth =$('#wrapperId').width();
$(window).resize(function(){
       $('#panel2Id').css("width",conWidth -200 );
       $("#splitterContainer").wijsplitter("refresh");
}

On resizing, I observe the following:
a. On contracting the browser page, saturday width decreases 
b. On contracting further, the events events move out of place.
c. On Expanding by clicking the restore down button of browser, the saturday width increases more than other cell's width.

Attaching screenshots for your reference.


Regards,
Deepti

Sep 24, 2012
#1 deepti...@gmail.com
How do I attach the screenshots?
Aug 18, 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-Bug