Issue 123843

Summary: Cell formatting does not hold
Product: Calc Reporter: Rob <nevermundahne>
Component: formattingAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Normal    
Priority: P3 CC: elish, issues
Version: 4.0.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Issue Type: DEFECT Latest Confirmation in: 4.0.1
Developer Difficulty: ---
Description Flags
Call A2 will have the word "Client: " on the first change, but not if changed again, unless there is a number. none

Description Rob 2013-12-12 21:49:02 UTC
Created attachment 82086 [details]
Call A2 will have the word "Client: " on the first change, but not if changed again,  unless there is a number.

Format -> Cells... -> User-defined

Format entered: "Client: "@

Typed into cell: 'Home Depot'
Expected Result: 'Client: Home Depot'
Actual Result on first try: 'Client: Home Depot'

Next typed into cell: 'Lowes'
Expected Result: 'Client: Lowes'
Actual Result on subsequent try: 'Lowes'

At this point if I type something with a number: '1Home Depot'
Expected Result: 'Client: 1Home Depot'
Actual Result: 'Client: 1Home Depot'

As long as there is a number somewhere in it, it will work, but just text will no longer have 'Client: ' in front any more, unless I reload the file.
Comment 1 Edwin Sharp 2013-12-13 08:40:06 UTC
Problem when word underlined by spell checker.

AOO410m1(Build:9750)  -  Rev. 1543812
Win 7
Comment 2 Rob 2013-12-13 12:43:40 UTC
Thanks Edwin, I just figured that out this morning and was going to add the comment, any idea if there is going to be a fix? Other then turning off spell checker?
Comment 3 Edwin Sharp 2013-12-13 13:25:56 UTC
I've hopefully added target milestone 4.1.0.
Comment 4 Rob 2013-12-13 13:59:20 UTC
Got it, I see how this forum works now, Thanks for the quick replies!
Comment 5 Oliver-Rainer Wittmann 2014-02-10 11:50:48 UTC
Reverting field Target Milestone has this should set, if we are more or less sure that it is/will be fixed in the given version.

If you think that this issue should be fixed in the next release, please raise it on the dev-list. Then it could be marked as a 'show-stopper'