Hide extension button when embedded in an IDE - #9956
Conversation
extension on screen, even when embedded in an IDE.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the DevTools scaffold to conditionally show or hide the ExtensionSettingsAction based on the current screen and the embed mode. Specifically, when DevTools is embedded in an IDE (EmbedMode.embedOne), the extension settings action is hidden unless the active screen is an ExtensionScreen or the query parameters specify to hide all except extensions. The changes also include corresponding updates to the status line and comprehensive unit and widget tests to verify this behavior. There are no review comments, and I have no feedback to provide.
_controller_web.dart to prevent browser X-Frame-Options iframe errors during local debugging.
| When an AI agent is performing this workflow: | ||
|
|
||
| - **Obtaining VM Service URI**: When connecting to a target app, ask the user to provide the VM Service URI printed in the target app's console output (using `ask_question` or a direct prompt). | ||
| - **Automated Browser Opening**: The agent should launch DevTools and execute `open <url>` to launch the browser automatically. |
There was a problem hiding this comment.
step 2B above gives other commands depending on the OS. Should we include those other commands here or link to where this is described above?
Co-authored-by: Kenzie Davisson <43759233+kenzieschmoll@users.noreply.github.com>
|
@kenzieschmoll this is ready for another look |
3 participants
Hide the extension settings action when DevTools is running in an IDE, unless the current screen is an extension.
This also helps with debugging extensions locally by adding an agent skill, and by fixing an issue where
flutter.dev'sX-Frame-Optionsheader caused a "connection refused" when debugging extensions locally.Fixes #8507