[NemesisDevX]

Fixes #10004

The Network screen toolbar and the shared footer status line overflowed and overlapped at narrow widths (328 to 599 px). The toolbar's search and filter fields were squeezed into one row beside fixed controls. The footer's page status, device text and embedded actions did not fit.

What changes

• Network toolbar: below 600 px the search field gets its own row. Below 900 px the filter field gets its own row. At 900 px and above the layout is unchanged.
• Footer (StatusLine, shared by all screens): footer text is truncated with an ellipsis instead of overflowing. Below 900 px the video tutorial link and, when DevTools is embedded, the Settings, Feedback, About and extension-settings actions move into a "More actions" popup. Each item calls the same callback as its inline control, and the tutorial item records the same analytics event. Below 600 px the disconnected status shows an icon with a tooltip instead of text.
• DevToolsScaffold.defaultActions now returns List<ScaffoldAction> (was List<Widget>), so the footer can reuse the existing actions. The other caller in app.dart is unchanged.
• Release note added under "Network profiler updates".

Reviewer notes:

• At 328 px in standalone mode the popup contains only the tutorial. Settings, Feedback and About stay in the top bar, as before.
• The "More actions" trigger renders 48 × 27 logical px, the height of the footer. It is not a 48 px square target.

Before and after

Before and after captures at 328 px and 411 px, and separate 1400 px desktop comparisons, were taken with headless Chromium against the upstream base (9ac04e2) and this branch, using the same networking test app. They are attached below as public GitHub attachments.

Attachments, all public GitHub user attachments. The GIF and images were captured by scripts that drove headless Chromium against real pages. This is agent-operated capture, not manual testing.

Corrected 9.8-second GIF. Three scenes: 328 px standalone, 411 px embedded footer, and the More actions menu open at 411 px. Each frame shows the upstream base on the left and this branch on the right.

328 px standalone. Base on the left, this branch on the right.

411 px embedded footer. Base on the left, this branch on the right.

411 px embedded, More actions menu open. The popup overlaps part of the footer while it is open.

1400 px desktop, standalone. Base on top, this branch below. The top toolbar band and the request details pane are pixel-identical between builds. The footer request count differs with traffic.

1400 px desktop, embedded. Base on top, this branch below.

Tests

Run on the repository-pinned candidate SDK (Flutter 3.50.0-0.2.pre, revision fab991537bf):

Check	Result
flutter test on status_line_test.dart and network_responsive_test.dart	71 of 71 passed
flutter test on framework, network, logging, extension, memory diff and property editor suites	338 of 338 passed
dart format --set-exit-if-changed (changed files)	0 changed
dart analyze (changed files) and dart analyze lib	No issues
dt presubmit (without --fix)	Passed with exit 0. Warnings: nonfatal analytics network exceptions, and flutter_lints resolution warnings in fixture format checks.
flutter test test/ (full devtools_app suite)	Not clean locally. Candidate runs ended with 1 unrecovered failure each (+1721 ~12 -1, and +1720 ~12 -1 with exit 1). The base 9ac04e2 run also failed (+1649 ~12 -1). The failures are a CPU-profile benchmark threshold (GenerateFromCpuSamplesBenchmark, expected under 120000) and an intermittent "used after being disposed" error on ValueNotifier<StackFrameAndSourcePosition?>. Both also occur on the base. This change does not touch those tests, and I did not alter them. CI is the reference for the full suite.

Not run: golden tests, integration_test/ tests, and macOS or Windows desktop builds.

Known limitations (pre-existing, not changed here)

• Keyboard: Tab from the page does not reach the footer, because the screen body is a Flutter focus scope. This is the same on the upstream base. Once the More actions trigger has focus, Enter or Space opens the menu, Tab and Shift+Tab move between items, Enter activates an item, and Escape closes the menu. In Chromium, arrow keys do not move focus within the popup. Flutter's stock PopupMenuButton behaves the same on this SDK. The widget tests cover arrow keys under the Flutter test binding, not in a browser.
• Settings dialog: its checkbox rows overflow below 600 px, in shared dialog code that also overflows on the base. The Settings menu item is tested at 600 px only.
• Page status: "Showing N of M requests" is hidden below 600 px, as on the base.
• Screen readers were not tested.
• The browser checks were scripted (Playwright driving headless Chromium, profile-mode web builds, Windows). They are not manual testing.

AI assistance disclosure

Implementation and tests were developed with AI assistance (Devin, an AI software agent), which also ran the scripted browser checks. GPT-6, an AI model, reviewed the change and the evidence. The contributor directed and supervised this work and intends to take responsibility for it. Line-by-line human review of the code has not yet been completed, and this PR will not be marked ready for review until it has been. An earlier series of agent-authored development commits is not part of this PR. This PR contains a single commit with the same tree as the tested branch.

Checklist

Pre-launch checklist (boxes left unchecked are for the contributor to confirm personally):

General checklist:

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read the Flutter Style Guide recently, and have followed its advice.
• I signed the CLA.
• I updated/added relevant documentation (doc comments with ///).

Issues checklist:

• I listed at least one issue that this PR fixes in the description above.
• I listed at least one issue which has the contributions-welcome or good-first-issue label. (Not applicable: DevTools Network tab header and footer toolbar controls overlap on narrow screens #10004 has neither label.)
• I did not list at least one issue with the contributions-welcome or good-first-issue label. I understand this means my PR might take longer to be reviewed.

Tests checklist:

• I added new tests to check the change I am making.

AI-tooling checklist:

• I did not use any AI tooling in creating this PR.
• I did use AI tooling, and...
  • I read the AI contributions guidelines and agree to follow them.
  • I reviewed all AI-generated code before opening this PR.
  • I understand and am able to discuss the code in this PR.
  • I have verifed the accuracy of any AI-generated text included in the PR description.
  • I commit to verifying the accuracy of any AI-generated code or text that I upload in response to review comments.

Feature-change checklist:

• This PR does not change the DevTools UI or behavior and...
• This PR does change the DevTools UI or behavior and...
  • I added an entry to packages/devtools_app/release_notes/NEXT_RELEASE_NOTES.md.
  • I included before/after screenshots and/or a GIF demo of the new UI to my PR description. (Attached in Before and after.)
  • I ran the DevTools app locally to manually verify my changes.

If you need help, consider asking for help on Discord.