Re: dev-developer-tools Digest, Vol 63, Issue 6

[Musisi Tonneys]

ufijwefhow;c


On Mon, Feb 19, 2018 at 4:00 AM, <
dev-developer...@lists.mozilla.org> wrote:

> Send dev-developer-tools mailing list submissions to
> dev-devel...@lists.mozilla.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.mozilla.org/listinfo/dev-developer-tools
> or, via email, send a message with subject or body 'help' to
> dev-developer...@lists.mozilla.org
>
> You can reach the person managing the list at
> dev-develope...@lists.mozilla.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dev-developer-tools digest..."
>
>
> Today's Topics:
>
> 1. Re: Proposal to remove `console.exception` from the console
> spec (Harald Kirschner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 18 Feb 2018 15:03:21 +0000
> From: Harald Kirschner <har...@mozilla.com>
> To: Brian Grinstead <bgrin...@mozilla.com>
> Cc: dev-developer-tools <dev-devel...@lists.mozilla.org>,
> Michael Taylor <mi...@mozilla.com>
> Subject: Re: Proposal to remove `console.exception` from the console
> spec
> Message-ID:
> <CAPnv6M3eXAu4TbtsOMJV_MScSdds1m5UugSFPcfsf_mCsBQJZA@
> mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> [+miket for web compat input]
>
> Given the potential web compat issues and prior issues we recently found
> with synthetic errors; I?d like to get some more data to inform this. It
> might be ok as only Edge and FF have it, but lets get more data points.
>
> API calls are not instrumented by telemetry, other than few manual
> exceptions.
>
> As we have work lined up for improving console error formatting (usage of
> error objects and error logging methods); we could actually invest in
> adding a probe that can inform this using at least some Nightly data.
>
> /Harald
>
> On Sat, Feb 17, 2018 at 15:49 Brian Grinstead <bgrin...@mozilla.com>
> wrote:
>
> > There?s a discussion about removing `console.exception` from the
> > specification at
> > https://github.com/whatwg/console/issues/27#issuecomment-366326423. The
> > method was added in Bug 922214, and came over from Firebug?s console
> > implementation. Some points in favor of removing it:
> >
> > 1) It's basically just an alias for console.error (I can?t find any
> > difference in the implementation between the two methods).
> > 2) There are only a few hits within m-c for it (
> > https://searchfox.org/mozilla-central/search?q=console.exception&path=)
> > and would be easy to migrate to `console.error`.
> > 3) Chrome, Safari, and node haven?t ever implemented it, and it?s not
> > likely to get added to the spec unless if we advocate for it.
> >
> > I don't have a strong argument for keeping it in the spec, but the main
> > argument against removing our implementation would be web compat breakage
> > for sites currently using it. Given that only Firefox and Edge have
> > implemented it, I would expect it to generally be used alongside a
> polyfill.
> >
> > Feedback is welcome. Also, do we have existing telemetry data on web api
> > usage that would capture console methods? If we do and someone could
> point
> > me towards that it would be helpful.
> >
> > Thanks,
> > Brian
> >
> > _______________________________________________
> > dev-developer-tools mailing list
> > dev-devel...@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/dev-developer-tools
> >
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> dev-developer-tools mailing list
> dev-devel...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-developer-tools
>
>
> ------------------------------
>
> End of dev-developer-tools Digest, Vol 63, Issue 6
> **************************************************
>