On Wed, Nov 21, 2012 at 4:07 PM, wrote:
> In VS2010 you can have symbols in your watch window that are in an
> anonymous namespace and you can put breakpoints on them. For example:
>
> namespace {
> int g = 42;
> }
>
> In your Watch window, add g, and you can see 42.
>
> If you have an anonymo
That's not exactly correct.
In VS2010 you can have symbols in your watch window that are in an anonymous
namespace and you can put breakpoints on them. For example:
namespace {
int g = 42;
}
In your Watch window, add g, and you can see 42.
If you have an anonymous namespace inside of anothe
On Wed, Nov 21, 2012 at 3:19 PM, wrote:
> Maybe there's a specific case where you can reproduce this, but in general
> I've always been able to set breakpoints in unnamed namespaces.
> I've tested just now with a simple app in VS2008, VS2010 and VS2012. And
> on those debuggers it works fine.
>
> Even worse, in Visual Studio 2010 (not sure about 2012),
> you can't set a breakpoint on an anonymous-namespace symbol
> *at all*. And we can't submit patches to fix that, either :-).
Maybe there's a specific case where you can reproduce this, but in general I've
always been able to set break
On 21/11/12 14:09, Justin Dolske wrote:
> On 11/20/12 1:31 PM, Mihai Sucan wrote:
>> Hello!
>>
>> Any https page I try to load shows:
>>
>>Peer's certificate has an invalid signature.
>>Error code: sec_error_bad_signature
>>
>> I can't even run mochitests that load https pages.
>
> Check y
On 11/20/12 1:31 PM, Mihai Sucan wrote:
Hello!
Any https page I try to load shows:
Peer's certificate has an invalid signature.
Error code: sec_error_bad_signature
I can't even run mochitests that load https pages.
Check you system's date + time? If it's living in 1912 or 2112 all the
Hello!
Any https page I try to load shows:
Peer's certificate has an invalid signature.
Error code: sec_error_bad_signature
I can't even run mochitests that load https pages.
Internet searches only point me to faulty certificates, to self-signed
certs, etc. The issue I am having seems sl
Following our discussion here and in the weekly platform team call, I've
gone ahead and altered the C++ style guide to note that we now prefer
'static' to anonymous namespaces (except for cases that can't be covered
by 'static').
https://developer.mozilla.org/en-US/docs/Developer_Guide/Coding_
On 20/11/12 00:41, Jonas Sicking wrote:
If this is indeed the case, maybe we should add something to the UA
string which indicates the screen size.
As well as being something no other browser does, that would increase
our fingerprintability.
Gerv
___
On 20/11/12 00:14, Jonas Sicking wrote:
If indeed we can't send the token on mobile devices (because it would
cause them to send us the somewhat-larger-screen-size tablet UI?) then
I agree with you. My proposal only makes sense if we can send the
"touch" token for mobile as well.
Or developers
On Tue, Nov 20, 2012 at 3:54 AM, Pelota
wrote:
> The real problem was using an old 17.0 Gecko SDK. With SDK 17.0b6 there is
> no problem.
>
> Thx for fast help, Kyle!
>
As Neil alludes to, this is actually our fault for changing the interfaces
during beta. We've undone that now. The released ve
Kyle Huey wrote:
The IID of nsIDOMHTMLInputElement changed from Gecko 16 to Gecko 17. You are
probably compiling against headers for Gecko 16.
How does bug 813264 affect this?
--
Warning: May contain traces of nuts.
___
dev-platform mailing list
d
On Mon, Nov 19, 2012 at 10:41 PM, Jonas Sicking wrote:
> On Tue, Nov 13, 2012 at 8:37 AM, wrote:
> > On Tuesday, November 13, 2012 2:49:14 AM UTC-8, Jonas Sicking wrote:
> >> Websites generally send dramatically different content for touch-based
> >> UIs. Different enough that they'd want to se
The real problem was using an old 17.0 Gecko SDK. With SDK 17.0b6 there is no
problem.
Thx for fast help, Kyle!
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
14 matches
Mail list logo
