© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
What I think confuses us is the fact that this default behavior is a
regression on the behavior of the previous version, or else there wouldn't
be all these reports and Quantal would show the same wrong behavior.
I have just been packaging a patch someone was kind to write and provide,
as long as it works with the updated packages I'll continue to publish it.
This won't be fixed as have been said by various people, maybe we should
just let it go...
Cheers,
Bruno
No dia 8 de Dez de 2012 23:50, "Łukasz Zemczak" <email address hidden>
escreveu:
> Ok, I think this needs some clarification. The bug is not fixed because
> no dev had time to do it. It was actually fixed quite a long time ago,
> but the fix got reverted. Sadly, bugs like these are really hard to
> 'fix', because those do not really fit the SRU criteria. Stable releases
> can only have SRUable bugs fixed.
>
> To fix this bug, it would mean to change the current *default behavior*.
> Fixes like these are unacceptable after Feature Freeze, so pushing a
> modification like this to Quantal and Precise is something that would
> have to be forced with the design teams and the release teams.
>
> I created a fix (basing my work on what Bruno did), I pushed it to
> compiz, but the design team rejected the change, as it is too late to
> change the default behavior of keybindings. It's a complicated issue. I
> would rather have it fixed as well, but hm, that's not so easy to do
> 'paper-work' wise...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [regression] scale/spread: "Initiate Window Picker for All Windows"
> does not show all windows. It shows only windows from curent
> workspace.
>
> To manage notifications about this bug go to:
> https:/
>