General error: Automatic browser scroll to red-marked mandatory field (small screens)
Submitted by Dagolere on Mon, 10/02/2017 - 15:12
Forums:
Example: Interactive Video -> Crossroads (image attached)
Fields for "Question Text" and "Choyce Text" are filled out, but the "Go To"-field has not been filled out.
When pressing "DONE" nothing happens. There is no indicator of what is wrong, because I can't see that the "Go To"-field has been marked red.
In order for this to show, the browser needs to scroll automatically to the "non-filled/data not accepted"-field.
*Using Google Chrome on Mac
BV52
Tue, 10/03/2017 - 05:34
Permalink
Hi Dagolere,Thank you for
Hi Dagolere,
Thank you for reporting this. In order give your bug report the best chance of getting answered, please include the following information:
The more information you provide, the quicker the community will be able to fix it and the quicker you'll have a working solution!
Dagolere
Tue, 10/03/2017 - 09:52
Permalink
Error occurs in the demo on this website
This has been tested on your web site demo.
1. Go Interactive Video -> add youtube-file -> Open Crossroads interaction window ->add data inn Fields; Question text and choice text ->press DONE -> (error) browser does not scroll automatically to mandatory field that has error state (in other words: error is not identified to the user when DONE-action is prevented)
2. The version you are using on the demo on this website
3. Desktop: Macbook
4. Mozilla Firefox, Google Chrome and Safari on Mac
5. The plugin on H5P.org
6. The content type version on H5P.org
7. During creation
8. Screenshot attached
BV52
Tue, 10/03/2017 - 11:14
Permalink
Hi Dagolere,Thank you for the
Hi Dagolere,
Thank you for the information.
This is actually by design or a lack of the feature. I think this is a valid concern and can help a lot by knowing immediately what is missing. Also if I may suggest to have this feature on all content types. There is also an alternative where there would be a message at the top saying that there is a missing field. I think it may be easier to code this kind of change what do you think? I have moved the post to the Feature Request forum for better visibility.
-BV52