This component follows Semantic Versioning (aka SemVer), visit (http://semver.org/) to learn more about it.
- Add Setter/getter manually invalid input. Thanks to @herberthobregon.
- When source changes update suggestions. Thanks to @programmer4web.
- Fix removed the
readOnlyattribute from thefocusedproperty. This was causing that the value was not being updated. Thanks to @programmer4web.
- New
selectedproperty has been added that exposes the current selected value. Thanks to @programmer4web.
- Suggestion list will now work properly if text-property or value-property not set to default value. Fixes #66 and #103. Thanks to @christianaye
- Component now exposes
disabledoption. Fixes #96. Thanks to @JaySunSyn. focusedproperty exposed. Fixes #102. Thanks to @programmer4web.
- Component now exposes
readOnlyoption.
- Show results on focus is now disabled by default. The new feature introduced in previous version changed the default
behavior for everyone and that might not be the best solution in all cases. So for that reason, by default, suggestions
are not displayed onfocus. If you want to add that behavior again, use the following option:
show-results-on-focus. Sorry for that! :) - New option
autocapitalizehas been added (thanks @ardean).
- Suggestions will be displayed (if available) on focus (thanks to @nomego)
- New CSS mixin to give custom styles to suggestions (
--suggestions-item); paper-itemslotprefixis also now exposed and it can be used (thanks to @nomego)
- Added a new boolean option
highlight-firstto bothpaper-autocompleteandpaper-autocomplete-suggestionsthat when set, it will always highlight the first result each time new suggestions are presented.
- It is now again possible to add a custom
paper-inputsuffix. See the new demo.
- Removed duplicated
auto-validateattribute from paper-autocomplete (thanks to @kaseyhinton). - Fixed regression:
onClear()now triggers'autocomplete-reset-blur'event (as is documented in the API) and not the event'autocomplete-reset'. - Added integration with SauceLabs so now test can be run against multiple platforms and browsers.
- This version does not contain any breaking change in the API. The breaking changes come from limitations in styling
when working with
<slots>and::slotted(). Due to this limitations, when working with custom templates, you must put your<style>inside the custom template<template>tag.
- The component has been transformed to work in hybrid mode, which means that the component is now compatible with both Polymer 1.x and Polymer 2.x.
*Special thanks to everyone who has contributed to this version. Specially @ajbarriosleon, @kamte who did most of heavy-lifting at the beginning of this new version.
tabindex="-1"was added to the clear button, so you can no longer use tab to focus it. This is a temporary workaround until this issue is fixed: PolymerElements/paper-input#324 .
- Private property
_bindedFunctionsinsidepaper-autocomplete-suggestionswas being shared between all instances. This now has been solved thanks to @plequang.
- Updated
README.mdto clarify compatibility with Polymer 1.x and 2.x.
- Moved
<style>tags inside the<template>tag, to avoid leaking styles and to be inline with latest Polymer recommendations (thanks to @alejost848). - Demo pages has been fixed so now all demos work in IE/Edge.
- Event name when clicking in the clear button was wrong. Now event name matches the one in the documentation:
autocomplete-reset-blur(thanks to @orenagiv).
- Removed
mocha,chaiandsinonfrom the list of bower dependencies.
- X button to clear is now a paper-input suffix.
- Hiding native clear X button in the input in IE/Edge. Fixes #24
paper-autocompletenow exposes a new CSS mixin that can be used to style the suggestions popup:--paper-autocomplete-suggestions-wrapper.- Updated wrong CSS mixin value in the
paper-autocomplete-suggestionselement.
Thanks to @jimivdw.
- The
--paper-input-container-focus-colordefault value is no longer hardcoded to a specific color (#2196f3). Now it is set by default tovar(--primary-color).
paper-autocompletenow has a new option:placeholder.
- Fixed a typo in the code that was causing an error when calling
hideSuggestions()method.
- Added new option
namefor integrating the autocomplete with aniron-form.
- Fixed option disableShowClear, option was not being behaving as documented, added tests for same. Thanks to @vidhill.
- Fixed when user pressed UP or DOWN with no results, a JavaScript error was thrown.
- Preventing the focus to switch from input field when autocomplete-suggestions is a child of an element with tabindex and user clicks in the scrollbar to scroll over results.
textandvaluewere not set when a selection was made. This is now fixed.
- Bumping version to avoid a possible version conflict with Beta and RC versions.
paper-autocompletehas been split in two components:paper-autocompleteandpaper-autocomplete-suggestions. The second one is a new component containing all the logic related to the popup with suggestions: search, selection, etc. This allows using the autocomplete functionality with any input field.- Selection with the keyboard has been changed: now you can go from the first/last to the last/first pressing up/down keys.
- Added test to the component (at this moment, two A11Y tests are failing when the component is test with ShadowDom, this issue is being investigated).
- When user pressed
leftorrightkey when a component was highlighted, the state was reset. Now the popup is ignoring those key events.
- It is now possible to specify custom templates for suggestions.
- You can now specify your own
queryFnto filter suggestions according to your needs. - Added
CHANGELOG.md
- Property
useShadowDomhas been removed because now the component works in both modes without it. You can just remove it from your apps. However, if you have it, nothing will break, it will just be ignored.
setOption()method was not taking into accounttextPropertyandvaluePropertyoptions.