`autoSelect` option

[mifi]

`autoSelect` option

[limonte]

Anyways I thought it might be a common use case to have the text auto selected, but whether it needs to be an option or not.. your call.

Nah, I don't think this small functionality deserves its own parameter 😄

Right.. maybe it's still better to explicitly list all those types that actually support the cursor though, in order to avoid possible bugs/errors from occurring (in certain browsers)?

Also nah, it has been like this several years already w/o any issue-reports. Listing all of them explicitly would create another place to keep in mind when adding new input types in future.

[limonte]

Just to clarify, are you asking about making this:

Swal.fire({
  input: 'text',
  inputValue: 'test',
  didOpen: () => {
    Swal.getInput().select()
  },
})

a parameter?

[limonte]

it places cursor in case of input.type !== 'file'. so for HTMLSelectElement it also places the cursor, however I'm not sure that HTMLSelectElement has a cursor? shouldn't it be changed to something like input.type === 'text' || input.type === 'textarea'?

You're right. For HTMLSelectElement it probably just silently does nothing w/o any errors or warnings.

input.type === 'text' || input.type === 'textarea' wouldn't be enough because there are 'email', 'phone', 'password', 'search' and many others

[mifi]

a parameter?

Yes, although I didn't realise that it's actually that easy to do it 🙈 I can confirm that your code solves my problem too, thanks!

Anyways I thought it might be a common use case to have the text auto selected, but whether it needs to be an option or not.. your call.

input.type === 'text' || input.type === 'textarea' wouldn't be enough because there are 'email', 'phone', 'password', 'search' and many others

Right.. maybe it's still better to explicitly list all those types that actually support the cursor though, in order to avoid possible bugs/errors from occurring (in certain browsers)?