Education websites browser vs Smartboard compatibility issues

[jmak]

Since installing Windows 10 1803 on the PCs connected to the Smartboards in the classrooms, we're getting compatibility issues with some websites in some browsers. The websites display correctly, but don't respond to touch. Our default browser is Chrome, as we've found that has best compatibility overall, but some websites work in IE only. The teachers are pretty good at testing websites before lessons to make sure that they're not blocked etc, but don't always get an easy opportunity to try in the classroom without children present.

 

I've said that this is random and that there's not much I can do to predict or prevent, but thought I'd ask in case there is a more general fix. Smart Notebook 11.4 with either driver versions 12.2 or 12.9, latest browser versions.

 

Thanks

[psydii]

Chrome OS is becoming a tablet OS. I wonder if that isn’t related.

[XiJ]

We found chrome and smart drivers 11.4 could be problematic. But the drivers were legacy and the school no longer used smart boards so we removed it.

[jmak]

Unfortunately not an option for us. Smart Boards in every class and no subscription to a later version. I'll have to do more testing on different browsers to see if we can make do without Chrome.

[Arthur]

Is Smart Notebook listed here?

 

chrome://settings/incompatibleApplications

[XiJ]

Could you not subscribe to a newer version of you’re Smart board / screen. I

Know there’s a cost - but a lot less than non smart hardware.

[jmak]

Is Smart Notebook listed here?

 

chrome://settings/incompatibleApplications

(Somewhat) interestingly, the only application listed there is Sophos Anti-Virus [emoji54]

Could you not subscribe to a newer version of you’re Smart board / screen. I

Know there’s a cost - but a lot less than non smart hardware.

🤣

 

Just had another thought; could it be because I don't have Java installed?

[thimon]

We were on Smartboard v11 having this issue on 1803, upgraded to the latest version of Smartboard and still get it. In Google Chrome go to chrome://flags and enable Touch Events API, seems to help, but doesn't completely resolve the problem