-
Notifications
You must be signed in to change notification settings - Fork 1.3k
afterRenderEvent not fired when in readonly mode #1327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@stanverbakel Thanks for the report. Apparently, this condition should be changed to Please understand I can guarantee the release date of the patch. |
Thanks! I will edit the source files and rebuild so i can use your solution until there is a version released with this fix. Thanks for your fast reply and fix. |
fix: afterRenderEvent doesn't work in readonly mode ( fix #1327 )
Version
TOAST UI Calendar 2nd Edition @Version 2.1.3
Test Environment
Browser: Chrome Version 108.0.5359.99 (Official Build) (64-bit)
Current Behavior
When using the calendar in readonly mode the
afterRenderEvent
is not fired when redering events, this is the code i use:When i switch
isReadOnly
tofalse
it will output 2 events in the console. WhenisReadOnly
istrue
it will not log anything.Expected Behavior
I couldn't find anything in the docs about this event not working in read only mode (some other events in the docs do state
isReadOnly: false
is needed). But the events that needisReadOnly: false
are mostly events that only happen when editing/changing/removing things which isn't posible in read only mode so it makes sense. I think there are many use cases where you want the read only mode in combination with this event.The text was updated successfully, but these errors were encountered: