Start Building Professional
Web Apps Today

Hi,

I saw a similar question answered on August 3rd regarding dhtmlxWindows and the IE6 "secure / nonsecure items" message.

The patch you posted fixed my problem with the dhtmlxWindows. 

Now I seem to have the same issue with context menus attached to a grid. 

Is there a patch for that?  I can provide an example if needed.

We are using Pro version 2.5 revision 090904

Thank you!

-Chip

Hello,

do you use the latest menu version ? The issue wasn't reproduced locally. Please, check that sample http://www.dhtmlx.com/docs/products/dhtmlxGrid/samples/03_context_menu/01_pro_context_menu.html

The issue only occurs in IE6 when browsing via https

I did get the "secure / nonsecure" message when I tried the above URL in https, i.e.

https://dhtmlx.com/docs/products/dhtmlxGrid/samples/03_context_menu/01_pro_context_menu.html

The version of dhtmlxmenu.js we have is v.2.5 build 090904

Thanks

The issue has been confimed. We are working at fix creating. 

As a quick solution  - please, set the full path to menu icons:

menu.setIconsPath("https://some.com/dhtmlx/90904/dhtmlxMenu/samples/common/imgs/");

The issue has been confimed. We are working at fix creating. 

As a quick solution  - please, set the full path to menu icons:

menu.setIconsPath("https://some.com/dhtmlx/90904/dhtmlxMenu/samples/common/imgs/");

Thanks Alex, the full path workaround is helpful in the meantime.

Not to confuse things, but I also wanted to mention that I found the same issue when initializing the dhtmlxCalendar in IE6 browsing a secure page (https) 

It may be related to an IFrame element rendered by dhtmlxcalendar.js

If I set useIFrame = false, the page reloads without the nonsecure warning.

-Chip

Additional info regarding calendar...

The calendar issue described above (IE6 nonsecure message when browsing https) started after updating to version 2.5. build 90904.

It does not occur if we roll back to dhtmlxCalendar v.2.1 Standard edition build 90226 (dhtmlxCalendar.js)

Hello,

the issue was confirmed and fixed. Please try to use attached dhtmlxcalendar.js.