I did a trivial hard-code binding fix for this issue in https://code.launchpad.net/~sil2100/unity-2d/trunk.lp839628 - but as Saviq noticed, this might not quite be the solution we are looking for. It's now a question who ultimately should be the one to pick up the F10 handling - the application, or unity? My fix makes unity-2d-panel be the one in control.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839628 Title: F10 doesn't start keyboard navigation to the panel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/839628/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
