Issue 103596 - Tooltips do not issue a11y events when showing
Summary: Tooltips do not issue a11y events when showing
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOO310m11
Hardware: Sun All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@sw
URL:
Keywords: accessibility
: 104294 (view as issue list)
Depends on:
Blocks:
 
Reported: 2009-07-16 21:56 UTC by williewalker
Modified: 2013-08-07 14:44 UTC (History)
2 users (show)

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


Attachments
Simple test application (274 bytes, text/plain)
2009-07-16 21:57 UTC, williewalker
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description williewalker 2009-07-16 21:56:29 UTC
When one presses Ctrl+F1 to cause a tooltip to appear, no a11y event is issued.
 The events only seem to be issued when the tooltip goes away (and even that
seems intermittent for some reason).

To reproduce:

1) run the to-be-attached test application.  
2) run soffice
3) press Alt+F then Ctrl+F1 to force a tooltip to appear.

Event output should be emitted by the test application when the tooltip appears.
 In particular, I'd expect an object:state-changed:showing event with a detail1
value of 1 when the tooltip appears.
Comment 1 williewalker 2009-07-16 21:57:10 UTC
Created attachment 63591 [details]
Simple test application
Comment 2 eric.savary 2009-09-21 15:08:34 UTC
Set keyword
Comment 3 malte_timmermann 2009-12-03 10:29:18 UTC
Please fix in 3.3...
Comment 4 philipp.lohmann 2009-12-03 10:33:58 UTC
Oh great :-( a what of who event ? An how do I run that script ?
Comment 5 joaniediggs 2009-12-03 12:00:46 UTC
> Oh great :-( a what of who event ? An how do I run that script ?

It's not all THAT bad, now is it? ;-) ;-)

An accessibility event indicating that the state of the tooltip has changed from
not showing to showing.

Via a python interpreter on a machine running the GNOME desktop. Alternatively
you could get the same information via Accerciser.
(http://live.gnome.org/Accerciser) Accerciser is an awesome tool if you're going
to be working on accessibility issues for OOo in GNOME.
Comment 6 joaniediggs 2009-12-04 15:59:54 UTC
williewalker and I are going over bugs and realized I'd filed a dup of this one.
Sorry.

Given pl's questions and my mention of Accerciser, here is the text from my bug
in the hope that the details are of some use:
===============================================
Steps to reproduce:

1. Launch Writer and Accerciser

2. Turn event monitoring on in Accerciser

3. In Writer, cause a toolbar tooltip to appear either by hovering the mouse
over a button or by moving focus to it and pressing Ctrl+F1

Expected results: An object:state-changed:showing event (detail1 == 1) would be
emitted.

Actual results: An object:state-changed:showing event is not emitted, though we
do get an object:state-changed:visible (detail1 == 1) event.

Impact: All of the other toolkits and applications (that I am aware of) which
expose tooltips via at-spi, emit an object:state-changed:showing event. Orca at
the moment does not listen for object:state-changed:visible events -- and it
won't until we've been able to ascertain that doing so will not impact
performance across the board.

Therefore, what I am hoping is that it will be quite easy for you to emit this
event at the same time you emit the object:state-changed:visible event. If so,
things should JustWork(tm). If it's more difficult than that, please let me know
and I'll start doing performance analysis. Thanks in advance!
Comment 7 joaniediggs 2009-12-04 16:00:47 UTC
*** Issue 104294 has been marked as a duplicate of this issue. ***
Comment 8 philipp.lohmann 2010-02-24 18:45:32 UTC
It seems we don't even "emit" the state-changed:visible event but that gtk does
that on its own when the GtkWindow associated with the tool tip gets shown.

I'll look a bit further.
Comment 9 philipp.lohmann 2010-02-25 11:39:43 UTC
Yes, this is so.
Comment 10 philipp.lohmann 2010-02-25 11:41:10 UTC
added a state change for "showing" in this case.

Fixed in CWS vcl110
Comment 11 philipp.lohmann 2010-03-26 15:13:17 UTC
please verify in CWS vcl110
Comment 12 eric.savary 2010-04-09 17:24:09 UTC
Verified in CWS vcl110
Comment 13 malte_timmermann 2010-06-23 12:18:05 UTC
Closing accessibility issues which have been fixed, verified and integrated...