Why auto-select in text entry

Hi Philippe,

There is no way to block the auto select or to stop the user from removing all the text. 

I hope that someone who may have run into a similar situation is able to provide a suggestion or solution to you here. 

Hi,

Thanks for your support.

Why there is a auto select ? Because I tested the behavior of my e-learning course and severals times, all the text dissapear due to this auto select. It's to easy to make a mistake and lost all text in these text boxes. It's not a normal behavior with text treatment. Like Microsoft Word or something else, there is no auto select with control loses focus. On about 2000 students per year, I think that this problem will be a blocker for this e-learning course. And for my other thread (Problem with ESSAY), is it possible to sumbit this issue to your programming team or someone else ? Because I think it's a bug.

Thanks.

Hi Philippe,

I may be misunderstanding what is happening within your file - so just to clarify I wanted to describe what I'm seeing.

In a text entry, such as an essay question  if I type a bunch of text, and use the submit button, I go to the next slide. Let's say I then click "previous" to go back to look at the essay question. All the text is selected, but I can't adjust it (type new, delete, etc.) as the interaction has already been submitted. 

If I have a text entry with no "submission" trigger, when I revisit that slide, again all the text is selected and if I start typing my text disappears. If I click within the text entry box I'm able to add text wherever I clicked - either in the middle of the text entry or at the end. This all seems to be working as expected, and if you'd like to see a different behavior, you're welcome to share your thoughts in the form of a feature request here. 

In regards to the other thread, we'd want to take a look at how you had this set up, and it looks like you may have attached the published output in that thread. Can you share the .story file here with us or share it with our Support team here?

This is working as expected but this does not mean it is a great user experience because when a user goes back to edit the text they usually end up wiping out everything they previously entered.

I don't have a solution for survey fields but do have a partial solution for editable fields that are prepopulated with text that you want the user to modify.

What I do is put the editable text in the value field assigned to the text variable. The editable text displays in the field when you preview or publish. Because people have a tendency to wipe out the text in the field, I add a reset button to the screen with a trigger that says to set the variable to the value when the user clicks the button. This does not retain any of the edits the user made but it does restore the text to the initial value so they can start again.  

here is a demo: Demo

I've also attached the storyline 1 file.

Thanks for your responses. 

Does someone could try this:
1- Create essay (survey) .
2. Set the size of text entry area about 200px (h) x 450px (W)
3- Click Preview
4. Write text to overflow the text box (the scroll bar will appear)
5. Go to the beginning of your text to make a change (eg change the first word of the text or sentence)

What do you notice ?
Is what you see what you write ? I do not see what I am trying to change . I only see the end of the text.

Is it a desired behavior ?

Could you try this too :

With the previous activity (essay)
1- With enough text to make the scroll bar appear.
2- Make a change in your text at the top , middle and at the bottom of your text and using the scroll bar of course to put the cursor in the right place .

Do you think it 's odd behavior as when you want to change anything in your text ? Why there was a text selection whenever the focus is on the text box ? In each case, the user must ensure to click again in the text to remove the selection or risk losing all the text if unfortunately he presses a key on the keyboard.

So what do you think?

Thanks

Hi,

Has anyone could try this ?

Thanks

Hello Phillippe!

I tested this and it is auto selecting in the preview mode, however I am not seeing this behavior in the Published output.

Have you tested this in publish? Do you have a file you could share?

Here are the e-learning course (attached).

Yes I tested this by publishing this training on our LMS (Ellicom). I even tried to open the story.html (in the folder generated when publishing) and it's the same problem.

How have you tested your "publish output" not to see auto-selection ?

Thanks

Hello Philippe!

Thank you for sharing your file. I did test this in published output and I do see that when going back to the beginning of the text, it is auto selected. (I was using Storyline 2)

However I am able to select anywhere in the box of text and make changes. As Ashley stated above, this is working as expected. Have you tried using Nancys example above?

Thank you for your reply.

Unfortunately, I can not use the technique of Nancy for my project . I looked at his .story and it's changing text already registered in the writing area. In my case, the student must write his own text and to change it.

I understand that if the text is limited to the size of the writing area and the scroll bar does not appear, I can actually move my cursor in the text without auto-selection (if the focus is not leaving this writing area). But if the text is longer than the writing area and the scroll bar appears , once you click on the scroll bar, the focus is no longer on the text box. And when the focus returns to the writing area, we only see end of text which requires us to go up the text at the beginning with the scroll bar and we loses focus again.

The only thing that worries me is that it's easy to lose accidently his text because of losing focus with the scroll bar.

Is it something that can be modified by you that eliminating auto-selection when the focus is on the text ? Or prevent the loss of focus of the text when using the scroll bar ?

Thank you .

Hello Philippe

You may want to submit a feature request if you would like to see a different behavior with these types of questions.

I submit a feature request.

Thanks

I also submitted a request.

This seems counter-intuitive!

Thanks Carlos for submitting the request. 

I have also placed a feature request to have this resolved as this seems more pronounced with SL360 and HTML5.

Thanks Pano for submitting the request!