I think the you can get around the issue by setting the
security.sandbox.content.level pref to 0 while you're debugging.

On 23 May 2017 at 08:32, Shih-Chiang Chien <sch...@mozilla.com> wrote:

> Which platform you're using? For windows it seems to be solved by
> https://bugzilla.mozilla.org/show_bug.cgi?id=1320458, however other
> platforms are not fixed yet.
>
>
> Best Regards,
> Shih-Chiang Chien
> Mozilla Taiwan
>
> On Tue, May 23, 2017 at 11:59 AM, Chris Pearce <cpea...@mozilla.com>
> wrote:
>
> > On Sunday, November 27, 2016 at 5:59:27 AM UTC+13, Valentin Gosu wrote:
> > > Hi everyone,
> > >
> > > (I meant to send this mail a few weeks ago but forgot it in my Drafts
> > > folder.)
> > >
> > > With the landing of Bug 1303762 (Firefox 52), we now have a way for
> users
> > > to enable logging without restarting the browser, and without having to
> > > know what an environment variable is.
> > >
> > > We've added a new Logging section to about:networking. When a user
> > > encounters a bug, all they have to do is open that page, click on
> "Start
> > > Logging", reproduce the bug, then click on "Stop Logging" and upload
> the
> > > logs. The buttons will be disabled if the MOZ_LOG_FILE or MOZ_LOG env
> > > variables have been defined.
> > > The log modules are automatically set to the most common networking
> > > modules, but you may instruct the bug reporters to change them - just
> > tell
> > > them the string.
> > >
> > > This is very useful for bugs that are harder to reproduce once you
> > restart
> > > the browser.
> > >
> > > There are a bunch of improvements that we could make to the UI, so
> please
> > > feel free to send me your feedback and patches. Many thanks to Honza
> > > Bambas, Eric Rahm, Jared Wein, Patrick McManus and all others that
> helped
> > > with the implementation and review of this bug and its dependencies.
> > >
> > > https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/
> > HTTP_logging?document_saved=true#Using_aboutnetworking
> >
> > This seems super handy, but I tried it out and it seems to only affect
> the
> > parent process, and not the sub-processes of Firefox?
> >
> > _______________________________________________
> > dev-platform mailing list
> > dev-platform@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/dev-platform
> >
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to