![]() ![]() accessibility frame is misplaced on a secondary monitor on macOS a11y : Screen magnifier shows extra characters (0) at the end JButton accessibility name Menu items with submenus in JPopupMenu are not spoken on macOS Voice over moving JTable column to be the first column JVM crashes VoiceOver : Getting : Invalid location on Editable JComboBox New NSAccessibility peers should return they roles and subroles directlyĬommonComponentAccessibility.createWithParent isWrapped causes mem leakĬreate NSAccessibilityElement implementation for JavaComponentAccessibility TableAccessibility and TableRowAccessibility miss autoreleaseĪccessibility of a table on macOS lacks cell navigation ![]() JNI call of getAccessibleSelection on a wrong threadĬreate implementation for NSAccessibilityOutline protocolĬreate implementation for NSAccessibilityTable protocolĬreate implementation for NSAccessibilityNavigableStaticText protocolĬrash in A11y cursor gets stuck when combobox is closed NSAccessibilityShowMenuAction not working for text editors Incorrect JNI parameters in number conversion in A11Y codeĬreate implementation for NSAccessibilitySlider protocol Incorrect function name in NSAccessibilityStaticText native peer implementation not all KEY_PRESSED events sent when control modifier is usedĬreate implementation for component peer for all the components who should be ignored in a11y interactions Update named used for Java run loop mode Removing remaining JNF dependencies in the sktop module Users can, at their own risk, remove these restrictions by modifying the curity configuration file (or override it by using the system property) and removing "SHA1 usage SignedJAR & denyAfter " from the security property and "SHA1 denyAfter " from the security property. JARs affected by these new restrictions should be replaced or re-signed with stronger algorithms. ![]() =MD2, MD5, RSA keySize < 1024, DSA keySize < 1024, SHA1 denyAfter WARNING: The jar will be treated as unsigned, because it is signed with a weak algorithm that is now disabled by the security property: Signature algorithm: SHA1withRSA (disabled), 2048-bit key To determine if your signed JARs are affected by this change, run jarsigner -verify -verbose -certs on the signed JAR, and look for instances of "SHA1" or "SHA-1" and "disabled" and a warning that the JAR will be treated as unsigned in the output. This exception may be removed in a future JDK release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |