https://bugs.documentfoundation.org/show_bug.cgi?id=146734

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |---

--- Comment #4 from [email protected] ---
Works erratically in:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d466df5bc220eb80b8a51ff64507de881b938ed3
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: da-DK (da_DK); UI: en-US
Calc: CL threaded


Details:

1. Always goes to correct page (
https://help.libreoffice.org/7.6/en-US/text/shared/guide/template_manager.html
) but not correct bookmark in this page.

2. When opening the Template Manager for the first time, and pressing F1 with
the "Manage" button selected, it always goes to "Search"

HID=sfx/ui/templatedlg/search_filter#bm_id041620170649376935

3. Leaving the Template Manager open and repeating F1 on the "Manage" button,
it usually goes to "Search", but occasionally has gone correctly to "Manage"

HID=sfx/ui/templatedlg/action_menu#bm_id041620170649376938

4. Every once in a while, it reports a 404 message.

5. Have not been able to detect any pattern.  Sometimes goes correctly to
Manage after 2 or 3 tries (where the initial results was always "Search").  But
in other attempts, it went to "Search" 14 times and never went to "Manage". 

6. Also tested in Safe Mode, with similar problems (e.g., in first three
attempts, I got:  "Search", "404 not found", and "Manager" (expected).
And have quit and restarted the program, but the same problem remains.

7. I have the impression that once LO "finds" the right bookmark, then it
continues to go to the right place (but has been hard to test systematically),
but if the Template Manager is closed and reopened, then the first attempt with
F1 on "Manage" always goes to Search.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to