Issue 504: SSL in IE7 forces a nonsecure popup (caused by resizable)
Status:  Released
Owner: ----
Closed:  Aug 2013
Reported by matt.man...@gmail.com, Jun 2, 2010
I am hosting my site through SSL and when the calendar is rendered in IE7,
I receive a security popup that says "This page contains both Secure and
nonsecure Items"

This only happens when I set the Editable Property = true.  If I set
editable to false, this behavior does not occur.

I've confirmed that all of my url's in the html are specifying https.  One
thought I have is that the calendar might be loading an i-Frame.  When IE
finds an iFrame without a src attribute specified, it will throw this
security popup.

Jun 16, 2010
Project Member #1 adamrs...@gmail.com
that is very strange. fullcalendar does not do anything like with iframes. i don't see how this could be happening. would you be kind enough to post a demo of the bug, hosted on one of your servers with the ssl? i dont have an ssl cert or have the desire to set any of that up on my personal server. thanks a ton
Jun 18, 2010
#3 Erwan...@gmail.com
It's the hover fix for IE (both IE6 and IE7).

On the CSS, remove this line (line 296 on 1.4.6 for .fc .ui-resizable-handle classes):
	background: url(data:image/gif;base64,AAAA) !important; /* hover fix for IE */


You can use conditionals comments for this background hack on IE8 only if you are on https.
Jun 25, 2010
#4 Erwan...@gmail.com
you can use a transparent 1px gif (just google blank.gif) for the background
works on IE6 / IE7 and over SSL without warning (of course, blank.gif hosted on your https server ;) )
Jul 5, 2010
Project Member #5 adamrs...@gmail.com
Erwan, thanks for the post. i will try to get this fixed in the next release. i try to avoid using image dependencies w/ fullcalendar, so i am going to try some other solutions first, but thanks for pointing me in the right direction
Summary: SSL in IE7 forces a nonsecure popup (caused by resizable)
Status: Accepted
Mar 20, 2011
Project Member #6 adamrs...@gmail.com
this is fixed in 1.5. thanks for the bug report.
Status: Fixed
Aug 13, 2013
Project Member #7 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Implemented
Aug 13, 2013
Project Member #8 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Released