Open Bug 1794660 Opened 3 years ago Updated 2 years ago

Dev tools extension to observe internal state of components

Categories

(Firefox for Android :: General, task)

All
Android
task

Tracking

()

People

(Reporter: csadilek, Unassigned)

Details

From github: https://github.com/mozilla-mobile/android-components/issues/6341.

Some what related to #455.

Problem
There's a lot of state in our components. We are unifying on using browser-state which operates on a large, redux-style, state tree. Understanding how this tree looks like and how it changes it key in debugging issues. The debugger sometimes is helpful here, but we are never interested in observing all state changes - and it only works for debug builds.

Idea
We already support connecting to remote devices via about:debugging on a desktop computer. And (at least on desktop) there is a webextension API that allows us to extend the functionality of dev tools. Would it be possible to use dev tools from a desktop computer to inspect the state of browser-state? If this is a feasible approach then we could step by step add more helpful tools using that bridge.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Severity: -- → N/A
Type: defect → task
Flags: needinfo?(cpeterson)
You need to log in before you can comment on or make changes to this bug.