Updates:
Cc: [email protected] [email protected]
Comment #4 on issue 25357 by [email protected]: Need to deal with non-SSL
reads from shared workers
http://code.google.com/p/chromium/issues/detail?id=25357
Seems the thread mentioned above (Adam, specifically) leaned to fixing this
at the
end:
"In summary, I think we should trigger a mixed content warning if a
secure origin creates an insecure shared worker to prevent developers
from working around the mixed content indicator with shared workers. "
If I read it correctly, most other replies on the thread were in favor of
propagating
the mixed content warning as well.
Can haz broken lock? If it's a lot of implementation it's fine to delay but
I think we
should not lean to wontFix on this one.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
