Skip to content

Remove legacy inspector documentation #13233

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
crackedhandle wants to merge 2 commits into from
Closed

Remove legacy inspector documentation #13233

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9b0a7cb
Remove legacy inspector documentation
crackedhandle Mar 30, 2026
8dad405
Remove 'new' distinction from inspector heading
crackedhandle Mar 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 2 additions & 14 deletions src/content/tools/devtools/inspector.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,11 @@ trees, and can be used for the following:

![Screenshot of the Flutter inspector window](/assets/images/docs/tools/devtools/inspector_screenshot.png){:width="100%"}

## The new Flutter inspector {:#new}
## The Flutter inspector {:#new}

As part of Flutter 3.29, the new Flutter inspector is enabled by default.
However, it can be disabled from the [inspector settings dialog][].
The Flutter inspector is enabled by default. It can be configured from the [inspector settings dialog][].

[inspector settings dialog]: #inspector-settings
[legacy inspector]: /tools/devtools/legacy-inspector

@gemini-code-assist gemini-code-assist Bot Mar 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The removal of the legacy inspector link is correct. However, the introductory text in this section (lines 32-33) still refers to the inspector as "the new Flutter inspector" and mentions that it can be disabled. Since the legacy inspector has been removed, these distinctions are now obsolete and potentially confusing for users.

Consider updating the text to reflect that the current inspector is the standard one and removing the mention of disabling it to switch to the legacy version. For example:

## The Flutter inspector {:#new}

The Flutter inspector is enabled by default. It can be configured from the [inspector settings dialog][].

@crackedhandle crackedhandle Mar 30, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The removal of the legacy inspector link is correct. However, the introductory text in this section (lines 32-33) still refers to the inspector as "the new Flutter inspector" and mentions that it can be disabled. Since the legacy inspector has been removed, these distinctions are now obsolete and potentially confusing for users.

Consider updating the text to reflect that the current inspector is the standard one and removing the mention of disabling it to switch to the legacy version. For example:

## The Flutter inspector {:#new}

The Flutter inspector is enabled by default. It can be configured from the [inspector settings dialog][].

Fixed, updated the heading and intro text to remove the 'new' distinction and the mention of disabling to switch to legacy inspector.

[filing a bug]: https://github.com/flutter/devtools/issues/new

### Debugging layout issues visually
Expand Down Expand Up @@ -570,16 +568,6 @@ Toggling this value enables or disables the hover inspection functionality.
When enabled, the widget tree automatically refreshes after
a hot-reload or a navigation event.

### Use legacy inspector

When enabled, use the [legacy inspector][] instead of the new inspector.

:::note
The [legacy inspector][] will be removed in a future release.
Let us know if there are issues preventing you from using the new inspector by [filing a bug][].
:::

[legacy inspector]: /tools/devtools/legacy-inspector

### Package directories

Expand Down
Loading