https://bugs.documentfoundation.org/show_bug.cgi?id=157428
Stéphane Guillou (stragu) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |minor Summary|Auto-input when editing |AutoInput active when |existing text: no hint that |trying to change |the value will change when |capitalisation in previous |pressing enter |value Priority|medium |low --- Comment #8 from Stéphane Guillou (stragu) <[email protected]> --- Just tested with Office 365 and indeed, even though autoinput is on, going back to a value and changing the capitalisation does not trigger autoinput. Example in Office 365: 1. Insert in A1: some words <Enter> 2. Insert in A2: some W <Enter> Result: it autocompletes with "some words" (lowercase version), which makes sense to keep data consistent. However, if editing A2: A) mid-string change in capitalisation: no autoinput suggestion, accepts edit (different to LO) B) remove character(s) at the end of the string: no autoinput suggestion, accepts edit (same as LO) C) remove characters at the end of the string, then add characters that match a previous value: autoinput active (same as LO) If several values match, a list is shown, without a default selection. (Different to LO.) I tend to agree with Frants now, in that this MS Office behaviour for case A should be preferred, and an existing value should not be forced on the user if they are going back to change the case of some characters mid-string. -- You are receiving this mail because: You are the assignee for the bug.
