[SWINGX-1258] JXLoginPane must not leave the sandbox Created: 26/Jan/10  Updated: 03/Mar/11  Resolved: 03/Mar/11

Status: Resolved
Project: swingx
Component/s: Authentication
Affects Version/s: 1.6.1
Fix Version/s: 1.6.3

Type: Bug Priority: Blocker
Reporter: kleopatra Assignee: Karl Schaefer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 1,258


reported in swingx-demos


Comment by kleopatra [ 18/May/10 ]
      • Issue 1324 has been marked as a duplicate of this issue. ***
Comment by stolsvik [ 18/May/10 ]

May I suggest a component client property or simply an instance method?

Comment by kleopatra [ 19/Oct/10 ]

good suggestion - just wondering why is this (enableCapslock) implemented via a
system property to start with? Karl, Jan?


Comment by Karl Schaefer [ 03/Mar/11 ]

Issue 1258: Removed the current caps lock support and built a new external support class. Removed all system properties and used the support class to handle the caps lock detection. It is now enabled by default and is responsive to the change of the caps lock key during the life span of the login. None of the new code is unsafe, so we no longer need to worry about sand box issues.


Committed revision 3938.

Generated at Fri Mar 24 09:05:05 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.