1916462 - Enable tracer debugger sidebar by default

Status: RESOLVED FIXED

(DevTools :: Debugger, enhancement)

Description

[Alexandre Poirot [:ochameau] [PTO back August 21]]

The debugger sidebar is now much more useful than the web console output, so let's make it the default output for the JS Tracer.

Comment 1

[Alexandre Poirot [:ochameau] [PTO back August 21]]

Attachment: Bug 1916462 - [devtools] Enable tracer debugger sidebar by default.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d4177d855b3a
[devtools] Enable tracer debugger sidebar by default. r=devtools-reviewers,nchevobbe

Comment 3

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/d4177d855b3a

Comment 4

[Sebastian Zartner [:sebo]]

It looks like this is still not mentioned at https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features. So now it's a great point in time to add the Tracer Debugger there.

I saw this feature is already documented at https://firefox-source-docs.mozilla.org/devtools-user/javascript_tracer/index.html.
Though, as far as I understand, the Tracer Debugger itself didn't get enabled by default yet by this change, only the default logging method got changed from the Web Console to the Debugger sidebar, right?

Sebastian

Comment 5

[Alexandre Poirot [:ochameau] [PTO back August 21]]

(In reply to Sebastian Zartner [:sebo] from comment #4)

It looks like this is still not mentioned at https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features. So now it's a great point in time to add the Tracer Debugger there.

I wasn't aware of this page. Do you know how we typically contribute to this list?

I saw this feature is already documented at https://firefox-source-docs.mozilla.org/devtools-user/javascript_tracer/index.html.
Though, as far as I understand, the Tracer Debugger itself didn't get enabled by default yet by this change, only the default logging method got changed from the Web Console to the Debugger sidebar, right?

The main audience of this feature is platform and web compat engineers in order to figure out Web Compatibility issues.
It is not covered by tests, nor being translated, nor do we guarantee any backward compatiblity when debugging Fenix.
So, this isn't necessarily ready for public audience.