I'm getting "This page contains both secure and non secure items.  Do you want to display the non-secure" warning  when I mouseover the linkbutton that launches the popup menu.  It works fine on my http dev server but not, of course, on my production https box.  The interesting thing is the popup works fine  regardless of whether you click yes, no, or cancel and it only prompts once for that page - all the popup menus (I have multiple) work fine after that on the same page.

I've built in a little preference toggle so my peeps can turn it off, but do you atlas control guys  think you can fix it?  Pretty please? 

As Shawn says, this problem kind of surprised us. I dug into it this morning and pretty quickly decided the problem wasn't due to the Toolkit code itself. So I poked around in Atlas a bit, and found out the problem's with Sys.UI.PopupBehavior's implementation of show() that HoverMenu (and PopupControl) uses. On IE, show() does something unexpected that causes this problem. It's described briefly by the Atlas team in this post to their forum: http://forums.asp.net/thread/1270112.aspx.

We're really sorry you've hit this problem, but it's not clear what to do on the Toolkit side of things. Using the PopupBehavior is the "right" thing for HoverMenu to be doing here, so I don't think changing that is a good solution for the Toolkit (though maybe it's a good solution for YOU?). I'm optimistic this will be fixed by the next Atlas release and then the Toolkit controls will automatically benefit. (Fingers crossed!)

Thanks for the report and your patience here!!

Is there any update on this yet? I'm still getting the same error with the latest CTP using a PopupControl on a secure site.

Thanks!

Has this been submitted as a bug to the Atlas team? Is there somewhere I can check on its status and/or promote it on the list?

I'd love to see a fix for this seemingly large bug. It basically makes these toolkit items worthless on any secure sites.

Cool, thanks.

For future reference, do they have a public bug tracking site so we can see the progress of items like this?

I have a workaround posted in this thread: http://forums.asp.net/thread/1364944.aspx

Hopefully the atlas team can incorporate this soon if it hasn't already been done (haven't looked at the July CTP yet!)

I see that this is still an issue in the July CTP.

I really hope this gets fixed in the next release! It's already tough to sell new technologies to the team. If we have to document "workarounds" in our software, it's an even tougher sell.

-Abby