Skip to content

Releases: bitwalker/keys.js

0.2.1

28 Jan 02:18
@bitwalker bitwalker
0.2.1
782b0a3
Compare
Choose a tag to compare
0.2.1 Latest
Latest

CHANGELOG

  • The keypress event is now available in the handler in case you need access to it.
  • Added ability to unregister a handler
  • Changed license to LGPLv2.1
Assets 2
Loading

Version 0.2.0

03 Jul 04:45
@bitwalker bitwalker
0.2.0
32f1b7d
Compare
Choose a tag to compare
Version 0.2.0

CHANGELOG

Breaking Changes

  • Keys.js now loads itself into the Keys namespace on initialization. You will have to make sure that you either create aliases for the Bindings, Combo, and Key classes, or reference them with the fully qualified name, ex. Keys.Bindings.

Newly Added

  • Added Bindings.load method, which allows you to fully specify both bindings and handlers for your entire application with one call. This can drastically simplify configuration code. See documentation for examples and more detail.
  • Added description property to bindings, and can now be passed as a parameter to Bindings.add, or as a property of the specification object passed to Bindings.load. This can be used to provide a friendly name for your presentation layer, should you wish to list bindings programmatically.

New Behavior

  • By default, handlers are not executed in the context of input, textarea, or select elements. Can be overridden with isGlobal boolean flag as last parameter provided to Bindings.registerHandler, or as a property of the specification object passed to Bindings.registerHandlers, and Bindings.load.

Bugs Fixed

  • Do not prevent default input behavior when a binding is unhandled
  • Fix case-sensitivity issue in Key.fromName
Assets 3
Loading