Steps to reproduce:

1. Hover over a term in order to show the available actions.
2. Click the "select all children" action.
3. Hover over the term again. The option is now correctly renamed to "unselect all children".
4. Uncheck the all the children terms of this term by clicking their checkboxes.
5. Hover over the parent term again. The option still says "unselect all children" when it should be "select all children".

The same thing (the opposite thing actually) happens if you try to use the hover-over action "unselect all children" while previously having checked the children checkboxes of a term:

1. Choose a term with a couple of children terms.
2. Check all these children terms by using their checkboxes.
3. Hover over the parent term.
4. Instead of showing a "unselect all children" hover action, it says "select all children".

...of course clicking on this action has no effect other than toggling the available action to "unselect all children". Now the user needs to click on it a second time in order to do the thing they intended to do in the first place.

Comments

klonos’s picture

...btw, a google search for "deselect or unselect" brings pretty interesting results. Some of them mention:

Dictionaries (Merriam-Webster and New Oxford American Dictionary) have deselect but not unselect. The NOAD defines deselect as “turn off (a selected feature) on a list of options on a computer menu”, which is what you want.

Unselected, on the other hand, is used to qualify something that has not been selected, not something that was selected and isn't anymore.

Since English is not my native language and I'm aware of the fact that there are quite a few differences between American and British English I honestly wouldn't know for sure which term is correct or if both can be used.

mh86’s picture

  • Just renamed unselect to deselect - thanks for that hint!
  • In RC1 the select all children isn't really working, as the child terms don't get expanded. Just fixed that
  • Making both actions context aware will be more difficult. Always displaying both would be some kind of workaround.
klonos’s picture

Sorry for the late reply Matthias, been busy for a while...

...thanks for that hint!

No problem ;)

Making both actions context aware will be more difficult. Always displaying both would be some kind of workaround.

Fair enough, I'll take any workaround in the meantime. Thanx.

mh86’s picture

Status: Active » Closed (won't fix)

Marking as won't fix, because there is no easy way to make it context aware.