Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348998

Summary: Network Connections Dialog:checkboxes make not much sense (usability)
Product: [Eclipse Project] Platform Reporter: Bernhard Merkle <bernhard.merkle>
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: prakash
Version: 3.7   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
checkboxes have readonly semantic but displayed as editable none

Description Bernhard Merkle CLA 2011-06-10 04:59:59 EDT
Build Identifier: 

please see the attached screenshot of "Network Connections" dialog.

the checkboxes (marked red) really make currently no sense as:

- the are displayed as editable but in reality read-only 
so please also make the background grey to display the read-only behaviour

- however what you really want to display I think this (e.g. in the Proxy entries table) is: am I active or not. So togglein the active provieder also toggles the checkboxes. (however as mentioned above: this is a status information and not editable to readonly seem the right displaying style).

I would rather prefer to have the table "proxy entires" displayed with editable entries and deactivated entries, depending on the status of "Acitve Provider" box.



Reproducible: Always
Comment 1 Bernhard Merkle CLA 2011-06-10 05:00:45 EDT
Created attachment 197758 [details]
checkboxes have readonly semantic but displayed as editable

checkboxes have readonly semantic but displayed as editable
Comment 2 Bernhard Merkle CLA 2011-06-10 05:22:50 EDT
please also see bug#349000 and bug#349001 for a redesign of the dialog
Comment 3 Bernhard Merkle CLA 2011-06-10 05:27:08 EDT
not sure if bug#348998 bug#349000 bug#349001
belong to Update and hence to equinox/p2. If yes feel free to move them there.
Comment 4 Lars Vogel CLA 2019-11-14 03:38:46 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.