Skip to content

Latest commit

 

History

History
117 lines (78 loc) · 9.81 KB

settings.md

File metadata and controls

117 lines (78 loc) · 9.81 KB
title Settings
description Pick the panel theme, hide, pin and reorder tabs, set up the popup button (passive mode and the counts launcher), save filters, resize panes, and turn the browser agent tools on or off.
Your own preferences for the panel (theme, tab bar and the popup on your app's page), and the dev server's browser agent tools switch.

Settings

Open Settings with the gear button in the panel header, or with Open settings in the command palette. Press the gear button again to go back to the tab you had open. The page is also at #tab=settings.

Where settings are saved

Settings belong to you, not to the project. The panel saves them in the browser's localStorage, so every panel on the same address uses them, and they survive reloads. The Chrome extension and the panel on your dev server have different addresses, so each keeps its own.

Key Holds
pangular-pref:theme light or dark. Missing means System.
pangular-pref:tabs The order, hidden tabs and pinned tabs.
pangular-pref:passive true when passive mode is on.
pangular-pref:pill true when the counts launcher is on.
pangular-pref:filters:<view> The saved filters of one view.
pangular-pref:pane:<view> The width a splitter left a pane at.

If the browser blocks storage, the settings apply until the panel reloads. Remove the keys to go back to the defaults.

Browser agents is the exception. The dev server keeps it, not the browser, so it applies to every page and panel connected to that server.

Theme

Choice The panel
System Follows the hub, the Chrome DevTools theme in the extension, or your system color scheme. This is the default.
Light Stays light.
Dark Stays dark.

The popup frame on your app's page follows the panel's theme. The command palette has the same three choices.

Tabs

The Tabs list shows every tab the panel can show, in tab bar order.

Control What it does
Pin Moves the tab to the start of the tab bar, with the other pinned tabs. A pinned tab is always shown.
Shown Clear it to hide the tab from the tab bar. A hidden tab stays reachable from the command palette and from links. Hiding unpins it.
Up and down arrows Move the tab one place. Pinned tabs move among the pinned ones, the others among the others.
Reset tabs Back to the default order, with every tab shown and none pinned.

Each row works with the keyboard: Tab reaches its buttons, and Alt+↑ or Alt+↓ on any control in the row moves the tab. After a move, focus stays on the row and a screen reader hears the new position, such as Signals moved to position 2 of 11. Dragging is not needed.

The tab you have open stays in the tab bar while it is open, even when it is hidden. Turning an inspector off in the configuration removes its tab whatever the settings say.

Passive mode

Passive mode hides the floating button on your app's page until you press the popup shortcut, Alt+Shift+P unless popup.hotkey sets another one. The button shows while the panel is open and hides again when it closes.

The popup saves passive mode with its layout, under pangular-popup in your app's localStorage, so it stays on after a reload. Turn it on or off from the panel in the popup: the panel sends the change to the popup around it, and the button hides as soon as you close the panel. A panel opened elsewhere, such as the Chrome extension, saves the setting but has no popup to change.

With popup.hotkey: false there is no shortcut to bring the button back, so passive mode is off and the checkbox is disabled.

Counts launcher

Counts launcher turns the floating button on your app's page into a small pill that shows two counts while the panel is closed:

Count What it counts
renders Component template updates since the page loaded, as Angular's profiler reports them. The count pauses while the tab is in the background.
errors Errors the Errors inspector caught on the page, each repeat included. It stays at 0 when that inspector is turned off.

It is off by default. The panel saves its own copy under pangular-pref:pill in its localStorage. Like passive mode, the popup keeps a separate copy under pangular-popup in your app's localStorage. The panel in the popup changes the popup's copy. A panel that the popup moved to its own window also changes it. That panel sends the change to the page that opened it. In passive mode the button stays hidden, pill or not.

Saved filters

Every inspector page has one search field, named Filter. Type in it to narrow the page, and press Escape to clear it. An Escape that clears the field does nothing else, so it doesn't also close the popup.

To keep a filter you use often, type it and press Save next to the field. It becomes a chip under the field:

  • Press a chip to apply its text. Press it again to clear the field. The chip of the text in the field shows as pressed.
  • Press the × on a chip to remove it.

Each view keeps up to 8 chips, in pangular-pref:filters:<view>. The Errors and Console views of the Errors tab, and the live and source views of a tab, keep separate chips. A chip saves the text only, not the other filters of the page.

Resizable panes

On a wide panel, the Injectors tree and its detail, and the NgRx Store log and its entry, are split by a bar you can drag. To resize from the keyboard, focus the bar and use the arrow keys (Shift for larger steps), Home and End. A double click puts the default width back. The width is saved per view, in pangular-pref:pane:<view>.

Browser agents

The Browser agent tools switch registers the read-only agent tools on your app's page, so an agent that drives the browser finds them through WebMCP or Chrome DevTools for agents. See Browser agents for what is registered and how the tools answer.

What Behavior
Default Off, unless agent.browserTools is true in the devtools config.
Turning it on or off Every page connected to the dev server registers or unregisters the tools right away. No reload is needed.
How long it lasts Until the dev server restarts. Then agent.browserTools decides again. The hint under the switch says whether the config has it on or off.
Where it is kept On the dev server, not in localStorage. Every panel connected to the server shows the same value and follows a change made in another one.
When it is disabled While the panel connects, in a saved report from pangular build, and with a devtools server that has no switch. Then set agent.browserTools in the config.

If the server refuses the change, an error with Retry shows under the switch.

In-page agents and other scripts can list WebMCP tools and run them. Leave the switch off if your development page loads scripts you don't trust.

Where to next