Intent to implement and ship: Changing the toString result on DOM prototype objects

Summary: The current IDL spec says that Object.prototype.toString() on a DOM prototype object for interface Foo is "[object FooPrototype]", whereas for instances of the interface it's "[object Foo]", and that's what we implement. However, as we try to move to the ES6 @@toStringTag world, this

Re: Top crash list is odd right now

Is the plan to prompt on release as well? On Fri, Jun 3, 2016 at 11:33 AM, Andrew McCreight wrote: > blassey landed a patch to suggest that users submit unsubmitted crash > reports. This is going to make various kinds of crashes, like shutdown > crashes, grossly

Re: 32-bit developer edition?

On 2016-06-03 8:51 AM, Ben Kelly wrote: In any case, we're not showing a 64-bit link anywhere now. Who should I pester or where should I file a bug to get that fixed? Mozilla.org :: webdev - mhoye ___ dev-platform mailing list

Intent to implement: a list of domains to auto-disable plugins

Summary: plugins, especially Flash, are still a major attack vector for malware authors. We intend to create a list of domains which are commonly loaded in a 3rd-party context and which therefore present a higher than normal risk of malware attacks. Sites on this list would be automatically

Re: 32-bit developer edition?

+Clarkbw, who runs Dev Edition. Expansion of 64 bit was on hold pending the release of 47, where we had some critical sandboxing issues fixed and (conveniently) the Widevine CDM also hit that timeframe for video support. It’s an interesting idea to hit developers, who are a bit savvier. We

Top crash list is odd right now

blassey landed a patch to suggest that users submit unsubmitted crash reports. This is going to make various kinds of crashes, like shutdown crashes, grossly overrepresented in the crash-stats "Top Crashers" list. You probably want to use "By build date" instead of the default "By report date" for

Re: All about crashes

On Fri, Jun 3, 2016 at 6:57 AM, Ted Mielczarek wrote: > BugHunter[1] attempts to reproduce crashes from crash-stats by loading > the URLs from the crash reports, which is sometimes successful. > Of note, BugHunter also uses both debug and AddressSanitizer builds, which

Re: Top crash list is odd right now

I reviewed the patch. Currently, the feature is only enabled on Nightly, Aurora and Beta. We originally wanted the beta unsubmitted crashes due to the content process crashes we were getting there with e10s that we didn't understand. Now that we have a better handle on those content process

Re: Documentation on how to read crash reports

On Thu, May 26, 2016, at 09:52 AM, Benjamin Smedberg wrote: > https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_a_minidump I spent some time today cleaning this page up a bit. I streamlined the Windows section (since you no longer need to manually download the matching binaries

Re: Documentation on how to read crash reports

On Thu, May 26, 2016, at 02:41 PM, Benoit Girard wrote: > - Crash address can give you a hint as to what's going on: 0x0 -> null > crash, 0x8 -> null offset accessing a member like this->mFoo, N.B.: due to the way addressing works on x86-64, if the crash address is "0x0" for a Linux/OS X crash

W3C Proposed Recommendation: Subresource Integrity (SRI)

A W3C Proposed Recommendation is available for the membership of W3C (including Mozilla) to vote on, before it proceeds to the final stage of being a W3C Recomendation: Subresource Integrity https://www.w3.org/TR/SRI/ deadline: Tuesday, June 7, 2016 Given Mozilla's involvement in

Proposed W3C Charter: Web Performance Working Group

The W3C is proposing a revised charter for: Web Performance Working Group https://w3c.github.io/charter-webperf/ https://lists.w3.org/Archives/Public/public-new-work/2016Jun/0001.html Mozilla has the opportunity to send comments or objections through Thursday, June 30. Please reply to

Re: Intent to implement and ship: Changing the toString result on DOM prototype objects

On 06/03/2016 06:41 PM, Boris Zbarsky wrote: Summary: The current IDL spec says that Object.prototype.toString() on a DOM prototype object for interface Foo is "[object FooPrototype]", whereas for instances of the interface it's "[object Foo]", and that's what we implement. However, as we try

Re: 32-bit developer edition?

We should offer both. --Jet On Thursday, June 2, 2016, Ben Kelly wrote: > Hi all, > > I noticed recently that all of the available download links for dev edition > point to the 32-bit installer. Is there a reason for this? > > Given we are talking about how to upgrade

Re: All about crashes

On Tue, May 24, 2016, at 04:58 PM, Lawrence Mandel wrote: > "Improve ranking of crash clusters." > > I think this is weighting or estimating impact of a crash instead of > volume > of submissions, which is how we have historically processed the clusters. > Severity is one component with startup

Re: All about crashes

I think that the ADI data comes from the blocklist ping which includes OS version (possibly Windows service pack as well). Robert On Fri, Jun 3, 2016 at 7:02 AM, Ted Mielczarek wrote: > On Tue, May 24, 2016, at 04:58 PM, Lawrence Mandel wrote: > > "Improve ranking of crash

Re: All about crashes

On Jun 3, 2016, at 8:53 AM, Ted Mielczarek wrote: > On Wed, May 25, 2016, at 10:27 PM, Eric Rescorla wrote: >> - Making it so that certain kinds of defects still happen but they are >> safer. >> For instance, in C writing dereferencing past the end of an array is >>

Re: 32-bit developer edition?

+ Javaun who should be able to fill in details about timing and what we want to do with Win64 and why On Fri, Jun 3, 2016 at 8:51 AM, Ben Kelly wrote: > On Jun 3, 2016 2:15 AM, "Jet Villegas" wrote: > > > > We should offer both. > > If we get a net

Re: All about crashes

On Wed, May 25, 2016, at 10:27 PM, Eric Rescorla wrote: > - Making it so that certain kinds of defects still happen but they are > safer. > For instance, in C writing dereferencing past the end of an array is > undefined behavior and may well cause something horrible, in Python > you get an

Re: All about crashes

On Wed, May 25, 2016, at 01:47 AM, Eric Rahm wrote: > Details on using rr to debug crashes would certainly be nice. In my experience, if a crash is reproducible it's generally straightforward to fix. rr could be useful if a crash is hard to reproduce or intermittent, but once a developer can

Re: 32-bit developer edition?

On Jun 3, 2016 2:15 AM, "Jet Villegas" wrote: > > We should offer both. If we get a net reduction in OOMs with 64-bit it seems to me we should make that the default download link. In any case, we're not showing a 64-bit link anywhere now. Who should I pester or where