On 5/18/2011 1:07 AM, Brian Smith wrote:
See https://twitter.com/#!/scarybeasts/status/69138114794360832: "Chrome 13 dev
channel now blocks certain types of mixed content by default (script, CSS, plug-ins). Let
me know of any significant breakages."
See https://ie.microsoft.com/testdrive/brows
On 18/05/2011 19:25, Brian Smith wrote:
No, he meant dev.security
I could have been more explicit.
and he cross-posted and set the follow-up
header on his message to point to that newsgroup. I agree that if
there's any discussion, it can/should happen there.
But my message ended up with an
Lucas Adamski wrote:
> You mean the private security group list?
No, he meant dev.security and he cross-posted and set the follow-up header on
his message to point to that newsgroup. I agree that if there's any discussion,
it can/should happen there.
- Brian
> I'm curious why you say
> that.
You mean the private security group list? I'm curious why you say that.
Generally we should discuss as much on public lists as possible, especially new
features or changes to existing ones. Security group exists really just to
discuss issues that we can't publicly, because doing so would put
Brian Smith wrote:
See https://twitter.com/#!/scarybeasts/status/69138114794360832:
"Chrome 13 dev channel now blocks certain types of mixed content by
default (script, CSS, plug-ins). Let me know of any significant
breakages."
See
https://ie.microsoft.com/testdrive/browser/mixedcontent/assets/w
See https://twitter.com/#!/scarybeasts/status/69138114794360832: "Chrome 13 dev
channel now blocks certain types of mixed content by default (script, CSS,
plug-ins). Let me know of any significant breakages."
See https://ie.microsoft.com/testdrive/browser/mixedcontent/assets/woodgrove.htm
IE9: h
6 matches
Mail list logo
