Community
Participate
Working Groups
The new signing tray should show any problems there may be with the signed content.
Rather than open a separate bug, I'll add some other improvements to this bug that were suggested in bug 269079. When we revisit the signing tray, we can look at these > (Also, while not accessability, I'd expect top of that dialog to be aligned > with the top of the table.) Agree, this should be fixed later (although it wasn't aligned in 3.4.x either)... > > 10) On the "Feature Plug-ins" dialog: "Show signing info" has no visial > indication of being a read-only text Not sure what is meant by this. Color? In 3.4.x, one of the read only texts was gray and the other was white. In 3.5, I've made them all white. The reason they are read-only text is so that screen readers will stop in the tab order at each field and read the label. > > 11) On the "Feature Plug-ins" dialog: "Show signing info" should have a label > both indicating what it is to mere mortals and supplying info for the text > readers The labels are there. The coloring/formatting may be confusing. It is colored to look integrated. Signing Date: <value> Signing Certificate: <value> The info was the same in 3.4.x, but everything was colored gray except for the second value. I think the new/consistent coloring looks better, but it's subjective. I'm assuming that people (mere mortals) who wanted to see the signing info must know what it means. (Or else they'll quickly close it like I do ;-) )
assigning milestone for investigation in 3.6
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
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.
