Document the uselessness of native change events when using widgets #63

Closed
scottgonzalez opened this Issue Oct 26, 2012 · 5 comments

Comments

Projects
None yet
3 participants
@scottgonzalez
Owner

scottgonzalez commented Oct 26, 2012

All widgets that build on top of form controls kill the ability to use the native change event since we programmatically change the field's value. We should mention this in the docs for each widget.

@tjvantoll

This comment has been minimized.

Show comment Hide comment
@mikesherov

This comment has been minimized.

Show comment Hide comment
@mikesherov

mikesherov Jan 12, 2013

Member

@tjvantoll , This is good in wontfix in contribute, but this should also be mentioned in the regular docs as well, as @scottgonzalez describes.

Member

mikesherov commented Jan 12, 2013

@tjvantoll , This is good in wontfix in contribute, but this should also be mentioned in the regular docs as well, as @scottgonzalez describes.

@tjvantoll

This comment has been minimized.

Show comment Hide comment
@tjvantoll

tjvantoll Jan 12, 2013

Member

Alright I can take care of that as well. Thoughts on the best place to put this? I was thinking in the "Additional Notes" section of each widget.

Member

tjvantoll commented Jan 12, 2013

Alright I can take care of that as well. Thoughts on the best place to put this? I was thinking in the "Additional Notes" section of each widget.

@scottgonzalez

This comment has been minimized.

Show comment Hide comment
@scottgonzalez

scottgonzalez Jan 14, 2013

Owner

I think the Additional Notes section works well. We can have a generic note that we include for each widget that needs it.

Owner

scottgonzalez commented Jan 14, 2013

I think the Additional Notes section works well. We can have a generic note that we include for each widget that needs it.

@tjvantoll

This comment has been minimized.

Show comment Hide comment
@tjvantoll

tjvantoll Jan 26, 2013

Member
Member

tjvantoll commented Jan 26, 2013

@tjvantoll tjvantoll closed this Jan 26, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment