Created attachment 170487 [details] It show the context menu of the form instead of the input - Open a document and add a text input form field - Open the form broswer and click on the form name (not the root) - Right click on the text input field => it will show the context menu of the form instead of the input field - left click on the text input field - right click on the form name => it will show the context menu of the input instead of the form
On pc Debian x86-64 with master sources updated today, I could reproduce this.
(The form browser is the form navigator that you can found in the form menu)
Dear Matheod, 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
Created attachment 189876 [details] replace with context menu missing v6.3 Reproducible exactly as described in the original "actual results" in 7.3.3.2. Version: 7.3.3.2 (x64) / LibreOffice Community Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348 CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL However, if you dig back to 6.3 for example, the "actual results" isn't reproduced as described, however, there is still an issue with the "Replace with" context menu goes missing for the form controls. See step 5 and attachment for the results with the issue. Steps: 1. Open writer 2. Create a form control e.g. Form > Text Box 3. Open Form Navigator e.g. Form > Form Navigator 4. Within the Form Navigator, Left click on form name (above the form control) 5. Right click on form control (e.g. Text Box). The "Replace with" menu goes missing, which is NOT expected. 6. Left click on form name (above the form control). 7. Left click on form control (e.g. Text Box). 8. Right click on form control(e.g. Text Box). The "Replace with" menu appears, which is expected 8. Left click on form control (e.g. Text Box). 9. Right click on form name (above the form control). The context menu appears with all the correct options (New, Cut, Delete, Tab Order, Rename, Properties), as expected. Version: 6.3.0.0.alpha1 (x64) Build ID: 547edd20e527fb02900f6174973770d26306e2e7 CPU threads: 6; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL
On pc Debian x86-64 with LO Debian package 7.5.6 + gen rendering, I don't reproduce this. Idem with LO 7.5.7 on Windows 10. Could you give a try to a recent LO version like 7.5.7 ?
Dear Matheod, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
I was unable to reproduce this in the following version: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded I will move it to unconfirmed per QA Admin request.
Matheod: still waiting for your feedback
Dear Matheod, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp