[Firefox Desktop] Issues found: December 4th to January 8th

Hi everyone, Here's the list of new issues found and filed by the Desktop Manual QA team last week, January 4 - January 8 (Week 1). 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/p/Des

Changes to the firefoxtree hg extension

I spent some time confronted to this last week, so for firefoxtree extension users out there, this might be useful too. The way the mercurial firefoxtree [1] extension maintains repository labels (like "fx-team", "inbound", "central", "aurora", etc.) has changed recently (not sure when this happen

Re: "-Moz-Element" -like API by extending WEBGL_dynamic_texture

On Thu, Jan 7, 2016 at 10:32 AM, Robert O'Callahan wrote: > Some of the things that would need to be handled: > -- controls need to not expose sensitive data about file > paths No great ideas here other than simply not rendering them. > -- For SVG images we disable native themes to avoid those

Re: nsIProtocolHandler in Electrolysis?

On 05/01/2016 10:50, Kris Maglione wrote: > On Mon, Jan 04, 2016 at 06:29:26PM -0800, Kris Maglione wrote: >> I think that doing this in an add-on is asking for trouble. I don't >> think I've ever seen nsIChannel implemented in JavaScript. > > I take that back. I see Overbite is indeed implemente

any concerns with dropping the talos test v8 and using AWFY Octane instead?

Currently we run a very outdated version of V8 (version 7) in Talos. This has since been replaced with Octane in the world of benchmarks. AWFY (arewefastyet.com), has been running Octane and catching regressions faster than Talos. There is missing coverage in AWFY, specifically e10s, pgo, aur

Re: any concerns with dropping the talos test v8 and using AWFY Octane instead?

On Mon, Jan 11, 2016 at 3:08 PM, wrote: > Currently we run a very outdated version of V8 (version 7) in Talos. This > has since been replaced with Octane in the world of benchmarks. > > AWFY (arewefastyet.com), has been running Octane and catching regressions > faster than Talos. There is missi

Re: Changes to the firefoxtree hg extension

Thanks for sharing this, I've seen a few people asking about it. Note, as of bug 1234927 the `wip` alias that |mach mercurial-setup| provides you has been fixed. But if you already had a pre-existing `wip` alias, you'll have to update it manually like Patrick mentions. -Andrew On 11/01/16 06:00

mozregression – Engineering Productivity Project of the Month

Hello from Engineering Productivity! Once a month we highlight one of our projects to help the Mozilla community discover a useful tool or an interesting contribution opportunity. This month’s project is mozregression! mozregression helps to find regressions in Mozilla projects like Firefox or Fi

Re: bug number for iframe scrollbars displayed with overflow:hidden (repost)

many thanks "Boris Zbarsky" wrote in message news:j5idnt0r6-ok7w_lnz2dnuu7-l-dn...@mozilla.org... On 1/10/16 6:53 AM, rvj wrote: This obvious bug seems to have occurred after release 28 ..I presume its registered as the regression must be at least a year, possibly two years old This wa

Re: about:profiles and the new profile manager

On Sunday, December 27, 2015 at 2:33:44 PM UTC-5, Mark Finkle wrote: > As work on this feature continues, I think we want to block the code and UI > from shipping in Firefox for Android. Can you look into ways to stop the > toolkit code, strings and UI from getting packaged for Android? > > On Fri

Re: The warning about the Java Deployment Toolkit should be removed.

On Friday, July 18, 2014 at 3:31:53 PM UTC-5, Gavin Sharp wrote: > > ... > > With click to play on by default we could probably remove the broad > block, but we'd want to still block the known-vulnerable versions, > which would require coming up with a regexp that matches only the > right version

Re: bug number for iframe scrollbars displayed with overflow:hidden (repost)

... although I have to say it does seem like a bad regression! It seems that it is now necessary to frig the root node of any HTML and XML documents loaded via an iframe (viewport) and apply a bit of js to test for and insert a style attribute containing overflow:hidden ... ... and

Re: bug number for iframe scrollbars displayed with overflow:hidden (repost)

On 1/11/16 10:49 AM, rvj wrote: It seems that it is now necessary to frig the root node of any HTML and XML documents loaded via an iframe (viewport) and apply a bit of js to test for and insert a style attribute containing overflow:hidden ... Or just use the "scrolling" attribute on t

Re: any concerns with dropping the talos test v8 and using AWFY Octane instead?

On 2016-01-11 9:08 AM, jma...@mozilla.com wrote: Currently we run a very outdated version of V8 (version 7) in Talos. This has since been replaced with Octane in the world of benchmarks. AWFY (arewefastyet.com), has been running Octane and catching regressions faster than Talos. There is mis

Re: about:profiles and the new profile manager

Hey all, I filed this last week, but didn't assign it. I've been unable to > open nightly at all since the new profile manager launched. > > Hi John, I asked your a question on bugzilla. Can you take a look? Thanks. If you prefer we can talk on IRC. My nick name is 'baku'. bye b ___

Re: bug number for iframe scrollbars displayed with overflow:hidden (repost)

I dont think so... but not sure ! Bascially I want display iframes suitable for touch screen usage so it must a) never show document window scrollbars and perhaps also supress document content iframe scrollbars b) but allows the user to "flick" scroll the document content in and out of

Re: Dynamic Logging

> On Jan 8, 2016, at 5:50 PM, Mike Hommey wrote: > > On Fri, Jan 08, 2016 at 05:32:48PM -0800, Eric Rahm wrote: >> Hi Folks- >> >> With bug 1233881 we >> landed the ability turn on logging via prefs. >> >> Lets say you have a log module "F

Re: Dynamic Logging

By default we use |printf_stderr|, which prints to stderr (or logcat on android/b2g). I presume we grab that in the test logs, but maybe I'm mistaken? -e On Fri, Jan 8, 2016 at 6:32 PM, Bobby Holley wrote: > This is incredible - thank you for pushing this through Eric! > > In case the implicati

Re: Dynamic Logging

Yes, printf_stderr is generally the most sure-fire way to get something in the log IME. Sounds great! On Mon, Jan 11, 2016 at 11:02 AM, Eric Rahm wrote: > By default we use |printf_stderr|, which prints to stderr (or logcat on > android/b2g). I presume we grab that in the test logs, but maybe I'

Re: mozregression – Engineering Productivity Project of the Month

I wanted to chime-in and emphasis this: One of the first thing you do when looking at a bug is establish if it's a regression and starting with mozregression right away if it is! From my experience running mozregression for easily reproduced regressions can be done in about 10 minutes and it real

Re: mozregression – Engineering Productivity Project of the Month

I also just want to give Julien a shout out for the fantastic work he's been doing to make the tool both more versatile and also more user-friendly. If you haven't used it in awhile, give it a look! -Ryan On Mon, Jan 11, 2016 at 2:46 PM, Benoit Girard wrote: > I wanted to chime-in and emphasis

Re: C++ Core Guidelines

Henri Sivonen wrote: > On Wed, Jan 6, 2016 at 9:27 PM, Brian Smith wrote: > > Henri Sivonen wrote: > >> > >> On Thu, Oct 1, 2015 at 9:58 PM, Jonathan Watt wrote: > >> > For those who are interested in this, there's a bug to consider > >> > integrating > >> > the Guidelines Support Library (GSL

Re: any concerns with dropping the talos test v8 and using AWFY Octane instead?

On Monday, January 11, 2016 at 8:42:11 AM UTC-8, William Lachance wrote: > It seems like another alternative might be to run Octane in Talos, > instead of v8_7. > > It seems like Talos has two advantages over AWFY (correct me if I'm wrong): > > 1. Easy for developers to schedule jobs via try (ma