What | Removed | Added |
---|---|---|
Summary | Service Manager: applying loses selection | yast2-services-manager: applying changes loses selection |
Flags | needinfo?(giecrilj@stegny.2a.pl) | |
Severity | Normal | Minor |
With a lot of guesswork I tried to reproduce this, and here is what I observed: After applying a change to the currently selected service, the table content is reloaded. The previously selected table item is no longer selected; it is now a different one, probably the (case-insenstive) alphabetically first one, "accounts-daemon". But that's not the first visible item in that table; that would be "Modem-Manager" which is the case-sensitive alphabetically first one. I am not sure how useful it would be to select the previously selected one again; we'll have to discuss that internally. But at the very least the behavior is inconsistent (case-sensitive vs. case-insensitive first item).