I've noticed: if a user spells something wrong the red squiggly underline comes up, but the user is unable to right-click and see the suggested spelling; unless they're using Internet Explorer.
It doesn't matter if I try publishing my file as LMS, Web, or Review 360. All publishing methods work only on Internet Explorer
I've tested my file on Chrome, Firefox, and Safari as well, but was unable to right click on the misspelled word
I haven't seen this behavior before, and appreciate you bringing it up. After consulting with our team on this, there is not a built-in way to control and view browser-based attributes like this one in Storyline's published output and Player.
Fortunately, there are tons of crafty folks here who might have accomplished this somehow. I'll open the floor to them!
For now, I'm going to submit a Feature Request on your behalf so we can keep you updated with any news on such a function!
I'm going to subscribe to this, I'm keen to see how this pans out. My client uses a surface pro, and have asked how they can get rid of the red underline, and as they're not able to right-click, I'd be curious to see any other work around.
I've also noticed that if you get learners to type an answer and it is incorrectly spelled then in the feedback layer the red underlines still appear through from the base layer (but the words themselves don't). Some additional work needs to be done to sort this spell check behaviour which I guess is built into the browser?
Thanks for checking in! The red underline for incorrect spelling is a standard browser setting. I'm not aware of any workarounds for changing this in a browser environment.
If we have any updates on our end, we'll let you know!
Thanks Lauren....you can turn off spell checking in the browser and the red lines disappear. The issue is that the words are on the base layer so the red lines really shouldn't appear once another layer is placed over the top. Guess it's just a Storyline bug for the time being.
Yes, that's correct! This is a bug we see in Storyline that our team is still looking at. Thanks for bringing these details to our attention. We'll let you know when we have more information to share.
Thanks for the update Lauren...I can report that back to my client and we can come-up with a workaround - or maybe just teach people to spell correctly ;-)
I have exactly the same problem John described. I inserted a SL block in Rise and ask the user to type into a text entry field and then click a button. The button opens a new layer over the original text entry. The words get covered, the red underline doesn`t.
I don`t experience this in my Firefox browser, where I don`t have an active spelling check, but in my edge browser, where I do have a spelling check.
Since you`re still working on this bug, I thought I share this part of my project as well. Might be helpful.
Thanks for the follow-up, and I'm sorry this bug is affecting your course as well!
We're working through this one, and it's looking good, so we'll pop back in here to let you know as soon as we have an update. Thanks again for bringing this up!
I am adding my +1 for this issue. When clicking on the misspelled word, the whole word is selected. Right-clicking does not bring up the browser's spell check. However, by going through the browser Edit/Substitutions menu, the option to correct the misspelled word is presented and, if you select a substitution, the misspelled word is replaced.
12 Replies
Hello, Ali. Happy first post!
I haven't seen this behavior before, and appreciate you bringing it up. After consulting with our team on this, there is not a built-in way to control and view browser-based attributes like this one in Storyline's published output and Player.
Fortunately, there are tons of crafty folks here who might have accomplished this somehow. I'll open the floor to them!
For now, I'm going to submit a Feature Request on your behalf so we can keep you updated with any news on such a function!
Hi Katie,
Thanks so much for submitting as a feature!
Yeah I'm hoping I can get any kind of lead on this
UPDATE:
It seems to be an issue with right clicking inside the storyline window. I've been looking around, is there a solve for the right clicking issue?
I'm publishing HTML5 Only, LMS, Tin Can API
I'm going to subscribe to this, I'm keen to see how this pans out. My client uses a surface pro, and have asked how they can get rid of the red underline, and as they're not able to right-click, I'd be curious to see any other work around.
I've also noticed that if you get learners to type an answer and it is incorrectly spelled then in the feedback layer the red underlines still appear through from the base layer (but the words themselves don't). Some additional work needs to be done to sort this spell check behaviour which I guess is built into the browser?
Can we force the spell check to OFF?
Hi John!
Thanks for checking in! The red underline for incorrect spelling is a standard browser setting. I'm not aware of any workarounds for changing this in a browser environment.
If we have any updates on our end, we'll let you know!
Thanks Lauren....you can turn off spell checking in the browser and the red lines disappear. The issue is that the words are on the base layer so the red lines really shouldn't appear once another layer is placed over the top. Guess it's just a Storyline bug for the time being.
Hello John!
Yes, that's correct! This is a bug we see in Storyline that our team is still looking at. Thanks for bringing these details to our attention. We'll let you know when we have more information to share.
Thanks for the update Lauren...I can report that back to my client and we can come-up with a workaround - or maybe just teach people to spell correctly ;-)
I have exactly the same problem John described. I inserted a SL block in Rise and ask the user to type into a text entry field and then click a button. The button opens a new layer over the original text entry. The words get covered, the red underline doesn`t.
I don`t experience this in my Firefox browser, where I don`t have an active spelling check, but in my edge browser, where I do have a spelling check.
Since you`re still working on this bug, I thought I share this part of my project as well. Might be helpful.
https://rise.articulate.com/author/HwPpI7XYBqnR9vS6F_SMx7VlfMmvYmNe#/author/details/35FaXpRkHcZX2qot1-4m6TAOuDyBQKv1/preview
I`m looking forward to a solution :)
Hi Marlene,
Thanks for the follow-up, and I'm sorry this bug is affecting your course as well!
We're working through this one, and it's looking good, so we'll pop back in here to let you know as soon as we have an update. Thanks again for bringing this up!
I am adding my +1 for this issue. When clicking on the misspelled word, the whole word is selected. Right-clicking does not bring up the browser's spell check. However, by going through the browser Edit/Substitutions menu, the option to correct the misspelled word is presented and, if you select a substitution, the misspelled word is replaced.
It appears that the Storyline player disables the right click ability. This is consistent among both Chrome and Safari. Maybe this is related: https://community.articulate.com/discussions/articulate-storyline/enable-right-click-paste-into-text-entry-field-with-html5