When you are using v-list-goups with an #activator, then it seems to be almost impossible to be able to select the list-items acting as activator.
After spending hours trying to solve that, this is what I came up with: (simplified it a bit)
Having the class v-treeview-item--activetable-group-activator on the list item and the v-list-item--active class for the active state enables the visual selection effect. The v-model hack is also required to pass the value around, so it behaves in the same way as the regular v-list-item with the v-else.
As far as I have seen, this all leads to the fact that the property "activatable" which is included via the nested.ts is not changeable somehow.
I have no clue what you need to do to achieve that, but having actuvtors that behave like regular list-items would be great.
Problem to solve
When you are using v-list-goups with an #activator, then it seems to be almost impossible to be able to select the list-items acting as activator. After spending hours trying to solve that, this is what I came up with: (simplified it a bit)
Proposed solution
Having the class v-treeview-item--activetable-group-activator on the list item and the v-list-item--active class for the active state enables the visual selection effect. The v-model hack is also required to pass the value around, so it behaves in the same way as the regular v-list-item with the v-else.
As far as I have seen, this all leads to the fact that the property "activatable" which is included via the nested.ts is not changeable somehow.
I have no clue what you need to do to achieve that, but having actuvtors that behave like regular list-items would be great.