Skip to content

Releases: alpinejs/alpine

v2.3.4

15 May 14:30
408d8d6
Compare
Choose a tag to compare

Fixed

  • x-on on an x-fored element wasn't being registered, fixed now: #418
  • Fix cursor placement bug on Safari (back out old fixing strategy) #424
  • Ignore extra whitespace in :class="{...}" bindings #437
  • Mirror VueJS's behavior for binding false/null/undefined values to attributes #486

v2.3.3

04 May 15:23
Compare
Choose a tag to compare

Fixed

  • Obscure mutation observer bug when multiple mutations from different parts of the dom happen AND the first mutation was unrelated to the rest, a return statement inside a for loop would stop the rest of the mutations from being processed. We changed it to continue so all mutations would get processed and we are good to go! #456

v2.3.2

04 May 01:30
Compare
Choose a tag to compare

Fixed

  • <input type="hidden" x-model="foo">: x-model wasn't working on "hidden" input elements in Safari #453

v2.3.1

24 Apr 17:53
Compare
Choose a tag to compare

Added

  • Alpine.version property to get the current version of Alpine programmatically
  • CSP notes in the readme

Fixed

  • x-model issues with new Safari fix #403

v2.3.0

21 Apr 02:11
Compare
Choose a tag to compare

Added

  • Added NPM version to README #330
  • Added "nomodule" pattern to docs for IE11 build #365
  • Added .self event modifier: @click.self="foo" (will only run "foo" if the event originated on the listening target) #379
  • Refactored structure of x-for system #362

Fixed

  • All Chromium and WebKit browsers were causing "keydown" listeners to fire on "autocomplete" #389
  • Accessing outer loop variables from inner loop variables was broken #357
  • Now we're able to bind :value on an <input type="radio"> WITH x-model as an attribute #315
  • $nextTick was finishing before certain refreshes were finished updating #341
  • There was a bug in Safari that caused x-model inputs to make the cursor jump when the value was updated #367

v2.2.5

02 Apr 04:58
fd9eddd
Compare
Choose a tag to compare

Fixed

  • x-if was broken inside of x-for because of recent changes to how x-if is initialized (we moved away from using mutation observer to drive added x-if elements) #328

v2.2.4

31 Mar 17:32
Compare
Choose a tag to compare

Fixed

  • reactivity inside of x-if was broken. Fixed in: #324

v2.2.3

30 Mar 17:22
Compare
Choose a tag to compare

Fixed

  • You can now nest x-for loops (as long as they are wrapped in elements) #316
<template x-for="item in items">
    <div>
        <template x-for="subItem in item.subItems">
            <div x-text="subItem"></div>
        </template>
    </div>
</template>

v2.2.2

29 Mar 19:26
7caf2be
Compare
Choose a tag to compare

Added

  • x-on:foo.debounce.150ms and x-model.debounce #153
  • Make $watch support nested properties better #292

Fixed

  • Fixed reactivity in IE 11 #314
  • Fixed Mutation Observer issue with x-if inside an x-for #194
  • Fixed debounce core issues
  • Removed useless $nextTick stack clearing #289
  • Fix x-model.number casting to be more like Vue #285

v2.2.1

16 Mar 20:40
Compare
Choose a tag to compare

Added

  • A mechanism for third-party libs to defer loading Alpine until they are finished doing there thing (Livewire lol)
window.deferLoadingAlpine = callback => {
    // When some condition is met, call callback() and Alpine will load
}