Re: Intent to implement and ship: Limit the length of Referer header to 4k

On Tue, Jul 2, 2019 at 6:16 AM Thomas Nguyen wrote: > DevTools bug: No > Wouldn't it be helpful to indicate such truncation in the console (as a warning) or network panel (with a request badge)? I can imagine developers being confused about why the referrer header is not what they expect it to

Performance profiling improvements #3

Hello folks! It has been another 3 months since our last update on the Firefox Profiler. During this time the Performance Tools team and our brilliant contributors have made many improvements that should make using the tool a more delightful experience. Here are the highlights: # New Categorized

Re: PSA: mercurial-setup becomes vcs-setup and adds support for git

; > On Fri, Aug 17, 2018 at 3:51 AM Panos Astithas wrote: > >> Hi all, >> >> since bug 1257478 landed in m-c earlier today, you should now be using >> 'mach vcs-setup' instead of 'mach mercurial-setup'. Nothing else changes in >> your workflow

PSA: mercurial-setup becomes vcs-setup and adds support for git

Hi all, since bug 1257478 landed in m-c earlier today, you should now be using 'mach vcs-setup' instead of 'mach mercurial-setup'. Nothing else changes in your workflow (e.g. 'mach mercurial-setup -u' becomes 'mach vcs-setup -u') and the spell checker will suggest vcs-setup if you try to use mercu

Performance profiling improvements #2

Hello there! It has been almost 3 months since our last update on the Firefox Profiler. In that time the Performance Tools team and our awesome contributors have made numerous improvements that will hopefully make your jobs easier, for all of you trying to make Firefox fast, for good. Here are th

Re: Proposed W3C Charter: Web Performance Working Group

On Wed, Jul 11, 2018 at 4:52 PM Tom Ritter wrote: > Device Memory clearly has made an effort to make it 'less fingerprintable' > by only reporting possible values of 0.25, 0.5, 1, 2, 4, 8 - but there is > nothing in the spec about omitting it if desired to reduce fingerprinting. > This is a spec

Re: Proposed W3C Charter: Web Performance Working Group

Thanks everybody for the comments submitted so far on the WG rechartering process, please keep them coming! I would like to make two requests, if I may: - feedback on specs and not on the recharter should be submitted to the GitHub issue tracker for the spec (ping me if you can't find it) - if you

Performance profiling improvements

Hello! As we continue our relentless focus on improving Firefox performance, I would like to call your attention to some related improvements in our tools that occurred over the last few months. First of all, the performance tools team and the automation team worked together to make perf.html

Re: Intent to require `mach try` for submitting to Try

On Tue, Sep 19, 2017 at 7:20 PM, Andrew McCreight wrote: > I've been using git for years now to develop Firefox, and I feel like it is > a first class experience. There's a one time cost to setting up cinnabar, > but after that, everything just works, including |mach try| and |mach > mozreview|.

Re: Firefox 55.* in Windows/Ubuntu - every day CPU 100%/Hangs Up. Please to do something!

Hi, if you could file a bug, we can try to figure this out: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Untriaged Please attach the contents of about:support as an attachment, so we can get some idea of your configuration. Thanks, Panos On Wed, Sep 6, 2017 at 10:45 AM

Re: Stylesheet wait timeout?

On Fri, Sep 1, 2017 at 7:37 PM, Boris Zbarsky wrote: > I reported this issue to them (copy/paste of my report below) through the > form at https://ghostery.zendesk.com/hc/en-us/requests/new but if someone > has better contact info that might be nice. > I have forwarded your message to my contact

Re: Have you run 'mach bootstrap' lately?

I had filed bug 1257478 specifically for tackling the git configuration issue and when this larger plan was brought up, my inclination to work on it diminished :) If this broader work is not prioritized, could we split it into smaller bugs so that it's manageable in weekend-sized chunks? I realize

Re: Startup JS debugging (sometimes) possible via Browser Toolbox

You almost completely resolved the 4-year-old bug 814298, yay! I now wonder if this makes it easier to improve mochitest debugging per bug 929535. On Wed, Mar 8, 2017 at 9:22 PM, Kris Maglione wrote: > On Wed, Mar 08, 2017 at 01:09:10PM -0600, J. Ryan Stinnett wrote: > >> With bug 1275942 in Fir

Re: Converting assertions into release assertions

On Thu, Sep 22, 2016 at 6:07 PM, Ehsan Akhgari wrote: > On 2016-09-22 9:07 AM, Gijs Kruitbosch wrote: > > On 22/09/2016 05:28, Nicholas Nethercote wrote: > >> Greetings, > >> > >> Assertions, such as MOZ_ASSERT, are great. But they only run in debug > >> builds. > >> > >> Release assertions, such

Re: MXR permanently offline, please transition to DXR

It seems like the awesomebar could at least help you by boosting the frecency weight of the new URL compared to the old one, so it can gradually (or even not so gradually) be replaced. We are going to fix this in bug 737836. Panos On Fri, Jul 1, 2016 at 3:58 AM, Justin Dolske wrote: > This rem

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

On Fri, Jun 3, 2016 at 8:21 PM, Nick Fitzgerald wrote: > On Fri, Jun 3, 2016 at 8:41 AM, Boris Zbarsky wrote: > > > Devtools bug: none so far, but maybe we need one? Does devtools rely on > > the JSClass name or Object.prototype.toString anywhere? > > > > ​I think we are fine. There are certain

Re: Intent to ship: Treat cookies set over non-secure HTTP as session cookies

On Fri, Apr 15, 2016 at 5:47 PM, Tantek Çelik wrote: > However, As EKR pointed out, Kyle Huey's > > > Why should we be the ones to take the web compat hit on this? > > is the fundamentally biggest issue. > I realize I'm late to this thread and the discussion has moved the original proposal towar

Re: How to change the default profile in the profile manager?

On Thu, Mar 24, 2016 at 4:53 PM, Tobias B. Besemer < tobias.bese...@googlemail.com> wrote: > Hi! > > I resorted/renamed my profile folders... > Now, when I start the Developer Edition with the profile manager, FF > creates a new entry with "dev-edition-default" and the according folders in > \Roam

Re: Intent to implement: CSS Mask Image properties

On Tue, Nov 10, 2015 at 9:09 AM, Ku(顧思捷)CJ wrote: > *Summary*: > Intend to implement CSS mask. By using this it, you can apply a mask to a > graphical object, so that the graphical object will be painted onto the > background through a mask, thus completely or partially masking out parts > of the

Re: How would you like to spell check this?

On Thu, Sep 3, 2015 at 1:44 PM, Florian Quèze wrote: > On Sun, Aug 30, 2015 at 10:17 PM, Jörg Knobloch wrote: > > > So please voice your objections to the proposed solution, if any ;-) > > As someone mentioned already, lots of websites are actually > communication tools (eg. webmail, chat, socia

Re: Intent to Implement: Selection Events

On Tue, Aug 18, 2015 at 6:21 PM, Michael Layzell wrote: > Summary: We currently require webpages to poll the current selection when > they want to be > notified of changes to the user's selection.This patch adds two events, > selectstart and > selectionchange, which allow the website to detect wh

Re: Intent to implement: Moving DevTools to top level /devtools directory

On Thu, Jul 23, 2015 at 8:25 AM, Paul Rouget wrote: > On Wed, Jul 22, 2015 at 2:48 PM, Panos Astithas wrote: > > If you are thinking about shipping them as part of browser.html, we still > > have XUL dependencies that we need to get rid of first and that work is > > indepe

Re: Intent to implement: Moving DevTools to top level /devtools directory

If you are thinking about shipping them as part of browser.html, we still have XUL dependencies that we need to get rid of first and that work is independent from moving the code to a top-level devtools/ directory. On Wed, Jul 22, 2015 at 1:48 PM, Paul Rouget wrote: > Does that include getting r

Re: Changing the style guide's preference for loose over strict equality checks in non-test code

On Thu, May 14, 2015 at 11:22 PM, Gijs Kruitbosch wrote: > My point is there will be just as many "unexpected" issues when you use > "===" on opaque variables, because you didn't expect that that code in that > other file set this thing to null instead of deleting the property (causing > it to no

Re: mochitest-chrome tests now running on B2G emulators

On Tue, Mar 24, 2015 at 6:40 PM, Jonathan Griffin wrote: > Most (or all) of the tests in that directory were not working on B2G as > written. They were timing out and causing the harness to abort. So I > disabled that entire directory in the interests of getting the job running. > > I haven't

Re: mochitest-chrome tests now running on B2G emulators

This is very cool, I've been waiting for this for a long time! I see that existing tests are now skipped by default on b2g, e.g.: https://dxr.mozilla.org/mozilla-central/source/toolkit/devtools/server/tests/mochitest/chrome.ini#2 Is this because nobody has tested whether they work yet, or is it

Re: Is it time for mochitest-chrome on Android and B2G

Support for mochitest-chrome on mobile is sorely needed in devtools. It would increase our test coverage there by at least an order of magnitude. Panos On Wed, Jun 18, 2014 at 2:48 AM, Bobby Holley wrote: > I can't comment on the importance of the a-team's other priorities, or the > importance

Re: Web Replay

On Wed, Jan 15, 2014 at 10:24 AM, Dirkjan Ochtman wrote: > This may be a stupid question, but I just saw this on the webkit > mailing list: a way to capture network/user input events (with > "negligible" overhead) for debugging purposes. > > https://lists.webkit.org/pipermail/webkit-dev/2014-Janua

Re: Should we disable "autoplay" feature of HTMLMediaElement on mobile?

On Mon, Dec 9, 2013 at 4:48 PM, Gervase Markham wrote: > On 08/12/13 12:28, Tetsuharu OHZEKI wrote: > > On today's web, there are many "interactive" web sites which play > > sounds when open them. > > I suspect this is somewhat dependent on your culture and environment; > it's not a problem on th

Re: Intent to replace Promise.jsm and promise.js with DOM Promises

On Thu, Nov 21, 2013 at 9:00 PM, Paolo Amadini wrote: > Though it may seem counter-intuitive, the non-native Promise.jsm has > grown better error reporting and debuggability, and maybe even better > performance (depending on whether DOM Promises are optimized for not > returning to the outer OS ev