这是indexloc提供的服务,不要输入任何密码
Skip to content

Textfield focus issue workaround #9091

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.

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

Merged
merged 3 commits into from
Apr 4, 2025

Conversation

elliette
Copy link
Member

@elliette elliette commented Apr 2, 2025

Adds the workaround for flutter/flutter#155265 to ALL of DevTools, not just the Property Editor.

Incorporates @ditman's suggestions as well to check if we are in a <flutter-view> first before calling blur (thank you!)

FYI @DanTup @jwren

Also FYI @johnpryan (Dartpad has the same issue, so adding this workaround there might be a good idea until it's fixed upstream in Flutter)

@elliette elliette requested a review from a team as a code owner April 2, 2025 22:37
@elliette elliette requested review from kenzieschmoll and removed request for a team April 2, 2025 22:37
@@ -101,15 +102,15 @@ class _PropertiesListState extends State<_PropertiesList> {
@override
void initState() {
super.initState();
// Workaround for https://github.com/flutter/devtools/issues/8929.
// Workaround for https://github.com/flutter/flutter/issues/155265.
setUpTextFieldFocusFixHandler();
Copy link
Member

Choose a reason for hiding this comment

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

do we still need this since we now have it at the root of DevToolsApp?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point, removed!

Copy link
Member

@kenzieschmoll kenzieschmoll left a comment

Choose a reason for hiding this comment

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

Have we done thorough testing to make sure that we are not causing any unforeseen side effects on other parts of the DevTools app? (different screens, embedded and non-embedded, vs code & intelliJ, devtools extensions, etc.)

@elliette
Copy link
Member Author

elliette commented Apr 4, 2025

Have we done thorough testing to make sure that we are not causing any unforeseen side effects on other parts of the DevTools app? (different screens, embedded and non-embedded, vs code & intelliJ, devtools extensions, etc.)

I've done the following testing, will need to finish testing tomorrow morning:

  • Different screens
  • Standalone app (Not embedded)
  • Embedded in VS Code
  • Embedded in IntelliJ
  • DevTools Extensions

@elliette elliette merged commit 09c4072 into flutter:master Apr 4, 2025
41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants