Issue 98999 - If selection within input line of Calc is not reflected within the corresponding cell, then an entered change is lost
Summary: If selection within input line of Calc is not reflected within the correspond...
Status: UNCONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: ui (show other issues)
Version: DEV300m41
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-07 18:40 UTC by Graham Perrin
Modified: 2014-01-02 15:33 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
the word minim is selected in the input line but _not selected_ in the corresponding cell (144.11 KB, image/png)
2009-02-07 18:46 UTC, Graham Perrin
no flags Details
the overtype in the input line is _not reflected_ in the corresponding cell (144.12 KB, image/png)
2009-02-07 18:48 UTC, Graham Perrin
no flags Details
return key moves to the next cell and _loses the user's edit_ (143.25 KB, image/png)
2009-02-07 18:51 UTC, Graham Perrin
no flags Details
an example of a properly reflected selection (149.70 KB, image/png)
2009-02-07 18:52 UTC, Graham Perrin
no flags Details
the word amet is selected in the input line but _not selected_ in the corresponding cell (143.28 KB, image/png)
2009-02-07 18:53 UTC, Graham Perrin
no flags Details
the overtype in the input line is _not reflected_ in the corresponding cell (143.64 KB, image/png)
2009-02-07 18:54 UTC, Graham Perrin
no flags Details
demonstrating that mismatch also occurs without a highlight of the corresponding cell (147.33 KB, image/png)
2009-02-07 18:58 UTC, Graham Perrin
no flags Details
demonstrating again that a press of the Enter key loses the user's edition (144.96 KB, image/png)
2009-02-07 18:59 UTC, Graham Perrin
no flags Details
Name Box specifies A1; A1 not highlighted; three neighbours highlighted; the word selected in the input line is not selected in A1 (92.01 KB, image/png)
2009-02-07 19:26 UTC, Graham Perrin
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Graham Perrin 2009-02-07 18:40:25 UTC
1.	enter a few words in each of four cells A1 B1 A2 B2

2.	escape

3.	command-click B2, do not release the command key

4.	command-click A2, do not release the command key

5.	command-click B1, do not release the command key

6.	command-click A1

—	without moving the cursor away from cell A1

7.	release the command key

8.	observe selection of the four cells

—	aim for the input line

—	without double-clicking anywhere within the input line

9.	click the beginning of a word in the midst of the input line

10.	observe de-selection of the corresponding cell

11.	observe the remaining highlight of the other three cells

12.	drag to the end of the word (select)

13.	observe the matching selection of one word in cell A1


= Bug =

Selection of text 
within the input line 
is sometimes/often _not_ matched by a 
selection in the corresponding cell.

I see this often, more often than not, but I can't figure out exactly how to reproduce it.

Whenever this occurs: 

*	any edition of the text in the input line 
	will be lost when the user keys Enter or Return.

Now, whilst reporting: I see the bug even when there is highlight/selection of no more than one cell; 
but I'll leave this report as it is, because I noticed the bug first after non-contiguous (command-click) 
selection of cells. 

I'll attach screen shots demonstrating the mismatch and the loss of edition.
Comment 1 Graham Perrin 2009-02-07 18:46:58 UTC
Created attachment 60004 [details]
the word minim is selected in the input line but _not selected_ in the corresponding cell
Comment 2 Graham Perrin 2009-02-07 18:48:41 UTC
Created attachment 60005 [details]
the overtype in the input line is _not reflected_ in the corresponding cell
Comment 3 Graham Perrin 2009-02-07 18:51:58 UTC
Created attachment 60006 [details]
return key moves to the next cell and _loses the user's edit_
Comment 4 Graham Perrin 2009-02-07 18:52:35 UTC
Created attachment 60007 [details]
an example of a properly reflected selection
Comment 5 Graham Perrin 2009-02-07 18:53:32 UTC
Created attachment 60008 [details]
the word amet is selected in the input line but _not selected_ in the corresponding cell
Comment 6 Graham Perrin 2009-02-07 18:54:08 UTC
Created attachment 60009 [details]
the overtype in the input line is _not reflected_ in the corresponding cell
Comment 7 Graham Perrin 2009-02-07 18:55:29 UTC
When the selection in the input line is not reflected in the corresponding cell, 

* Enter key moves to the next cell and _loses the user's edit_
Comment 8 Graham Perrin 2009-02-07 18:58:23 UTC
Created attachment 60010 [details]
demonstrating that mismatch also occurs without a highlight of the corresponding cell
Comment 9 Graham Perrin 2009-02-07 18:59:20 UTC
Created attachment 60011 [details]
demonstrating again that a press of the Enter key loses the user's edition
Comment 10 Graham Perrin 2009-02-07 19:26:58 UTC
Created attachment 60015 [details]
Name Box specifies A1; A1 not highlighted; three neighbours highlighted; the word selected in the input line is not selected in A1
Comment 11 Graham Perrin 2009-02-07 19:54:19 UTC
Considering this issue 98999 

> If selection within input line of Calc is 
> not reflected within the corresponding cell, 
> then an entered change is lost

alongside issue 99001

> highlight is sometimes lost from 
> selected column headings and selected row headings

I wonder whether OOo is reacting strangely before, during, or after 
normal use of the command (Apple) key:

• in combination with tab key (switching between applications)

• in combination with single mouse clicks (non-contiguous selections).

Very difficult to reproduce exactly but in my tests this afternoon/evening I do find that more often than 
not, a selection in the input line is _not_ matched in the corresponding cell (and so, edition is lost).
Comment 12 Graham Perrin 2009-02-07 20:26:07 UTC
Bug issue 99002: 

> double-click wrapped text within a cell that has 
> white space above the text: insertion point is 
> misplaced beyond the aim of the user's double click

Whilst an excess of white space (above wrapped text) may not be visible in examples in this issue 98999 
or issue issue 99001, I wonder whether a misinterpretation of the user's aim (the user's single click) is 
contributory to this issue.