Bug 144489 - AutoInput in recent version(s) of LibreOffice Calc does not consistently function.
Summary: AutoInput in recent version(s) of LibreOffice Calc does not consistently func...
Status: RESOLVED DUPLICATE of bug 143960
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.2.0.4 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-14 13:00 UTC by rich.holtman
Modified: 2021-09-14 13:11 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rich.holtman 2021-09-14 13:00:38 UTC
Description:
AutoInput used to work. I use it all the time in multiple spreadsheets.

Steps to Reproduce:
1. create a new spreadsheet, be sure Tools, AutoInput is checked.
2. enter a few text strings in a column, with no empty spaces between
3. move down just below that column, type first letter of one string, AutoInput works as expected.
4. But, move down the column such that there is an empty row or rows between the few text strings and the empty input box, type first letter on one string, then AutoInput does NOT work as expected.

4.

Actual Results:
One can also use Alt+down arrow to display the AutoInput possibilities. This also only works properly when in an input box that is directly next to the text strings, either below or above the text strings.  Conversely, move such that an empty row exists and the AutoInput function does not work.

Expected Results:
When AutoInput does not work, nothing happens.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 Ming Hua 2021-09-14 13:11:53 UTC
Thanks for reporting.  This issue has already been reported and fixed.  The upcoming 7.2.1 release will include the fix.

See more details in bug 143960 and bug 142214.

*** This bug has been marked as a duplicate of bug 143960 ***