-
Notifications
You must be signed in to change notification settings - Fork 552
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
[BUG?] issues with 'change.querybuilder' event #556
Comments
"change.queryBuilder" does not exist yet #498 I tried your fiddle with "afterDeleteRule.queryBuilder" and it works very well |
sorry was editing the comment. so things might get wonky with this.... if the event doesnt exist yet then what event is being fired to output "changed" in the log area? https://jsfiddle.net/42t6chv6/3/ #confused |
latest fiddle https://jsfiddle.net/42t6chv6/5/ still no idea where edit found it..: https://github.com/mistic100/jQuery-QueryBuilder/blob/dev/src/core.js line 200 odd.
so probably still a WIP i guess |
No it's not a WIP. This event is just the input/select events bubbling up in the DOM, it is not triggered by the builder but by the browser. |
so best way to do a "change" would be something like
(i just took all the api "after" events) also using a debounce script to only fire once heres an events fiddle for anyone else thats interested with the "after" events |
nice, always a pleasure to know how it is integrated. |
So what William suggests can be used until global "change" event has been implemented in 2.4.5 release? |
of course, this is only existing events |
Thanks, just confirming :), |
Hey Damien, |
https://jsfiddle.net/42t6chv6/2/
add rules etc to see the event fired. as soon as you click [x delete] on any rule or group - it doesnt fire the change event.
is this a bug?
i tried adding the 'afterDeleteRule.queryBuilder' to it aswell, but it doesnt fire the event either
.on("change.queryBuilder afterDeleteRule.queryBuilder", function() {
changing the operator fires the
change.queryBuilder
event twice.The text was updated successfully, but these errors were encountered: