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

Remember current tab from previous user session #1073

Closed
ShaopengLin opened this issue Mar 30, 2024 · 5 comments · Fixed by #1120 or #1132
Closed

Remember current tab from previous user session #1073

ShaopengLin opened this issue Mar 30, 2024 · 5 comments · Fixed by #1120 or #1132
Assignees
Milestone

Comments

@ShaopengLin
Copy link
Collaborator

#1048 introduced the feature to reopen tabs on start-up. However, on many browsers (Firefox, Chrome), the current tab is also being kept track of when restoring user sessions. It would be good UX to have this feature.

One thing to discuss is: that we are not currently reopening invalid Zim tabs, empty tabs, settings tabs, etc. Users could be on one of those tabs from the previous session, including the library tab. How should we define the behavior of our tab reopenings?

@kelson42 kelson42 changed the title Remeber current tab from previous user session Remember current tab from previous user session Apr 1, 2024
@kelson42
Copy link
Collaborator

kelson42 commented Apr 1, 2024

One thing to discuss is: that we are not currently reopening invalid Zim tabs, empty tabs, settings tabs, etc. Users could be on one of those tabs from the previous session, including the library tab. How should we define the behavior of our tab reopenings?

Remembering these tabs is probably the right thing to do AFAP.

@ShaopengLin
Copy link
Collaborator Author

@kelson42 If we were to re-open all tabs(including invalid ones), should we have a designated, "404 not found" page? Or should we just leave it blank? Also tagging @mgautierfr since he also mentioned about this behavior back in the original issue.

@kelson42
Copy link
Collaborator

kelson42 commented Apr 8, 2024

@kelson42 If we were to re-open all tabs(including invalid ones), should we have a designated, "404 not found" page? Or should we just leave it blank? Also tagging @mgautierfr since he also mentioned about this behavior back in the original issue.

@ShaopengLin 404 is an HTTP specific error code, which makes not much sense in our local context. But "yes" a proper error message would be better than a blank page obviously. Probably this should be done in a dedicated PR.

@ShaopengLin
Copy link
Collaborator Author

If I get it correctly, we can simply open them as blank pages at the moment. We can achieve the functionality first and then open another issue for creating dedicated error message tabs.

@kelson42 kelson42 moved this to TODO in GSOC 2024 May 3, 2024
@kelson42 kelson42 added this to the 2.5.0 milestone May 18, 2024
@kelson42
Copy link
Collaborator

If I get it correctly, we can simply open them as blank pages at the moment. We can achieve the functionality first and then open another issue for creating dedicated error message tabs.

I confirm. You can go ahead with the implementation.

@kelson42 kelson42 moved this from TODO to DOING in GSOC 2024 May 30, 2024
@kelson42 kelson42 modified the milestones: 2.5.0, 2.4.0 May 30, 2024
@kelson42 kelson42 moved this from DOING to REVIEW in GSOC 2024 Jun 1, 2024
@github-project-automation github-project-automation bot moved this from REVIEW to DONE in GSOC 2024 Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: DONE
2 participants