Bug 137667 - Calc, API: queryContentCells doesn't correctly evaluate the flag bits 2^5 through 2^8
Summary: Calc, API: queryContentCells doesn't correctly evaluate the flag bits 2^5 thr...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-21 22:56 UTC by Wolfgang Jäger
Modified: 2023-07-09 03:16 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Demnstrating the reported bug in detail (16.91 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-10-21 22:56 UTC, Wolfgang Jäger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Jäger 2020-10-21 22:56:57 UTC
Created attachment 166606 [details]
Demnstrating the reported bug in detail

https://api.libreoffice.org/docs/idl/ref/namespacecom_1_1sun_1_1star_1_1sheet_1_1CellFlags.html#a54545dc062bc2be2d723d0cc34e8cbd2 defines flags which should be evaluated by the queryContentCells methods (connecting them by OR). 
Bit 5 (value 32) e.g. should, if set, make the query find cells to which a hard attribute was applied. Bit 6 (64) should find cells with an explicitly assigned cell style ...
These and also the "objects" flag don't work.  

Everything should is demonstrated in the attached document. 

BTW: The UsedAreaCursor qualifies cells with hard attributes as used.
Comment 1 Andreas Heinisch 2021-07-07 19:18:24 UTC
Confirmed in:

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 0aea0cee58fe77a9058217dfdfc3d6a02b29ee2a
CPU threads: 6; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: en-US (de_DE); UI: en-US
Calc: CL
Comment 2 QA Administrators 2023-07-09 03:16:16 UTC
Dear Wolfgang Jäger,

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