Bug 144100 - AutoInput fuction goes only on the next cell.
Summary: AutoInput fuction goes only on the next cell.
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-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-26 09:47 UTC by franco fuochi
Modified: 2021-08-29 03:49 UTC (History)
2 users (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 franco fuochi 2021-08-26 09:47:49 UTC
Description:
The autoinput function (LibreOffice Calc 7.2) goes only on the next cell. THis function don't go on other cells.
T.I.A.
 

Steps to Reproduce:
1.Insert any text in a cell
2. Go in the cell below and write the first letter of the cell above

Actual Results:
If you go in the cell below and you write the dirst letter of the cell above you will see the hint.
3.If, on the other hand, you go to some cell below and leave a blank one, the suggestion will not displayed...

Expected Results:
In the prevoius release (7.1.5) the hint was highlighted and fetched  for many cells...


Reproducible: Always


User Profile Reset: No



Additional Info:
none
Comment 1 [REDACTED] 2021-08-26 09:56:01 UTC
Repro

Version: 7.2.0.4 / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 4; OS: Mac OS X 10.16; UI render: default; VCL: osx
Locale: en-US (en_DE.UTF-8); UI: en-US
Calc: threaded

Repro

Version: 7.2.0.4 / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 2 m_a_riosv 2021-08-26 16:21:27 UTC
I don't find it, but I think it is already reported.
Comment 3 Ming Hua 2021-08-29 03:49:51 UTC
(In reply to m.a.riosv from comment #2)
> I don't find it, but I think it is already reported.
Yes, and it was resolved as NOTABUG :-(

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