Closed
Bug 320387
Opened 19 years ago
Closed 18 years ago
link-selected event provides incomplete information
Categories
(Firefox :: Disability Access, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: wwalker, Assigned: ginnchen+exoracle)
References
()
Details
Attachments
(1 file)
|
18.56 KB,
text/x-python
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051214 Firefox/1.6a1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051214 Firefox/1.6a1 Link-selected AT-SPI events do not specify which link was selected Reproducible: Always Steps to Reproduce: 1) Save the following html to foo.html: <html> <p>This is a <a href="foo1">test</a> and here is <a href="foo2">another test</a>.</p> </html> 2) Run the attached test tool in an xterm 3) Run Firefox and point it to foo.html 4) Tab between the two links in foo.html and observe the output in the xterm Actual Results: You will see the following output: object:link-selected -1 0 <CORBA.any of type 'IDL:omg.org/CORBA/Null:1.0'> Expected Results: The '-1' should be the index of the link that was selected (i.e., I believe 0 for the 'test' link and 1 for the 'another test' link.
|
Reporter | |
Comment 1•19 years ago
|
||
part of Bug 304805 cause is https://bugzilla.mozilla.org/show_bug.cgi?id=304805#c2
Fixed by Bug 320388
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
|
|
Reporter | |
Comment 5•18 years ago
|
||
This bug still exists in Bon Echo version 2.0a1.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|
||
Comment 6•18 years ago
|
||
320388 only landed on the 1.8 branch on 2006-03-31, so it missed the 2.0a1 release. You would need to check a nightly http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8/
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
|
|
Reporter | |
Comment 7•18 years ago
|
||
Oops! Silly me didn't understand that the nightly builds kept the same name for the tarballs, leading me to believe a tarball named 2.0a1 was the same as any other tarball named 2.0a1. Sorry about that. I understand the process better now.
You need to log in
before you can comment on or make changes to this bug.
Description
•