Issue 22714 - SPI_STATE_SHOWING incorrect for table cells
Summary: SPI_STATE_SHOWING incorrect for table cells
Status: CLOSED FIXED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ru
QA Contact: issues@ui
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2003-11-21 14:08 UTC by remusd
Modified: 2013-08-07 15:15 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description remusd 2003-11-21 14:08:38 UTC 
In spreadsheet, all visible cells to user contains state SHOWING. If horizontal
scrollbar changes its position the cell which are not visible to user still
contains state SHOWING.

Steps to reproduce:
 1. start gnopernicus (latest version from CVS HEAD) with braille monitor enabled.
 2. start SO spreadsheet (resize the window to have only a few cell visible --
this is only for read easy on braille monitor)
 3. make click on a cell. Only visible cells will be reported.
 4. change the position of horizontal scrollbar.
 5. click on a cell. More cells will be now reported.

 4.
Comment 1 ru 2003-11-24 09:42:01 UTC 
.
Comment 2 ru 2003-11-24 11:07:31 UTC 
Ralf -> Oliver: Please have a look. Thanks.
Comment 3 nospam4obr 2003-11-25 11:37:44 UTC 
obr -> sab:

The position of the slider seems not have the slightest influence on
the values returned for spreadsheet cells. 

Even if one changes the slider position before the first table cell
object has been created, states and coordinates are reported as if the
slider were in the left-most position.

So this is not a caching issue in the accessbridge.
Comment 4 sascha.ballach 2003-11-25 13:49:05 UTC 
Hi Ralph,

I think it is not important enough for OOo 2.0, so please change to
OOo later.

Thanks
Comment 5 sascha.ballach 2003-11-26 11:48:48 UTC 
Hi,

after some private mails now I know the importance of this bug, so I
will fix it as fast as possible.
Comment 6 sascha.ballach 2004-02-10 14:12:49 UTC 
fixed in sab013
Comment 7 sascha.ballach 2004-04-07 14:03:23 UTC 
please verify
Comment 8 ru 2004-04-08 12:03:32 UTC 
.
Comment 9 ru 2004-04-08 12:16:01 UTC 
.
Comment 10 ru 2004-04-28 14:13:40 UTC 
.