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
it is now quite unclear how setting selectiongStart/End to null should behave.
"On setting, it must act as if the setSelectionRange() method had been called, with the new value as the first argument; the current value of the selectionEnd attribute as the second argument, unless the current value of the selectionEnd is less than the new value, in which case the second argument must also be the new value; and the current value of the selectionDirection as the third argument."
is the idea that there is implicit null -> long conversion? so null would mean 0 ?
Yes, it should convert null to unsigned long, is how I figured it should work. I agree it is not great with "act as if foo method had been called" language though. We should have an abstract algorithm that is invoked by the relevant APIs instead.
it is now quite unclear how setting selectiongStart/End to null should behave.
"On setting, it must act as if the setSelectionRange() method had been called, with the new value as the first argument; the current value of the selectionEnd attribute as the second argument, unless the current value of the selectionEnd is less than the new value, in which case the second argument must also be the new value; and the current value of the selectionDirection as the third argument."
is the idea that there is implicit null -> long conversion? so null would mean 0 ?
@zcorpan ?
#1006
The text was updated successfully, but these errors were encountered: