All notable changes to this project will be documented in this file.
- Updated some links in the documentation. No functionality was changed.
- Fixed an issue where the autocomplete widget removes classes from a container (#116).
- Export
autocomplete.cssinpackage.json(#113)
- Provide ESM builds so that modern bundlers and frameworks can take advantage and use the package as ESM instead of CommonJS or UMD.
- Use textContent for CSP compliance (#111)
- Allows postcss-import to know which default file to use (#109)
- Detach custom autocomplete container during plugin initialization if it was already appended to the DOM (issue #103).
- Improved performance during keyboard navigation (up/down keys) in the autocomplete dropdown. Instead of re-rendering suggestions, the widget now only updates the relevant element attributes.
- Due to the above optimization, the
renderandrenderGroupfunctions will now only be invoked on the initial render and when text in the autocomplete changes. - Modified the
preventSubmitoption, which now accepts enum values for more granular control. Previously a boolean, it now acceptsNever(form submission is not prevented),Always(form submission is always prevented), andOnSelect(form submission is only prevented when a value is selected in dropdown).
- Resolved an issue where the autocomplete widget was erroneously re-displayed after selection on Firefox Mobile Browser.
- Added a new parameter to
AutocompleteResultthat allows to manually display autocomplete or trigger updates without an event like 'click' or 'keydown'
- Rollup configuration
- Added a changelog to simplify the process of tracking updates.
- Changed the event triggering the autocomplete widget from
keyuptoinput, resolving issues listed below. - The widget can now be displayed on mouse clicks when the
clickoption is correctly configured and passed to autocomplete.
keysToIgnoreproperty is removed and the newkeyupproperty should be used instead.
- The mouse paste operation now activates the autocomplete feature as intended.
- The autocomplete widget is now correctly activated when input values are altered on mobile devices without using the virtual keyboard (by voice or auto-correction).
- The widget will now properly reattach to its original parent container when a custom container is provided for autocomplete, instead of attaching to the body (issue #83)