Description: 1. Open a document containing user-defined variables in LIbreOffice 6.4 or earlier. 2. Copy the text, including the variables. 3. Go to a document in LibreOffice 7.0 RC1. 4. Paste the copied text. Expected: The text and variables all paste into the new document and are editable. Actual Result: The text pastes in, and the variables look like they have pasted in, but they are locked; their values can not be changed, nor can they be deleted. Double-clicking to open the value dialog has no response. Attempts to delete the pasted fields result in the message "Write-protected content can not be changed." The bug occurs if you use CTRL-C and CTRL-V. If you create new variables in LibO 7 RC2, they will cut and paste to new documents as expected. If you CTRL-C from an old version and then do "PASTE SPECIAL" (selecting the top option, which is currently blank) then they paste normally. The variables work fine if you open the original document (made in the prior version of LibO) with 7.0.0.1 RC 1. This only seems to affect cut/paste operations. It seems to do this consistently on both of the boxes I have tried it on (both running Windows 10). Steps to Reproduce: 1. Open a document containing user-defined variables in LIbreOffice 6.4 or earlier. 2. Copy the text, including the variables. 3. Go to a document in LibreOffice 7.0 RC1. 4. Paste the copied text. Actual Results: The text pastes in, and the variables look like they have pasted in, but they are locked; their values can not be changed, nor can they be deleted. Double-clicking to open the value dialog has no response. Attempts to delete the pasted fields result in the message "Write-protected content can not be changed." Expected Results: The text and variables all paste into the new document and are editable. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.0.0.1 (x64) Build ID: 04ba7e3f1e51af6c5d653e543a620e36719083fd CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Dear Steven Shelton, 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
Dear Steven Shelton, 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