You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removing child from front to back will lead to a problem of selected property when we remove option element. Because the second option will be selected when we remove the first option .
For example
The key property is random so it will append some new options to select and remove all old options and move new options to the front of the last VirtualText. The moving action has two steps: remove it and insert it. In this example we want to select the first option, but when we remove option from front to back all options's selected property will be true. After inserting the removed options the last option will be selected at last (Firefox is, but Chrome selects the second option weirdly).
For this case I think reorderChild method should remove child from back to front and insert child from front to back.
I made a pull request.
The text was updated successfully, but these errors were encountered:
Removing child from front to back will lead to a problem of
selected
property when we removeoption
element. Because the secondoption
will be selected when we remove the firstoption
.For example
The
key
property is random so it will append some newoption
s toselect
and remove all oldoption
s and move newoption
s to the front of the lastVirtualText
. The moving action has two steps: remove it and insert it. In this example we want to select the firstoption
, but when we removeoption
from front to back alloption
s'sselected
property will betrue
. After inserting the removedoption
s the lastoption
will be selected at last (Firefox is, but Chrome selects the second option weirdly).For this case I think reorderChild method should remove child from back to front and insert child from front to back.
I made a pull request.
The text was updated successfully, but these errors were encountered: