[Michael.CationParticipant]

We believe that we have been able to partially isolate the conditions that make this problem appear.

If we wipe a machine completely clean and install the latest version of Ubuntu (16.04) and Firefox from scratch then jqwidgets grid demo page works correctly. (We have not run the Chrome test yet.)

If we start with a machine that is running a prior version of Ubuntu (14.04.x), and prior versions of Firefox, and Chrome and go through the upgrade process to move from one major version of Ubuntu to another (going from 14.04.x to 16.04.x), and then also go through the update process with Firefox and Chrome, then we see this problem appear. So, it seems to be tied to the software upgrade path that has been taken on a machine.

Most of our machines were originally running Ubuntu 14.04.x and have been upgraded over time. By chance, we ran the test on a new machine that we installed last week (that had a fresh “out of the box” version of Ubuntu 16.04) and the demo page worked.

We’re doing some additional testing to see if we can further isolate the specific upgrade step that leaves one or more of the modules used by Firefox and Chrome in an incompatible state.

We’re also going to do some testing of un-installing Firefox and Chrome and re-installing them to see if we can find a simple sequence of steps to get a machine back into a clean state that is compatible with jqwidgets. It doesn’t look to us like this is a bug in jqwidgets — seems like more of an upgrade problem in Ubuntu/Firefox/Chrome land.

Hopefully this post will save other Ubuntu users some time if they run into this issue.

Thanks for your assistance!

[Michael.CationParticipant]

This appears to still be present. My company is running Ubuntu 16.04 with both Firefox (51.0.1 64-bit) and Chrome (56.0.2924.76 64-bit) as our standard development platform and this don’t appear to work with the grid utility. Click events seem to be ignored by the grid.

Does jqwidgets support Chrome and Firefox running on Ubuntu? Does jqwidgets have an ability to do browser testing on an Ubuntu platform? This is easy to reproduce with current versions of Ubuntu, Firefox and Chrome since the official demo page referenced in the original post above can be used to see the problem.

We’re an Ubuntu development shop so this is a show-stopper for us.

Please confirm whether or not a test is being run on an Ubuntu machine to reproduce and diagnose this problem. Just trying to test it from Windows will not replicate. Please let me know if there is anything that we can do to help with resolving the problem.

Thank you!

[Author]

Posts