STRs:

• open OBT, open console
• in the Console cog options, disable "Show Content Messages"
• close the OBT
• open OBT, open console

Expected Result: The setting should be persisted, "Show Content Messages" should be disabled
Actual Result: The setting is enabled again.

Note: this only applies to this setting. Timestamp and grouping options are correctly persisted across restarts.

Probably from this code that initializes the state of the console

showContentMessages: webConsoleUI.isBrowserConsole
        ? getBoolPref(PREFS.UI.CONTENT_MESSAGES)
        : true,

To be clear this should be updated to check webConsoleUI.isBrowserConsole || isBrowserToolbox (the catch is that we don't have a good isBrowserToolbox helper available I think)

Actually the console has webConsoleUI.isBrowserToolboxConsole which should be perfect here!

Nicolas, what do you think should be the default behavior of the Browser Toolbox Console? Should it show content messages by default or not?
Today, with the current code, the setting is always true on startup. If we change it to have the same logic as the Browser Console, then by default content messages will be hidden.

We can either:

• keep it disabled by default and update browser_toolbox_console_new_process.js to set the pref in the BT profile
• update the default value of devtools.browserconsole.contentMessages to be true (will then change the default behavior of the Browser Console)
• default it to true only for the Browser Toolbox Console (would be consistent with the current situation, but might be hard to justify)

I'd say let's keep it disabled to match the Browser Console logic.

sounds good, thanks!

https://hg.mozilla.org/mozilla-central/rev/45777f13e11a