#10992 closed enhancement (fixed)
Add tri-state behavior to the batch modify group togglers
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | 1.0.1 |
Component: | ticket system | Version: | |
Severity: | normal | Keywords: | batch-modify |
Cc: | Branch: | ||
Release Notes: |
The BatchModify select-all checkboxes are toggled with tri-state behavior when the ticket checkboxes are toggled. |
||
API Changes: | |||
Internal Changes: |
Description
The attached patch causes the group toggler to change state when the grouped toggle checkboxes are selected. The group toggler code is also refactored.
Mentioned in comment:13:ticket:9609.
Attachments (1)
Change History (14)
by , 12 years ago
Attachment: | t10992-r11483-1.patch added |
---|
comment:1 by , 12 years ago
Milestone: | → 1.0.1 |
---|---|
Owner: | set to |
Status: | new → assigned |
comment:2 by , 12 years ago
Two comments related to this patch:
- I'm not entirely confident about my use of closest rather than parents. cboos suggested I use
closest
in comment:11:ticket:9609, but I don't have the use cases entirely sorted out in my mind. - The jQuery documentation for prop suggests that method should be used rather than attr for changing the checked property, which motivated the changes
attr("checked", this.checked)
→prop("checked", this.checked)
.
comment:3 by , 12 years ago
closest
is fine, however you need to match both <thead>
and <tbody>
, as only the first group is a <thead>
. I have fixed it here already. The use of prop
is good.
follow-up: 6 comment:4 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Slightly fixed patch applied in [11505], together with a small optimization in the same code in the plugin admin panel. (There must be a way to combine both implementations into a generically-usable function, but it wasn't immediately obvious, so I left it at that.)
comment:5 by , 12 years ago
Owner: | changed from | to
---|
comment:6 by , 12 years ago
Replying to rblank:
(There must be a way to combine both implementations into a generically-usable function, but it wasn't immediately obvious, so I left it at that.)
It hasn't been obvious to me how to accomplish this either, but I've had it on my todo list so that the select all functionality could also easily be added to some of the admin panels that have tables. I can look into make this change as part of #10994.
follow-up: 8 comment:7 by , 12 years ago
Note that this tri-state behavior would probably be very useful for the repository filter in the timeline… I was 99% sure we had a ticket about the current behavior of this filter being somewhat confusing, but I can't find it anymore (#8758 is only the original enhancement request ticket).
follow-up: 9 comment:8 by , 12 years ago
Replying to cboos:
Note that this tri-state behavior would probably be very useful for the repository filter in the timeline… I was 99% sure we had a ticket about the current behavior of this filter being somewhat confusing, but I can't find it anymore (#8758 is only the original enhancement request ticket).
Yes, there is a ticket about that — #10144
comment:9 by , 12 years ago
Replying to Ethan Jucovy <ethan.jucovy@…>:
Yes, there is a ticket about that — #10144
Thanks a lot, yes that was it.
comment:10 by , 12 years ago
Keywords: | batch-modify added |
---|
Ryan, would you mind updating the Release Notes: and API Changes: fields (as appropriate) of the tickets you contributed?.
comment:12 by , 12 years ago
Release Notes: | modified (diff) |
---|
comment:13 by , 12 years ago
Release Notes: | modified (diff) |
---|
Patch against r11483 of the trunk.