Input/output ordering issues
See original GitHub issueHey @sa-si-dev , I don’t know how to properly communicate the issue here, because I’m not using virtual-select
directly, I’m using it via shinyvs, which uses an R
interface passing the parameters to virtual-select
as the backend. So I’m sorry about that and I’m hope we can find a way to work around it.
The problem I’m facing is that virtual-select
seems to force the input/tooltip label/output order to be the same as the one in value
in options
. I describe the matter in more details here https://github.com/dreamRs/shinyvs/issues/10 .
Is there a way to make the tooltip labels and the output to follow exactly the order of the input selected?
I believe that is the standard behavior of other selectInput tools that I use, and it would be great to have an option to obtain that.
virtual-select
output order actually follows the input order selected later interactively but not the initial selected order passed to selectedValue
.
Thanks a lot
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
@GitHunter0 thanks for letting me know it. I will implement it in the future release.
Hey @sa-si-dev , I came back to provide some feedback.
First, thanks again for the work.
I did some tests and I’m still having some issues. Here’s a MWE using
R
:Initial screen: output should be
val2, val4, val1
(in some previous tests it was correct but not anymore for some unknown reason)After adding
lab3
: now the new input order is respected in the tooltip and output, but not in thepopup
.Then after closing
lab2
by clicking x in tooltip tag, the tooltip and output change the order, so thatlab3
andval3
are no longer the last.PS: As an aside,
position
parameter is doing nothing in my tests (without popup option), should I open an issue for that?