I understand Android tablets are not supported, but was wondering if some experienced user found a way to create a Drag&Drop interaction for Android tablets - maybe "immitating" the interaction in some other way?
If you're running into issues with SL2 content on an Android device we'll want to take a look at the .story file and know more about how and where you're testing the content.
Sorry for my confusion - but I thought you were looking for support for Android devices? If so, you'd need to have included HTML5 or the option for the mobile player on Android. IE11 (and definitely 7 and 8) are not supported for HTML5 output. You can see that in the documentation that Michael shared, and I also like to reference sites such as HTML5test.com which compares different browsers and how they'll handle HTML5 output.
Thank you. i think i was one the that was confused. The users are viewing the training from Tablets and I was mixing up whether to remove the HTML5 output or to keep it.
Here is a summary of the issues we experienced during our in field testing on the tablets and the technical specs of the devices we are using.
Technical Specs:
Tablets: HP Elitepad 1000 G2
Windows OS version: 8.1
Internet Explorer Version: IE 11
The issues we saw today:
Many of the buttons within the content windows were unable to be pressed in both Desktop mode and Immersive mode of IE11.
Some of the buttons needed to be touched in very small portion of the button to work in both Desktop mode and Immersive mode of IE11.
Any drag and drop portions were extremely challenging to complete as the only some of the buttons were able to be moved in both Desktop mode and Immersive mode of IE11.
The text areas were difficult to actually get the cursor to show up in either Desktop Mode or Immersive mode of IE 11.
Have you checked to ensure that you have Flash enabled as a part of your browser and on the tablet? We don't support HTML5 in IE11, even on the tablets so it sounds as if it may be a Flash issue.
7 Replies
I know this is an old question, but I am having those problems today.
SL2 introduced support for Android, see here for info on system requirements.
Hi Helena,
If you're running into issues with SL2 content on an Android device we'll want to take a look at the .story file and know more about how and where you're testing the content.
I removed the HTML5 output for this client.
They are using IE11 ( I also think 7 and 8) and are viewing on their tablets.
Hi Helena,
Sorry for my confusion - but I thought you were looking for support for Android devices? If so, you'd need to have included HTML5 or the option for the mobile player on Android. IE11 (and definitely 7 and 8) are not supported for HTML5 output. You can see that in the documentation that Michael shared, and I also like to reference sites such as HTML5test.com which compares different browsers and how they'll handle HTML5 output.
Thank you. i think i was one the that was confused. The users are viewing the training from Tablets and I was mixing up whether to remove the HTML5 output or to keep it.
Here is a summary of the issues we experienced during our in field testing on the tablets and the technical specs of the devices we are using.
Technical Specs:
Tablets: HP Elitepad 1000 G2
Windows OS version: 8.1
Internet Explorer Version: IE 11
The issues we saw today:
Many of the buttons within the content windows were unable to be pressed in both Desktop mode and Immersive mode of IE11.
Some of the buttons needed to be touched in very small portion of the button to work in both Desktop mode and Immersive mode of IE11.
Any drag and drop portions were extremely challenging to complete as the only some of the buttons were able to be moved in both Desktop mode and Immersive mode of IE11.
The text areas were difficult to actually get the cursor to show up in either Desktop Mode or Immersive mode of IE 11.
Hi Helena,
Have you checked to ensure that you have Flash enabled as a part of your browser and on the tablet? We don't support HTML5 in IE11, even on the tablets so it sounds as if it may be a Flash issue.
This discussion is closed. You can start a new discussion or contact Articulate Support.