Re: MXR permanently offline, please transition to DXR

Ms2ger wrote: > On 22/06/16 20:30, Lawrence Mandel wrote: >> Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was >> taken offline on June 13, 2016, to investigate a potential security issue. >> After careful review of the codebase, we have decided to accelerate the >>

Re: MXR permanently offline, please transition to DXR

On 6/23/16 5:49 AM, Ms2ger wrote: On 22/06/16 20:30, Lawrence Mandel wrote: Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was taken offline on June 13, 2016, to investigate a potential security issue. After careful review of the codebase, we have decided to accelerate

Heads up on awesome change to socorro that will change crash stats...

The authors of the fix can explain in details what is going on, but since the users will experience (great, but new) results with currently processed crash reports, it was suggested I should mention it to a larger audience. https://bugzilla.mozilla.org/show_bug.cgi?id=1274345

Re: Why do we still need to include Qt widget in mozilla-central?

I'm going to resurrect this old thread to ask: is anybody currently triaging bugs the Core: Widget: Qt bugzilla component? I'm trying to find owners for all of our active bugzilla components, and I'm not sure the status of this. I would support us removing the widget/qt code from the tree unless

Fwd: [TCW] Scheduled Tree Closing Maintenance Window 2016-06-25 06:00hrs PDT (1.5 Hours)

NOTE: we do not expect any significant disruption from this activity, but a few jobs may burn. Developers are responsible for sheriffing their own jobs, and re-triggering as needed. Thanks! -- Forwarded message -- From: Date: Thu, Jun 23, 2016 at 11:09 AM

Re: MXR permanently offline, please transition to DXR

On 06/23/2016 03:49 PM, Ms2ger wrote: On 22/06/16 20:30, Lawrence Mandel wrote: Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was taken offline on June 13, 2016, to investigate a potential security issue. After careful review of the codebase, we have decided to

Re: PSA: Removing the Pointerlock permission UI

Yay! Thank you :-) --Jet On Thursday, June 23, 2016, Dale Harvey wrote: > In https://bugzilla.mozilla.org/show_bug.cgi?id=1273351 I am working on > removing the pointerlock permissions UI, now instead of a doorhanger > permission that the user needs to respond to before

Re: MXR permanently offline, please transition to DXR

On 22/06/16 20:30, Lawrence Mandel wrote: > Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was > taken offline on June 13, 2016, to investigate a potential security issue. > After careful review of the codebase, we have decided to accelerate the > planned transition from

Re: Notes about implementing DOM APIs in Rust

On 22/06/16 19:05, Henri Sivonen wrote: > We shouldn't expect to be able to use Servo's implementations of DOM > APIs in a drop-in a manner in Gecko. Because Servo allocates Rust > objects on the JavaScript heap, but Gecko doesn't allocate C++ objects > on the JavaScript heap, For the record,

PSA: Removing the Pointerlock permission UI

In https://bugzilla.mozilla.org/show_bug.cgi?id=1273351 I am working on removing the pointerlock permissions UI, now instead of a doorhanger permission that the user needs to respond to before entering pointerlock, the pointer lock will be granted with a warning given to the user explaining how to

Re: Proposed W3C Charter: Web of Things Interest Group

On Thu, Jun 23, 2016 at 3:19 AM, Anne van Kesteren wrote: > We should just let them do their thing and do our thing elsewhere. This seems like a reasonable plan. Unless and until someone thinks that a course correction is feasible, or decides that it's worth trying.

Re: Notes about implementing DOM APIs in Rust

On Jun 23, 2016 1:33 AM, "Andrew McCreight" wrote: > > On Wed, Jun 22, 2016 at 1:05 PM, Henri Sivonen wrote: > > > Now that I'm looking at the hand-written notes that I made in the > > meeting, I notice that the above paragraph fails to say how the >