You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This element is awesome, congratulations for its contributors!
However, my usage requires that the element to not be constrained by the source values, allowing custom inputs there too.
This way, the autocomplete should act only as a helper to get to the result faster.
Can it be done today with some config property? I am currently using autocompleteElement.$.autocompleteInput.value to accept any value, but this is a really dirty workaround.
The text was updated successfully, but these errors were encountered:
I agree I think it would be useful. How do you expect this should work? What would you expect to happen with the value? value === text === value in the input field?
This element is awesome, congratulations for its contributors!
However, my usage requires that the element to not be constrained by the source values, allowing custom inputs there too.
This way, the autocomplete should act only as a helper to get to the result faster.
Can it be done today with some config property? I am currently using
autocompleteElement.$.autocompleteInput.value
to accept any value, but this is a really dirty workaround.The text was updated successfully, but these errors were encountered: