Description: On Vertical text direction document, use Auto-Redact -> set black bar to different position. On detail is following step and attachment video. also, the direction of black bar is horizontal. Steps to Reproduce: 1. open writer document with vertical text direction. 2. tool > Auto-Redact 3. input target 4. Press OK -> Run Auto Redaction, but position and direction of black bar is different. Actual Results: position and direction of black bar is different. direction is horizontal. position is different. Expected Results: the direction of black bar is vertical. the position of black bar is true. Reproducible: Always User Profile Reset: Yes Additional Info: i confirm this version. Version: 7.1.0.0.alpha0+ Build ID: <buildversion> CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-07-27_15:39:15 Calc: threaded OS:Linux MATE
Created attachment 163670 [details] ScreenCast
Created attachment 163671 [details] Sample Document using file on video.
Reproduced. the so-called black bar in Draw that should have covered the area where confidential information is placed is horizontal, even when the page is set to tb-rl. This resulted in the auto-redaction beding useless in tb-rl documents.
note: the starting point of the redaction itself seems correct, i.e. paragraph start.
https://opengrok.libreoffice.org/xref/core/sfx2/source/doc/SfxRedactionHelper.cxx?r=0025b74e&fi=addPagesToDraw#142 https://opengrok.libreoffice.org/xref/core/include/vcl/outdev.hxx?r=751f4d44#119 only 5 arguments are given here, but if the text is vertical, we may need to explicitly specify the sixth argument, such as SalLayoutFlags::Vertical(but I'm not sure how to tell whether we need this flag) Also, I still haven't taken a look at rtl thingy yet.
>rtl thingy I meant Right To Left
Dear sawakaze, 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