|
Bugzilla – Full Text Bug Listing |
| Summary: | problems with 'always ask for password' (was: wrong sequence in provider dialog) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Karsten Keil <karsten.keil> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
provider dialog
Provider dialog in 10.3 |
||
|
Description
Karsten Keil
2005-09-02 12:42:45 UTC
What is the problem? Having to press Shift-Tab instead of Tab? This is a trivial issue. About the default: bug 59836 discusses why it was turned on. I don't think we can revert it, much less at this stage. If it interferes with other options, we can add help texts or, if it always breaks, warning popups. What do you suggest? The sequence is about usability, it's very uncommon and may irritate people, that they change a option, next must go back and than they come again to this option, it's the wrong flow. Add Sigi for a comment. I would say that in case of ISDN we should add a popup if 'always ask password' and Startmode 'onboot' or 'hotplug' is set. It should be say something like: "always ask for password will only work for startmode 'manual'". Can someone out there provide some screenshots of the dialog pages as an attachment? Or are current shots available somewhere in an /Export? Created attachment 48783 [details]
provider dialog
all infos are already given. Reassigning to the new maintainer of yast2-network. Created attachment 156978 [details]
Provider dialog in 10.3
Here is the new Provider dialog in 10.3. The checkbox and password fields are lined up with the username field. It looks pretty usable.
Any Problems with closing this bug?
No apparent problems with closing this at this time as per bug slash day so closing with fixed |