Description: According to specification: Abs determines the type of reference: 1: absolute ($A$1) 2: row reference type is absolute; column reference is relative (A$1) 3: row (relative); column (absolute) ($A1) 4: relative (A1) It should not give result in case, when abs=5..8 Steps to Reproduce: 1. Run LibreOffice calc 2. Enter following formulas to any cell: =ADDRESS(1, 1, 5) =ADDRESS(1, 1, 6) =ADDRESS(1, 1, 7) =ADDRESS(1, 1, 8) 3. Apply and observe result Actual Results: Calculation result is displayed: abs=5 - absolute ($A$1) abs=6 - row reference type is absolute; column reference is relative (A$1) abs=7 - row (relative); column (absolute) ($A1) abs=8 - relative (A1) Expected Results: #VALUE! error Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 6.0.6.1 (x64) Build ID: dc68ad6c5cde3c62874b96422f2e5e8252499bad CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: CL
Repro with Version: 6.1.1.0.0+ (x64) Build ID: c20eb29560fa9d9e552c799203156c0742451eba CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:libreoffice-6-1, Time: 2018-07-28_12:44:37 Locale: es-ES (es_ES); Calc: CL But looks to me as minor issue.
Created attachment 143923 [details] sample file
Also reproduced in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 @Winfried, I thought you could be interested in this issue...
The cases 5,6,7,8 are explicitly handled as synonyms for 1,2,3,4 at https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr1.cxx#8089 I guess that is for some compatibility with another spreadsheet application. Excel documentation https://support.office.com/en-US/article/ADDRESS-function-D0C26C0D-3991-446B-8DE4-AB46431D4F89 doesn't mention these values either, but maybe it handles them or earlier versions did such thing? The code is in since the early (then deactivated) prototype of 2006 commit 6aadb208c71286cf4fcbaf7c611c45fd2e0c6c92 FWIW, Gnumeric handles this the same but also documents only 1,2,3,4. (not really a surprise considering the author of the OOo prototype code was Jody ;-)
Dear Andrey, 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
No news here. Code is still the same, so.. I suggest to close this as wontfix, no one jumped in on comment 4 and I much believe the code is there for a compatibility reason.