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

Tab Maximize issue on custom editors #14051

Closed
safisa opened this issue Aug 15, 2024 · 5 comments · Fixed by #14062
Closed

Tab Maximize issue on custom editors #14051

safisa opened this issue Aug 15, 2024 · 5 comments · Fixed by #14062
Milestone

Comments

@safisa
Copy link
Contributor

safisa commented Aug 15, 2024

Bug Description:

Hi,
I think there is an issue in tab Maximize feature on custom editors. When using the maximized tab on a dirty tab, it will open it in dirty mode (modified state), but the issue is that if the user closes the maximized modified tab, and in the save modified file confirmation popup, select not to save, once the file is opened again it will open as modified !!!

Steps to Reproduce:

  1. open a custom editor file (e.g cat plugin)
  2. do some changes
  3. maximize the tab
  4. see that it is still a dirty file (bullet on the tab)
  5. close that tab
  6. in the save confirmation popup, choose not to save
  7. open the same file again, you will see that it is still in a modified state! it will keep like this until you save the file!

Additional Information

  • Operating System: Mac
  • Theia Version: 1.52
@JonasHelming
Copy link
Contributor

@dhuebner If I remember correctly, did you review or do a change in this area recently?

@dhuebner
Copy link
Member

@JonasHelming
Not sure I did something in the maximize editor workflow, but I can have a look.

@JonasHelming
Copy link
Contributor

:-) Not with maximizing, but with the save behavior or am I mistaken? Anyways, thank you for having a look!

@msujew
Copy link
Member

msujew commented Aug 19, 2024

@JonasHelming I've recently refactored the saving mechanism in #13683 :)

@msujew
Copy link
Member

msujew commented Aug 21, 2024

See #14062 for a fix. It seems like I broke some behavior in #13683.

@jfaltermeier jfaltermeier added this to the 1.53.0 milestone Aug 29, 2024
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 a pull request may close this issue.

5 participants