[khanak0509]

Fixes #9521

this PR fixes issue #9521 where logs with ANSI colors were not shown properly in the Logging screen. If a log had only a background color, the text became black, so with a black background it was fully invisible in dark theme. Colored text was also bigger than the normal text, and the Details panel showed the raw escape codes like [45m and [0m.

How I fixed it:
textSpansFromAnsi was creating a new TextStyle for colored spans and dropping the default style, so the color became null (black) and the font size fell back to default. Now it uses defaultStyle.copyWith(...), so colored spans keep the theme color and font size and only change what the ANSI code sets.
For the Details panel, I added a stripAnsi() helper and used it in LogData.prettyPrinted(), so the details text, search and copy all get clean text. For dart:developer logs the details are JSON, and JSON encodes the escape char as \u001b, so I handle that too.

before --

after --

Pre-launch Checklist

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.
• 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...
• OR there is a reason for not adding tests, which I explained in the PR description.

AI-tooling checklist

• I did not use any AI tooling in creating this PR.
• OR 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...
  • I added the release-notes-not-required label or left a comment requesting the label be added.
• OR 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.
  • I ran the DevTools app locally to manually verify my changes.

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

[gemini-code-assist]

Code Review

This pull request adds support for stripping ANSI escape codes from pretty-printed log details and refactors textSpansFromAnsi to preserve default text styles. It also includes comprehensive unit tests for these new behaviors. The review feedback recommends caching the computed result of prettyPrinted() to prevent redundant, expensive operations on the UI thread, ensuring better performance and consistency.

[srawlins]

Thanks much!