Bug 443081 - Inapropriate UI/UX when reopening tabs/docs
Summary: Inapropriate UI/UX when reopening tabs/docs
Status: RESOLVED DUPLICATE of bug 364680
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 20.12.3
Platform: Debian stable Linux
: NOR wishlist
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-28 15:40 UTC by Max Power
Modified: 2021-09-30 15:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Max Power 2021-09-28 15:40:13 UTC
SUMMARY
When Okular is closed abruptly (e.g. OS Shutdown) it remembers open tabs/docs from last session and reopens them again at the next startup. When Okular is closed as designated (e.g. X button) it does not remember the last open tabs/docs.

As a user who wants the last tabs/docs being reopened at the next startup, i never close okular as designated but abruptly so that Okular remembers the last tabs/docs - which does not represent a neat UX.  


STEPS TO REPRODUCE
1. open okular and open a document
2. close okuar
3. reopen okular

OBSERVED RESULT
opened okular is empty

EXPECTED RESULT
opened okular with reopened last document(s)

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: 5.10.0-8-amd64
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Albert Astals Cid 2021-09-28 19:03:01 UTC
There is nothing inapropiate about what Okular does, this is at most a wish.
Comment 2 Max Power 2021-09-28 23:42:49 UTC
Of course it's a wish, every expectation is a wish somehow. Every user has an expectation towards a tool made to be used by the user. And what I am experiencing is not what I expect. If the majority of users do not experience what they are expecting then that tool/module is just crap. Anyway thank you for your response.
Comment 3 Nate Graham 2021-09-30 15:17:20 UTC

*** This bug has been marked as a duplicate of bug 364680 ***