https://bugs.documentfoundation.org/show_bug.cgi?id=52242
stragu <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |.org Version|7.1.2.2 release |3.5.3 release --- Comment #17 from stragu <[email protected]> --- - Reverting the earliest version affected to correct one as per comment 2 - Issue regarding searching for a result of a formula using the search bar has been fixed in 7.3, which was tracked with bug 102506 (the default for the search bar is now to search for values, not formulas) Regarding what remains to be looked at in this bug report: (In reply to Roman Eisele from comment #1) > [...] > => IMHO there are two real bugs here: > > (i) when the user explictly selects "Search in": "Values", searching for > 120.00 and/or 120,00 (depending on locale settings) MUST find cell A3 with > the calculated value 120, too. > > (ii) when the user explictly selects "Search in": "Values", searching for > 120, 120.0 or 120,00 should NOT find the false-positive cells with values > 1120 (in C2) and 1200 (in C3). I can understand that (i) is a problem: one might want to find "120" when searching for "120.00", because there is a numerical equality. I believe this would require an extra option in the dialog, like "search for numerical values". (note that doing the opposite is already possible: using the "Formatted display" option, users can find a number formatted with e.g. two decimal places "120.00" by searching for the number "120"). Regarding (ii), I disagree that it needs a fix: users often want to search for parts of a string (or number), and if the user only wants the perfect match "120", an not "1120" or "1200", there is the option "Entire cells" for that. To clarify what this bug is about, I am changing the summary from the original, unspecific "Strange behaviour when searching numbers" to something more specific: "Match numeric values regardless of omissible leading or trailing zeros in Find and Replace dialog" To clarify further, what I think this bug report is about is: There should be an option to make a search for "120.00" or "120,00" (depending on locale) match the value "120". Similarly, the same option would allow searching for "000120" and getting the match "120" (or 120.0, etc.). In essence, a "numerical search" of sorts. -- You are receiving this mail because: You are the assignee for the bug.
