This is related because it is the same side-effect. If you try to use arrow keys and spacebar, each time a plugin is selected in the install panel, the current item is reset to 1 and you can't "go to the next" plugin in list with keyboard anymore.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to debug this but the control flow is not obvious and I was having difficulty figuring out why
certain code was being executed. Shlomy tried and also got a bit lost in the control flow. This is a tricky bug that requires advanced debugging skills.
Any volunteers?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
your fix improves things in that you can n ow read the description after checking a checkbox, but you still can't use arrow keys and spacebar to select a bunch of plugins because the current item gets reset to 0 after each checkbox toggle.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
which plugin reproduces this?
This is related because it is the same side-effect. If you try to use arrow keys and spacebar, each time a plugin is selected in the install panel, the current item is reset to 1 and you can't "go to the next" plugin in list with keyboard anymore.
I tried to debug this but the control flow is not obvious and I was having difficulty figuring out why
certain code was being executed. Shlomy tried and also got a bit lost in the control flow. This is a tricky bug that requires advanced debugging skills.
Any volunteers?
Fixed in revision 22633. It required a very complex and tricky fix :)
your fix improves things in that you can n ow read the description after checking a checkbox, but you still can't use arrow keys and spacebar to select a bunch of plugins because the current item gets reset to 0 after each checkbox toggle.
Ah, keyboard. I didn't test that.
Same issue exists with update panel too.
Alan, try the update I checked in in revision 22658. I believe this fixes the issue you mentioned last with keyboard handling.
looks like you fixed it! thanks! --alan