[19:53] <MikeRL> Hello. I have noticed that for some reason (probably Google changing from https://www.google.com/ to https://www.encrypted.google.com/), that searches are no longer encrypted by default. This effect the Firefox 15 RC.
[19:53] <MikeRL> I mean effects. Can anyone else confirm this bug?
[19:54] <bhearsum> MikeRL: you should try asking in #firefox on irc.mozilla.org
[19:54] <MikeRL> Thanks.
[21:23] <MikeRL> After extensive testing and trying out Mozilla's official builds, HTTPS not working by default with Google is an Ubuntu-only issue.
[21:23] <MikeRL> It only ocurrs with builds from the Mozillateam PPA. Including Nightlies and the Security Team. We should fix this, as it is a privacy concern.
[21:24] <MikeRL> If anyone else can confirm this, I will report it to LaunchPad ASAP.
[21:24] <micahg> MikeRL: I think that's a known issue, not sure what the current blocker on that is, chriscoulson might know more
[21:24] <micahg> MikeRL: ISTR that it's not a regression in  15 though
[21:25] <MikeRL> Is he here now? If not, when will he be available?
[21:25] <MikeRL> Nope, it only ocurrs in the PPA builds. Not directly from Mozila's site. Tried all in safe mode. See if you can reproduce.
[21:25] <micahg> MikeRL: tomorrow european day
[21:26] <micahg> MikeRL: I mean in our 15 build, Bug #978444
[21:26] <ubot2`> Launchpad bug 978444 in firefox "HTTPS is not used for Google searches" [Wishlist,Triaged] https://launchpad.net/bugs/978444
[21:26] <MikeRL> Anytime during the day (in Europe).
[21:26] <micahg> hrm, that seems to support it's a regression in 15 :(
[21:27] <MikeRL> What is causing it? Does anybody know?
[21:27] <micahg> ah, I see, not a regression, we're just missing a feature that upstream has which isn't good but isn't the end of the world
[21:27] <MikeRL> Can you guys include it? Do you know how to?
[21:28] <micahg> yeah, it has to do with the search plugins
[21:28] <MikeRL> Is it to hard to fix ASAP if possible. I know you have a lot on your plate.
[21:29] <micahg> hi chrisccoulson, MikeRL was wondering about the https by default search plugins, any idea for a timeframe on those?
[21:30] <MikeRL> I can use HTTPS everywhere as a workaround for now.
[21:35] <MikeRL> But if it's any easy fix, by all means, try fixing it soon, please.
[21:35] <MikeRL> It also occurs when searching from about:home.
[21:35] <MikeRL> He timed out...
[21:36]  * micahg must have pinged him too many times :)
[21:36] <micahg> it's late there anyways
[21:37] <MikeRL> Anyhow, if he won't come back, what time should I come back tomorrow? I live in Maryland (same time zone as New Yorkish) in the US.
[21:37] <micahg> MikeRL: morning
[21:37] <MikeRL> Early morning?
[21:38] <micahg> anytime US EST morning should still be UK work day
[21:38] <MikeRL> OK, good. Thank you and goodbye.