Bug 115926 - dock recents contextual menu not clearing
Summary: dock recents contextual menu not clearing
Status: RESOLVED DUPLICATE of bug 100532
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: All macOS (All)
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 115925 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-02-21 23:02 UTC by Ted Lee
Modified: 2018-02-22 07:57 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
screen shots of dock contextual menu and LO file menu/start center at the same time (671.52 KB, text/LibreOffice)
2018-02-21 23:09 UTC, Ted Lee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ted Lee 2018-02-21 23:02:07 UTC
In MacOS when an app is in the dock there often is a contextual menu list (right-click or control click) of recently opened documents, from which one can be selected to open the app with.  LibreOffice does have such a list when it is in the dock.  Unfortunately, it looks like the list contains every single document that has ever been opened (up to presumably some maximum.)  That list should be cleared whenever the "recent documents" list in the LO File menu or "recent files" in the start center is cleared.  Attached are screen shots of the contextual menu on my machine at the moment and the LO file menu and start center file display.  The latter two are empty; the dock list is not but should be.
Comment 1 Ted Lee 2018-02-21 23:09:16 UTC
Created attachment 140047 [details]
screen shots of dock contextual menu and LO file menu/start center at the same time

I thought this attachment went with the original bug report, but it doesn't look like it did.  If it's there but I can't find it, this would be a duplicate attachment!
Comment 2 Xisco Faulí 2018-02-21 23:17:47 UTC
*** Bug 115925 has been marked as a duplicate of this bug. ***
Comment 3 Alex Thurgood 2018-02-22 07:57:32 UTC

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