Skip to content
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

onFocusChange setting is not respected #11364

Closed
anavarre opened this issue Jun 29, 2022 · 4 comments
Closed

onFocusChange setting is not respected #11364

anavarre opened this issue Jun 29, 2022 · 4 comments
Labels
core issues related to the core of the application

Comments

@anavarre
Copy link

Bug Description:

When configurating Theia to automatically save onFocusChange, it is expected that the Auto Save Delay setting will not have any effect since it is written very clearly that this setting gets applied only when Auto Save is set to afterDelay.

onFocusChange

However, it seems this is not respected as you can see in the GIF file below.

bug-observation

Steps to Reproduce:

  1. Configure Auto Save to be OnFocusChange
  2. Set a high value for Auto Save Delay, e.g. 10000 to observe your file is never changed before 10 seconds, even when you change focus and expect the file to be saved then.
  3. Continue playing with the Auto Save Delay value until you get convinced it is indeed not respecting the promise that onFocusChange should take precedence and Auto Save Delay should only be enforced when the Auto Save is set to afterDelay.

Additional Information

  • Operating System: Ubuntu Xenial (with ESM)
  • Theia Version: 1.26
@vince-fugnitto vince-fugnitto added the core issues related to the core of the application label Jun 29, 2022
@colin-grant-work
Copy link
Contributor

I believe that this is a duplicate of #10812.

@anavarre
Copy link
Author

anavarre commented Jun 29, 2022

I did stumble upon #10812 before filing this issue but it didn't seem specifically related to it at first sight.

@colin-grant-work
Copy link
Contributor

I did stumble upon #10812 before filing this issue but it didn't seem specifically related to it at first sight.

Yes, my fault - it's an issue more for internal consumption than public clarity. I'll update the headline to be clearer.

@vince-fugnitto
Copy link
Member

Closing in favor of #10812.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core issues related to the core of the application
Projects
None yet
Development

No branches or pull requests

3 participants