Inconsistent previous lens/scope keybinding behavior for the command lens

Bug #1158236 reported by Łukasz Zemczak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Fix Released
High
Nick Dedekind
unity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

A regression introduced by 100 scopes it seems.

When the command lens is opened (alt+f2), according to the respective autopilot test test_command_lens test_ctrl_shift_tab_switching, a ctrl+shift+tab keybinding should switch to the video lens (the last lens in the lensbar). In our case that should be maybe something different, but still - pressing ctrl+shift+tab in the command lens does nothing.

Tags: 100scopes

Related branches

Changed in unity:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Nick Dedekind (nick-dedekind)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:~unity-team/unity/libunity-7.0-breakage at revision None, scheduled for release in unity, milestone Unknown

Changed in unity:
status: Triaged → Fix Committed
Changed in unity:
status: Fix Committed → Fix Released
Changed in unity (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.