Created attachment 159276 [details] Draw document with a single, open three point polyline While discussing bug 131758, I found there should be a context menu entry to "Open" a polygon, as the reverse action of the existing "Close object" entry. In bug 131758 comment 15, Regina provided an example document with screenshots to help me find that entry, which she is seeing on Windows. See attachment 159274 [details]. So currently I believe this is either a bug, or I'm still doing something different then Regina. I checked out the exact revision that Regina uses from the 6.5 / 7.0 linux bibisect repo (commit 0701a3a3be2f114d7ad176e7beabc7abc94cc5dc "sha:6388c578c672690fff662cb04b6a0436cd742f37"). No luck with either gen, gtk3 or kf5. So it doesn't seem to be a problem with the native menu VCL implementation in either gtk3 or kf5, as gen is also affected. I also tested a fresh profile using -env:UserInstallation without a difference. To reproduce: 1. open the attached document 2. select the polygon 3. open the context menu of the polygon and select "Close object" 4. open the context menu of the polygon and check for the toggle entry "Close object" Actual result: "Close object" entry vanishes after action 3. Expected result: "Close object" entry is a check box, doesn't vanish and is now selected. "Side bug": for whatever reason the entry is called "Close Beźier" in Regina's screenshot, even if it's a polygon from the status line.
Created attachment 186513 [details] repro-closed-polygon Repro Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c4a58634753a84b09f20f7271d6525a6656522d3 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded
Dear Jan-Marek Glogowski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug