|
Bugzilla – Full Text Bug Listing |
| Summary: | Software Manager: The "Accept" button has an inconsistent behavior | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Adrien Plazas <adrien.plazas> |
| Component: | YaST2 | Assignee: | YaST Team <yast-internal> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P4 - Low | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://trello.com/c/DpwEKJEL | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Adrien Plazas
2017-07-18 14:28:43 UTC
Yes, indeed. You basically accept 'do nothing'. The button might be grayed out (like 'save' buttons until there are changes to save). tracking in yast trello board I strongly disagree. "Accept" means "apply all pending changes and then proceed". Depending on how this module is configured, you might get an after-action report, after which the workflow is done, or it might be done immediately. "Cancel" means "discard all changes and get me out of here". So, if you didn't change anything, indeed it appears as if the same thing happens: The program exits. Disabling the "Accept" button in that situation would only add another level of complexity to the user interface for no good reason at all. Why make life harder for the users without a good reason? There is no inconsistency. You just have different expectations. |