During my test with ATK support I also found this issue, and I want to
share some discoveries:
* This only happens the first time that you open the Dash. So if you do:
* Open the Dash window. => you can't navigate
* Close the Dash window (ie: clicking with the mouse outside that window)
*
Related branch solves this issue. Kept back because we are on feature
freeze.
** Changed in: unity
Assignee: (unassigned) => Alejandro Piñeiro (apinheiro)
** Changed in: unity (Ubuntu)
Assignee: (unassigned) => Alejandro Piñeiro (apinheiro)
** Changed in: unity
Status: T
Some thoughts after these months:
* After my previous tests, it seems that now the launcher icon always have a
tooltip.
* Although it is long in some cases, Orca users can stop the speech pressing a
key (ie: after just listen "Firefox")
* tooltip seems to be used always for this kind of descr
FWIW, there is another bug with the issues on the interrelationship
between Onboard and Unity. You can find it here 739812
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/783439
Title:
unable to compl
For additional information take a look to bug 852506 comment 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/860805
Title:
Dash doesn't get the focus on pressing the super key first time after
lo
** Tags added: a11y
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/860805
Title:
Dash doesn't get the focus on pressing the super key first time after
login
To manage notifications about this bug
** Description changed:
- crash; was using firefox and entering the menu in unity panel. Panel
- crashes quite often with this WeTab (= tablet PC = ExoPC).
+ Should be fixed in 4.24. As it was identified as a race condition,
+ ensure you don't get any crash after 5 session restarts.
+
+
+ crash;
** Branch linked: lp:~apinheiro/unity/a11y-internal-dash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702700
Title:
BaseWindow on UnityRootAccessible shouldn't be added manually
To manage notifica
Related branch solves the bug. Not proposed to be committed due feature
freeze.
** Branch linked: lp:~apinheiro/unity/a11y-action-for-launcher-icon
** Changed in: unity
Status: Triaged => In Progress
** Changed in: unity
Assignee: (unassigned) => Alejandro Piñeiro (api
Hi. I have been testing this bug yesterday and today.
After all this tests, I can conclude that the problem is related with a
race condition.
First: the original environment where this bug was detected is not
valid. I was only able to reproduce it with a11y enabled, something not
suggested on the
** Branch linked: lp:~apinheiro/unity/bug843280
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843280
Title:
unity-panel-service crashed with SIGSEGV in g_closure_invoke()
To manage notifications ab
** Changed in: unity
Status: In Progress => Fix Committed
** Changed in: unity (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843280
Title:
Public bug reported:
Some of the last recent changes on the a11y framework was moving the
atk-bridge from a module to a library. In that way, the initialization
of the atk-bridge is encouraged to be used as a loadable module
(plugin), and instead use a library. atk-bridge consumers are already
sta
BTW, a new upstream ATK release was done, reverting this change:
https://mail.gnome.org/archives/gnome-accessibility-
devel/2012-March/msg4.html
Thanks for the testing and for pinging me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Note: I have found a user workaround for the problem of the dash not
being closed pressing Esc.
The workaround is the next one:
* Press Alt+F2: Dash is opened, without no focus
* Press Alt+F1: Launcher receives the focus
* Press Esc: no focus in any window
* Press Alt+F2: Dash is open
I had a interesting talking with mhr3 about this bug. It crashes in this
line:
if (GTK_IS_MENU (piea->priv->entry->menu))
So probably entry is NULL, or menu is not anymore a valid object.
Taking a look to the code, this is a custom atk object associated to a
non-GTK object. Taking a look to th
Answer to David: Although based on previous comments, it will really
unlikely that this change will be ready for Natty, I will try to take a
look to this issue, so it could be solved on the future release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Branch linked: lp:~apinheiro/unity/a11y-emit-children-changed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727137
Title:
Missing "children_changed" event emission from the atk support
--
ubunt
I have just uploaded the branch lp:~apinheiro/unity/a11y-emit-children-
changed
It doesn't emit that signal for all the accessibility object,
specifically:
* NuxViewAccessible
* NuxLayoutAccessible
But this is because nux::View and nux::Layout lacks signals reporting
that a child was added.
For your information I have created these bugs:
* Bug 734803: missing signals on nux itself
* Bug 734806: missing children-changed for the objects not included on this
bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: unity
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702672
Title:
NuxUtilAccessible requires to implement support to key event listeners
--
ubu
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727137
Title:
Missing "children_changed" event emission from the atk support
--
ubunt
** Branch linked: lp:~apinheiro/unity/a11y-key-event-listener
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702672
Title:
NuxUtilAccessible requires to implement support to key event listeners
--
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702672
Title:
NuxUtilAccessible requires to implement support to key event listeners
-
This problem was fixed after the last nux and unity update. Closing as
fixed.
** Changed in: unity
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722666
Title:
Branch merged, closing bug
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723806
Title:
LauncherIcon accessibility support requires t
Branch merged, closing bug
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723804
Title:
Require to implement AtkSelection on the Laun
Branch merged, closing bug
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722660
Title:
Keyboard navigation: no public API to know th
Ups, I missed that notification on my review of the branch, my bad
It should not required to change finalize for dispose, this line on the
finalize
atk_object_notify_state_change (ATK_OBJECT (piea), ATK_STATE_DEFUNCT,
TRUE);
is wrong.
ATK_STATE_DEFUNCT is a state of the accessible object when
** Changed in: unity
Status: Triaged => In Progress
** Branch linked: lp:~apinheiro/unity/Bug734806
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734806
Title:
Missing "children_changed" eve
** Changed in: nux
Status: New => In Progress
** Changed in: nux
Assignee: (unassigned) => Alejandro Piñeiro (apinheiro)
** Branch linked: lp:~apinheiro/nux/Bug734803
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nux
Status: New => Confirmed
** Changed in: unity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/735645
Title:
Timestamp field on the event stru
After a brief talk with Alex Launi on IRC, and as this is a nux bug, we
conclude that Jay is usually a good recipient of nux bugs, so I'm
assigning the bug to him.
As I said on the description, note that I was able to workaround this
bug (see unity_util_accessible.ccp::atk_key_event_from_nux_event
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734806
Title:
Missing "children_changed" event emission from the atk support for the
** Changed in: nux
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734803
Title:
Missing child addition signals on nux::Layout and nux::View
--
ubuntu-bug
** Changed in: unity
Status: Confirmed => In Progress
** Branch linked: lp:~apinheiro/unity/launcher-icon-also-focused
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729165
Title:
Regression:
** Changed in: unity
Status: Confirmed => In Progress
** Branch linked: lp:~apinheiro/unity/launcher-icon-also-focused
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727133
Title:
Orca doesn'
** Summary changed:
- Accessibility object parent-child hierarchy is broken
+ Accessibility object parent-child hierarchy on unity is broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727908
Title
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727133
Title:
Orca doesn't report that the Launcher receives the focus
--
ubuntu-bugs
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727908
Title:
Accessibility object parent-child hierarchy on unity is broken
--
ubunt
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729165
Title:
Regression: Orca doesn't speech out the selection changes on the
Launch
Rodrigo is the one that implements most of the a11y support on the panel
service, while I was more focused on unity itself. So I will reassign
this bug to him.
** Changed in: unity
Assignee: Alejandro Piñeiro (apinheiro) => Rodrigo Moya (rodrigo-moya)
--
You received this bug notificat
The title of the bug seems to suggest that the at-spi crash, but reading
the bug description:
"Tiping `top` on the tty1, I saw "at-spi-registry => 89% CPU" (on 3.3GHz
quad-core)
I launched the command `sudo skill at-spi-registry` and the "tty8" became
usable again."
If at-spi-registry is listed
And related to this (please forgive me if this is not the proper place
to ask this)
Anyone knows if there is a key combination to open the dash ? (in the
same way that pressing Alt+F1 opens the Launcher).
I was not able to find it, and this should be also required in order to
have a full dash key
Just a question, what is the difference between this bug and bug 608132?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727714
Title:
Dash needs keyboard navigation
--
ubuntu-bugs mailing list
ubun
Yes you are right I have just tested the Super key, and it opens the
dash.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/608132
Title:
[dash] Keyboard navigation not implemented as specified
** Changed in: unity
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727137
Title:
Missing "children_changed" event emission from the atk support
--
ubuntu-bu
As usual, reassigning unity-panel-service accessibility bugs to Rodrigo
Moya
Also adding the tag a11y
** Tags added: a11y
** Changed in: unity
Assignee: (unassigned) => Rodrigo Moya (rodrigo-moya)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Tags added: a11y
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/731651
Title:
The Unity panel service Does not connect to the
INDICATOR_OBJECT_SIGNAL_ACCESSIBLE_DESC_UPDATE signal.
--
ubuntu-b
I think that the problem is this bug:
https://bugs.launchpad.net/unity/+bug/727137
Due this bugs, sometimes it is required a manual atk object exploration
in order to have the proper accessible objects (so the signals related).
While solving this bug I didn't notice it because I usually checked
*** This bug is a duplicate of bug 729827 ***
https://bugs.launchpad.net/bugs/729827
** This bug has been marked a duplicate of bug 729827
at-spi-registry consumes most of the CPU and make the system unusable on
Natty
* You can subscribe to bug 729827 by following this link:
https://bugs
Public bug reported:
Binary package hint: unity
Recently AtkSelection and other selection stuff was added on the
Launcher, and orca properly speeched out the selection changes when the
key nav mode started on the launcher.
At first I thought that it was due the broker parent-child hierarchy
(see
** Branch linked: lp:~apinheiro/unity/fix-parent-child-hierarchy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727908
Title:
Accessibility object parent-child hierarchy is broken
--
ubuntu-bugs ma
** Changed in: unity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727140
Title:
Several ATK_STATE(s) not properly used on the accessibility framework
--
ubuntu-bug
** Changed in: unity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727137
Title:
Missing "children_changed" event emission from the atk support
--
ubuntu-bugs maili
** Changed in: unity
Status: New => Confirmed
** Changed in: unity
Assignee: (unassigned) => Alejandro Piñeiro (apinheiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727133
** Changed in: unity
Status: New => Confirmed
** Changed in: unity
Assignee: (unassigned) => Alejandro Piñeiro (apinheiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729165
** Changed in: unity
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727908
Title:
Accessibility object parent-child hierarchy is broken
--
ubuntu-bugs mailing
** Changed in: unity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727131
Title:
Required a formal and brief accessible name for the launcher menu icon
--
ubuntu-bu
As the one reporting the bug:
Well I have just tested it and this specific aspect of the Launcher
keyboard navigation seems to be working now (but now others like quick
list navigation)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
While testing:
https://code.launchpad.net/~rodrigo-moya/unity/fix-740360/+merge/55319
I detected a crash. As you can't upload a file to a merge proposal (at
least I don't know how), Im uploading a gdb backtrace here.
It seems a infinite loop. Although it is really big, it is truncated.
** Attac
Just a comment here: David already mentioned it on IRC, but probably it
would be good to add a new item on the initial tasks:
- Check if the startup time with a11y enabled is worse or not
- Apply previous items with a11y enabled
Opinions?
--
You received this bug notification because you
*** This bug is a duplicate of bug 810033 ***
https://bugs.launchpad.net/bugs/810033
** This bug has been marked a duplicate of bug 810033
Accessibility support not initialized on Oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: null
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702672
Title:
NuxUtilAccessible requires to implement support to key event listeners
To manage n
Sorry for the delay. In the end the solution was one line.
panel_indicator_entry_accessible_ref_child is a implementation of
atk_object_ref_child, and as the name implies, it supposes that a
reference count is required.
The branch that I have just linked to this bug also add some NULL check
condit
** Changed in: unity
Status: Confirmed => Fix Committed
** Changed in: unity (Ubuntu Oneiric)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/817477
Tit
I also had this problem using Ubuntu oneiric. I have this eclipse
packages installed:
ii eclipse3.5.2-11ubuntu1
Extensible Tool Platform and Java IDE
ii eclipse-jdt3.5.2-11ubuntu1
Well, I can't re-open this bug, but just to comment that using eclipse
directly from the official webpage is working properly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620516
Title:
java.lang.Un
*** This bug is a duplicate of bug 810033 ***
https://bugs.launchpad.net/bugs/810033
** Tags added: a11y
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813492
Title:
a11y code should switch to g
*** This bug is a duplicate of bug 817477 ***
https://bugs.launchpad.net/bugs/817477
** This bug has been marked a duplicate of bug 817477
unity-panel-service crashed with SIGSEGV in main_arena()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I have just relate this bug to a branch. Anyway, in order to work well
with orca, it requires this two bugs fixes:
https://bugzilla.gnome.org/show_bug.cgi?id=657732
https://bugzilla.gnome.org/show_bug.cgi?id=657646
The big problem here is that we are really long away from the oneiric
feature free
** Branch linked: lp:~apinheiro/unity/a11y-internal-dash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/731403
Title:
Unity Dash not accessible
To manage notifications about this bug go to:
https://
** Changed in: unity
Status: Triaged => In Progress
** Changed in: unity
Assignee: (unassigned) => Alejandro Piñeiro (apinheiro)
** Branch linked: lp:~apinheiro/unity/a11y-quicklist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Branch linked: lp:~apinheiro/unity/Bug851103
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/851103
Title:
a11y support on Unity is broken
To manage notifications about this bug go to:
https://bug
** Changed in: unity
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/851103
Title:
a11y support on Unity is broken
To manage notifications about this bug go to
The branch related was merged some weeks ago. Closing the bug.
Sorry the delay, I should have closed it some weeks ago.
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was solved some time ago, I will copy here a private mail from
Jay dated of 27 January:
"In Nux/WindowCompositor.cpp/.h I added the following signals:
sigc::signal sigVisibleViewWindow
sigc::signal sigHiddenViewWindow
Both signals are emitted when a BaseWindow becomes visible or
BTW, I still have pending to use this stuff to solve bug 702700, but in
theory those signals added would be enough
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702702
Title:
BaseWindow should notif
*** This bug is a duplicate of bug 727140 ***
https://bugs.launchpad.net/bugs/727140
** This bug has been marked a duplicate of bug 727140
Several ATK_STATE(s) not properly used on the accessibility framework
* You can subscribe to bug 727140 by following this link:
https://bugs.launchpad
** Branch linked: lp:~apinheiro/unity/Bug727140
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727140
Title:
Several ATK_STATE(s) not properly used on the accessibility framework
--
ubuntu-bugs mai
** Changed in: unity
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/731403
Title:
Unity Dash not accessible
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
** Changed in: unity
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727140
Title:
Several ATK_STATE(s) not properly used on the accessibility framework
--
ub
** Changed in: unity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727140
Title:
Several ATK_STATE(s) not properly used on the accessibility framework
--
ed in: unity (Ubuntu)
Assignee: (unassigned) => Alejandro Piñeiro (apinheiro)
** Changed in: unity (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/70
After checking this a little, just to comment that this error message
shouldn't be the cause of the segmentation fault.
I was able to reproduce it, but unity works fine (warning there, but
works fine).
Although I still plan to avoid that warnings, take into account that
likely it will not fix the
The branch that I have just linked solves that warning
Anyway, as I said, I really doubt that this Segmentation Fault caused by
this reason.
** Branch linked: lp:~apinheiro/unity/Bug705442
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I forgot to close the bug when I wrote the previous message. Doing now.
** Changed in: unity (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705442
Rodrigo and me were talking about this.
Although the comments on the bug are still valid, we found a issue with
that. GTK doesn't expose the path of the modules. So in order to load by
hand the module, we would require to use a fixed path, as Firefox does
(the example I used). This is somewhat hac
** Changed in: unity (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711183
Title:
Accessibility support on the service panel should also load GAIL
--
Due some other things with more priority (Launcher), I will change the
status to New. I will go back to this bug once I finish that other tasks
** Changed in: unity
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Changed in: unity (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702672
Title:
NuxUtilAccessible requires to implement support to key event listeners
--
In order to try this new functionality I tried the branch bzr branch lp
:~unity-team/nux/nux.event-fixes/
Unfortunately, I was not able to use it, as for any reason with this
branch the Launcher is not visible at all, and pressing Alt+F1 doesn't
provide the keynavmode. Don't know if caused for th
Today I noticed that the branch nux.event-fixes was updated, so I tried
it again. I have the same back luck. The Launcher is not visible at all,
and it doesn't get the keynavmode pressing Alt+F1 (or at least I can't
use it)
So I tried the option of apply that commit (support for accessibility)
on
** Branch linked: lp:~apinheiro/unity/atk-selection
** Changed in: unity
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723806
Title:
LauncherIcon accessibility sup
** Branch linked: lp:~apinheiro/unity/atk-selection
** Changed in: unity
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723804
Title:
Require to implement AtkSelect
** Branch linked: lp:~apinheiro/unity/atk-selection
** Changed in: unity
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722660
Title:
Keyboard navigation: no pu
96 matches
Mail list logo
