Selecting event in agenda view should call `onSelectEvent`
See original GitHub issueDo you want to request a feature or report a bug?
Feature.
What’s the current behavior?
Selecting events in the “agenda” view do not call the onSelectEvent
.
What’s the expected behavior?
Selecting events in all views should call the onSelectEvent
.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:13
- Comments:7
Top Results From Across the Web
Selecting event in agenda view should call onSelectEvent #743
Selecting events in the "agenda" view do not call the onSelectEvent. What's the expected behavior? Selecting events in all views should call ......
Read more >How to get selected event in React Big Calendar?
The onSelectEvent method gets the full event you clicked on {start, end, allDay, ...rest} , where start and end should both be true...
Read more >Handling Events | Charts - Google Developers
In this case, the code must call getSelection() on the chart to learn what the current selection is. More information is given on...
Read more >onselect event | select event JavaScript
Occurs after some text has been selected in an element. Use the onselect event on the textarea, input:password and input:text elements for cross-browser ......
Read more >react-big-calendar onclick event - You.com | The AI Search ...
An events calendar component built for React and made for modern browsers (read: not IE) and uses flexbox over the classic tables ....
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
Have created pull request https://github.com/intljusticemission/react-big-calendar/pull/852 to handle this issue
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.