Skip to content

Latest commit

 

History

History
48 lines (25 loc) · 4.4 KB

CHANGELOG.md

File metadata and controls

48 lines (25 loc) · 4.4 KB
Raw

@jspsych/plugin-image-slider-response

1.1.3

Patch Changes

  • #3184 9acfa29c Thanks @bjoluc! - Point to source maps via canonical unpkg URLs in NPM-published browser builds. This prevents 404 errors when using redirecting CDN URLs (as described in #3043).

1.1.2

Patch Changes

1.1.1

Patch Changes

  • #2632 a17f423f Thanks @bjoluc! - Improve browser compatibility when loading via unpkg.com, i.e. when using the dist/index.browser.min.js build artifact.

1.1.0

Minor Changes

Patch Changes

  • #2359 d8b23ca3 Thanks @jodeleeuw! - When require_movement is true, allow changes to the slider using the keyboard to enable the button (#1783).

1.0.0

Major Changes

  • #2183 c8760b1 Thanks @jodeleeuw, @becky-gilbert, @bjoluc! - jsPsych is now fully modular, with individual NPM packages for the core library, plugins, and extensions.

    To support this change, we've made a number of breaking changes. We've added a guide for migrating from version 6.x to 7.x to the documentation, and updated the hello world tutorial with instructions for configuring jsPsych in three different ways. In addition to enabling package management, some of the benefits that this change provides include an improved developer experience with IntelliSense code hints, proper encapsulation of jsPsych so that multiple instances can be run on the same page, and easier integration with modern JavaScript tools like bundlers.

Minor Changes

  • #2143 7fa8f26 Thanks @jodeleeuw! - When require_movement is true a 'touchstart' event or a 'mousedown' event will now enable the button. This means that this parameter will work on mobile devices, and that the button will become enabled as soon as the paricipant interacts with the slider rather than after they click and release the slider.
  • #2129 f37f64a Thanks @jodeleeuw! - All duration measurements, including response times, are now rounded to the nearest millisecond. We changed this because the precision that performance.now() generates is misleading in this context and removing the (often very long) decimal component of the measurement will save space in the data files.

Patch Changes