Sounds like Chrome devs don't plan on fixing the issue. https://code.google.com/p/chromium/issues/detail?id=582603mkwst@chromium.org:"We are ratcheting down on mixed content, and are intentionally making it more difficult to execute mixed script. We intend to show the shield less often, with the eventual goal of removing user-visible surface entirely."It will be interesting to see if Adobe drops Chrome as a supported browser for their "Enhanced Experience Composer".

mklooster wrote... In the mean time you can work-around this issue by using a different browser...

Correct... Although, it's actually the other way around. (script is HTTP while main page is HTTPS). Anyway, that's not important. Normally, by clicking the Shield icon in Chrome on FF you can allow scripts/css with different protocols to load onto an HTTPS page (thus allowing Target to work with non-https websites). However, there was a bug introduced on 01/29/2016 that broke the "shield" functionality when a site is iFramed (which is the case with Target Premium).Please read the linked issue on...