Bug: Fix Button JS Rendered
Event Emitted + Update Button JS Demo
#924
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira
http://vjira2:8080/browse/BDS-728
Details
Fixes the Bolt button component's JS logic so the
ready
andrendered
JavaScript events —recently added to the globally shared Bolt base component in v2.x when a component renders initially + re-renders, respectfully— fires as expected.Note: a recent update made to improve the cross-browser rendering of dynamically injected buttons caused this event to stop working as expected (forgot to call
super.rendered()
, however it's worth mentioning that given the virtually undocumented nature of this update and how the how this feature was only just recently added, it's incredibly unlikely this update was getting used downstream just yet.For reference, these events were added in the v2.x release as a possible new pattern to help with consistently binding / rebinding 3rd party JavaScript to a Bolt component in a number of different use cases and situations:
How to test
CC @charginghawk and @krlucas