Created attachment 145951 [details] Sample DOCX, protected The attached DOCX has been created and set to protected in Word via Review -> Restrict Editing, with editing restrictions set to No changes (Read Only). When opened in Writer, there's no editing restriction on the document. The same happens if the document is protected with a password. Observed using LO 6.2 alpha1 & 3.3.0 / Windows 7.
Created attachment 145952 [details] Sample DOCX, protected, password: 12345
Created attachment 145953 [details] Sample DOCX, protected, with editable region This document has editable regions after the colons in each line, which should be kept editable.
Created attachment 145954 [details] Screenshot of editable regions in Word This is what such a document with editable regions looks like in Word.
OK, let's have a bug for DOCX.
Dear Aron Budea, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Only the last patch is really involved in solving this particular bug, but they all flowed out of work for this bug: https://gerrit.libreoffice.org/c/core/+/90302 writerfilter: DocProtect_enforcement defaults to false https://gerrit.libreoffice.org/c/core/+/90321 tdf#106843 docxexport: don't write double docProtect https://gerrit.libreoffice.org/c/core/+/90322 related tdf#106843 docxexport: if not enforced, let Writer protect https://gerrit.libreoffice.org/c/core/+/90323 tdf#120852 writerfilter: support read-only docProtection
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3af7be613526404276210a698f77e0187831b9b1 tdf#120852 writerfilter: support read-only docProtection It will be available in 7.0.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.