On 11 October 2016 at 05:41, Nicholas Nethercote
wrote:
> On Tue, Oct 11, 2016 at 5:17 AM, Peter Bengtsson
> wrote:
> >
> > If indeed, the memory report is safe to always show I'll change the
> template
> > to always show the memory_report link (if applicable).
> >
> > Nicholas?
>
> Based on not
On Tuesday, 11 October 2016, L. David Baron wrote:
> But given that it is worthwhile to advance snapshots of stable
> features to Recommendation every so often, is there a reason to
> oppose this particular snapshot, even though it's not a suitable
> target for implementation?
It's not worthwhi
On 10/11/16 1:23 AM, L. David Baron wrote:
But given that it is worthwhile to advance snapshots of stable
features to Recommendation every so often, is there a reason to
oppose this particular snapshot, even though it's not a suitable
target for implementation?
I think the main reason I'm wary
On Tuesday 2016-10-11 07:07 +0200, Anne van Kesteren wrote:
> On Tuesday, 11 October 2016, L. David Baron wrote:
>
> > I'd note that Mozillians have been very involved in editing the
> > specification, but I'm not entirely sure of our level of involvement
> > in stabilizing the "release branch" t
On Tuesday, 11 October 2016, L. David Baron wrote:
> I'd note that Mozillians have been very involved in editing the
> specification, but I'm not entirely sure of our level of involvement
> in stabilizing the "release branch" to be a Level 1 recommendation.
We've been opposed towards putting re
On 10/10/16 11:57 AM, Jonathan Griffin wrote:
> We may implement these wireframes for non-sheriffs, or on a per-user basis,
> or only for Try.
Thinking in terms of "developers look at single pushes on try, sheriffs
look at multiple pushes on non-try" is wrong on all four counts. Many of
the develo
On Tue, Oct 11, 2016 at 5:17 AM, Peter Bengtsson wrote:
>
> If indeed, the memory report is safe to always show I'll change the template
> to always show the memory_report link (if applicable).
>
> Nicholas?
Based on nothing more than gut feeling, I'd prefer to keep it as PII.
Just feels like the
Yes, that's correct.
On Fri, Oct 7, 2016 at 11:09 PM, Ehsan Akhgari
wrote:
> Thanks Morris!
>
> As far as I know, no other engine has shipped this feature, is that
> correct?
>
> On 2016-10-07 3:34 AM, Morris Tseng wrote:
> > In bug 1172796, we shipped ImageBitmapRenderingContext accidentally. D
The W3C is proposing a new charter for:
Web of Things Working Group
https://lists.w3.org/Archives/Public/public-new-work/2016Sep/0005.html
https://www.w3.org/2016/09/wot-wg-charter.html
Mozilla has the opportunity to send comments or objections through
this Friday, October 14.
Please reply
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:
WebIDL Level 1
W3C TR draft: https://www.w3.org/TR/WebIDL-1/
W3C Editor's draft: https://heycam.github.io/webidl/
deadlin
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:
HTML 5.1
W3C TR draft: https://www.w3.org/TR/html/
W3C Editor's draft: https://w3c.github.io/html/
deadline: Thursday, Oc
On Friday, October 7, 2016 at 6:49:53 PM UTC+11, Gian-Carlo Pascutto wrote:
> Hi all,
>
> the next Nightly build will have a significantly tightened Linux
> sandbox. Writes are no longer allowed except to shared memory (for IPC),
> and to the system TMPDIR (and we're eventually going to get rid of
On Mon, Oct 10, 2016 at 06:24:33PM +0300, Henri Sivonen wrote:
> For benchmarking purposes, I'd like to call uconv from a Rust program.
> Since building uconv separately from Gecko hasn't really been
> maintained, I figured that I'd export a small number of C-linkage
> functions from libxul, dynami
TL;DR
- UI got more verbose, elements unnecessary hidden
- Too much vertical space used
- Passes and failures shouldn't be separated
- failure log becomes longer because of failure snippets
User persona
Developers:
- check the results of their own pushes to Try and own pushes to
official reposi
On Mon, Oct 10, 2016 at 2:07 PM, Andrew McCreight
wrote:
> In bug 1308652, I'm planning on removing about:bloat. It disables XPCOM
> leak tracking while it is running, so running it can cause false negative
> leaks (bug 1271182). I don't think anybody uses it much any more, so I'm
> going to remov
In bug 1308652, I'm planning on removing about:bloat. It disables XPCOM
leak tracking while it is running, so running it can cause false negative
leaks (bug 1271182). I don't think anybody uses it much any more, so I'm
going to remove it.
Andrew
___
dev-
On 10/10/16 2:57 PM, Jonathan Griffin wrote:
https://drive.google.com/file/d/0B3__-vbLGlRHajhEOE1SVXBQUU0/view?usp=sharing
Just to check, were these wireframes tested at window widths around
1000px or so? All the screenshots there are pretty wide, looks like.
Moving the commit info to above
TL;DR - we'd like some feedback on some UI changes to Treeherder
recommended by a 3rd party UX team.
The longer story - a 3rd party UX team has provided us with some
suggestions on how to improve Treeherder's UI from the perspective of the
average developer. They've created a set of wireframes her
On Mon, Oct 10, 2016 at 1:42 PM, Eric Rahm wrote:
> Is there a reason you need permissions for the memory report? Don't we
> anonymize it?
>
>
The link was made private when we thought it did contain possible PII.
Spoke to Ted about it.
He prefers to defer the fact finding to Nicholas.
If indeed
Is there a reason you need permissions for the memory report? Don't we
anonymize it?
-e
On Mon, Oct 10, 2016 at 8:34 AM, Benjamin Smedberg
wrote:
> Yes, downloading raw minidumps and memory reports requires the PII
> permission in crash-stats. This can be obtained by Mozilla employees with
> th
It does. You need to file a bug like
https://bugzilla.mozilla.org/show_bug.cgi?id=1118990
Kevin Brosnan
On Mon, Oct 10, 2016 at 8:23 AM, Ben Kelly wrote:
> Does the "raw dump" tab support require special permissions? I don't see
> any way to download the memory report from:
>
> https://crash-s
Yes, downloading raw minidumps and memory reports requires the PII
permission in crash-stats. This can be obtained by Mozilla employees with
the assent of your manager, although I'm not sure now what the correct
bugzilla component is.
--BDS
On Mon, Oct 10, 2016 at 6:23 PM, Ben Kelly wrote:
> Do
For benchmarking purposes, I'd like to call uconv from a Rust program.
Since building uconv separately from Gecko hasn't really been
maintained, I figured that I'd export a small number of C-linkage
functions from libxul, dynamically link with libxul as built as part
of Linux x86_64 Firefox and cal
Does the "raw dump" tab support require special permissions? I don't see
any way to download the memory report from:
https://crash-stats.mozilla.com/report/index/1a572047-ac64-4add-a82f-a31512161004#tab-rawdump
On Sun, Oct 9, 2016 at 7:51 PM, Nicholas Nethercote
wrote:
> Greetings,
>
> crash-s
Hi everyone,
Here's the list of new issues found and filed by the Desktop Release QA
Team last week, *October 3**- October 7* (week 40).
Additional details on the team's priorities last week, as well as the
plans for the current week are available at:
https://public.etherpad-mozilla.org/
25 matches
Mail list logo
