Re: Misunderstood the Assigned at bugs! Sorry !!!

2014-07-09 Thread Chris Peterson
hi Tobias, Bugzilla has many fields and teams use them in many different ways. :) It's usually best to let the people reporting or investigating the bugs update the bug fields. From my experience, many (most?) teams never change a bug's Status from NEW to ASSIGNED, but they still use Assigned

Re: Unimplement: @-moz-document regexp support?

2014-07-09 Thread Frederik Braun
On 09.07.2014 01:41, Ehsan Akhgari wrote: On 2014-07-08, 6:34 PM, L. David Baron wrote: On Monday 2014-07-07 15:18 -0400, Ehsan Akhgari wrote: That seems pretty bad. I think we should at least stop supporting it for Web content. David, what do you think? I'm ok with restricting it to UA

Re: Rethinking the crash experience

2014-07-09 Thread David Rajchenbach-Teller
Interesting point. What's the profile of users who write comments on crash reports? Would they click on a button add comments? On 08/07/14 21:33, Honza Bambas wrote: This would probably eliminate most comments we get on crash reports. Even if a good number of those are not helpful now, a

Re: Misunderstood the Assigned at bugs! Sorry !!!

2014-07-09 Thread Ryan VanderMeulen
On 7/9/2014 2:47 AM, Chris Peterson wrote: Despite its name, the Target Milestone field is usually left unset until *after* the bug is fixed. Then Target Milestone is set to the version of Firefox Nightly that was fixed (e.g. Nightly 33 is mozilla33). Even if a bug fix is uplifted from Nightly

Re: Misunderstood the Assigned at bugs! Sorry !!!

2014-07-09 Thread Tobias B. Besemer
Am Mittwoch, 9. Juli 2014 03:51:32 UTC+2 schrieb Tobias B. Besemer: I tried to help and clean up a bit Bugzilla with updating the Target Milestone to a Milestone that get still developed ... I did this:

Re: Misunderstood the Assigned at bugs! Sorry !!!

2014-07-09 Thread Gijs Kruitbosch
On 09/07/2014 16:00, Tobias B. Besemer wrote: Am Mittwoch, 9. Juli 2014 03:51:32 UTC+2 schrieb Tobias B. Besemer: I tried to help and clean up a bit Bugzilla with updating the Target Milestone to a Milestone that get still developed ... I did this:

Re: Misunderstood the Assigned at bugs! Sorry !!!

2014-07-09 Thread Milan Sreckovic
What’s the purpose of the “ASSIGNED status? If we’re saying that this status can be computed from Assigned To field (being set to nobody or something else), then why do we still have it? If it isn’t equivalent, then we may be losing some information if we reset it back to New. -- - Milan On

Re: Misunderstood the Assigned at bugs! Sorry !!!

2014-07-09 Thread Gijs Kruitbosch
As glob noted upthread, the NEW/ASSIGNED distinction is sometimes used by people when they are the assignee. There is only a lack of difference when the assignee is nob...@mozilla.org. That doesn't warrant abolishing the status (although we could arguably ask bmo folks to make the reset the

Re: Improving Session Restore Experience (was Re: Reordering opened windows)

2014-07-09 Thread Philipp Sackl
Hey all, here’s an illustrative video of the last option that David mentioned. http://cl.ly/2E0q3W3Y2S3h Note in particular, that the restoring of the background windows is not animated. — Philipp On 07 Jul 2014, at 06:43, David Rajchenbach-Teller dtel...@mozilla.com wrote: (Cc-ing

Re: Rethinking the crash experience

2014-07-09 Thread Robert Kaiser
Most probably would not type a comment when they're not immediately prompted for it. We could do an experiment around it, but I'd be surprised if anything else comes out of it. I for myself probably wouldn't type a comment myself in 90% of the cases when that was required, and I know how

Re: Rethinking the crash experience

2014-07-09 Thread Benjamin Smedberg
On 7/9/2014 4:46 PM, Robert Kaiser wrote: Most probably would not type a comment when they're not immediately prompted for it. We could do an experiment around it, but I'd be surprised if anything else comes out of it. There's no reason to guess or use personal anecdotes for this. We'll do

Problems with the channels for FF TB

2014-07-09 Thread Tobias B. Besemer
Hi! I was interested to test the new TB 31 Beta ... ... I'm now using 24.6.0 ... ... so I installed the extension Update Channel Selector 1.6 and switched to beta ... When I now open the About I see that I be on beta, but TB says: Thunderbird is up to date (I think there is a point at the end

Re: Problems with the channels for FF TB

2014-07-09 Thread Kevin Brosnan
That is an unsupported way to use beta. Please use the download links below. http://www.mozilla.org/en-US/firefox/beta/all/ https://www.mozilla.org/en-US/thunderbird/all-beta.html On Jul 9, 2014 5:10 PM, Tobias B. Besemer tobias.bese...@googlemail.com wrote: Hi! I was interested to test the

How did mozbuild running XPCSHELL_TESTS_MANIFESTS

2014-07-09 Thread Yonggang Luo
In the moz.build files, there is specified XPCSHELL_TESTS_MANIFESTS, but I can not found where to processing this variable/files in mozbuild system. ___ dev-platform mailing list dev-platform@lists.mozilla.org

fopen, gtest and try

2014-07-09 Thread Anthony Jones
I've recently been using gtest for media code. However I've come across the issue of fopen() working locally but not on the try servers. https://tbpl.mozilla.org/?tree=Tryrev=11d9f94c54bd Any suggestions on how I should do this differently? Anthony

Re: How did mozbuild running XPCSHELL_TESTS_MANIFESTS

2014-07-09 Thread Gregory Szorc
On 7/9/14, 8:21 PM, Yonggang Luo wrote: In the moz.build files, there is specified XPCSHELL_TESTS_MANIFESTS, but I can not found where to processing this variable/files in mozbuild system. See the following:

Re: Intent to implement: Ability to surpress default contextmenu items

2014-07-09 Thread Jonas Sicking
On Sat, Jun 28, 2014 at 9:30 PM, Ian Hickson i...@hixie.ch wrote: On Sat, 28 Jun 2014, Dale Harvey wrote: Application developers have the ability to specify additional menuitems for contextmenus via

Re: Intent to implement: Ability to surpress default contextmenu items

2014-07-09 Thread Jonas Sicking
On Mon, Jun 30, 2014 at 5:26 AM, Wesley Hardman whardma...@gmail.com wrote: Suppressing the contextmenu is extremely user-hostile (for some users). There is a reason I always run with dom.event.contextmenu.enabled set to false. This option would continue to work and make us ignore the