Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What should happen with input.selectionStart = null; #1628

Closed
smaug---- opened this issue Aug 4, 2016 · 1 comment
Closed

What should happen with input.selectionStart = null; #1628

smaug---- opened this issue Aug 4, 2016 · 1 comment
Labels
clarification Standard could be clearer topic: forms

Comments

@smaug----
Copy link

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

@domenic domenic added the clarification Standard could be clearer label Aug 5, 2016
@zcorpan
Copy link
Member

zcorpan commented Aug 9, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer topic: forms
Development

No branches or pull requests

4 participants