My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1245: CSS header button positions in IE9
1 person 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 bert.dil...@gmail.com, Jan 13, 2012
Hi,

First off thanks for sharing this very well worked out project. It really saved me a lot of coding time!

Using the standard css file, I noticed a placement bug in IE9. It displays all header buttons at the top of the page instead of within the header element margins. It seems this is a known bug for IE9 and is easily solved. (see below)

To recreate this bug, I think it would suffice to add a spaced out div at the top of the page, be fore the calendar div.

I tested all other major browsers and they all support the css without problems.

To fix this issue, add the following code to the header section of the css file :
.fc-header {
  position: relative; /* IE9 fix so children will stay within boundaries */
}

Once again, thanks for sharing!
Cheers Bert.
Aug 14, 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-Defect Type-Bug
Sign in to add a comment

Powered by Google Project Hosting