Search onSelect does not fire when inline={true}
See original GitHub issuePressing enter in a Search component does not fire the onSelect function.
Expected Behavior
Search should execute onSelect when inline={true}
Actual Behavior
onSelect function is not executed.
URL, screen shot, or Codepen exhibiting the issue
http://codepen.io/anon/pen/yJqzgO?editors=0010
Steps to Reproduce
- Type something in the inline search box and press enter. Search is not executed.
- Type something in the noInline search box and press enter. Search is executed.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Solved: OnSelect not firing on certain screen
Solved: I have a screen where no OnSelect events will fire, though the Powerapps studio, web or mobile. It is a simple statement....
Read more >Blazor - drop down onchange or onclick events not firing
I am not able to invoke this function at all DoStuff() I have put in MudSelect and MudSelectItem tags, but none of the...
Read more >node_modules/semantic-ui/RELEASE-NOTES.md - GitLab
Checkbox/Dropdown/Search - Fixed issue where using .trigger('change') would not fire native change event. Only triggering event handlers ...
Read more >Getting a value from a function within setTimeout - SitePoint
I'm new to JS and I have recently ran into a problem with the setTimeout function while using the Jquery-UI Datepicker. I would...
Read more >The attribute for input tag"onchange" will not fire, but ...
onchange is only triggered when the control is out of focus. That means you have to click outside of the input field after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can check in a few days.
This is related to passing props to a Grommet component. We are doing it on a need basis.
It seems that Search needs passing props to the input element. Similar to the way we did for the Calendar: https://github.com/grommet/grommet/pull/718/files
would any of you be willing to write a PR for the Search component?