Saxon » SaxonJS

Further investigations have revealed that the problem occurs on computers which have touch screens. In the Chrome browser, the documentation app navigation does not work with mouse clicks, but does work with touch events. So the problem is in the design of the event handling in the documentation app.

The documentation app affectively assumes that if touch events are possible, then mouse clicks are not. Clearly this needs updating since there are devices that allow both.

I have updated the design of the documentation app, to remove the difference for touch and click events, so it should now be working without problems for devices which allow both.

The previous app design assumed that devices only used one or the other type of event, with separate (but very similar) event handling templates for the different cases (with mode="ixsl:onclick" and mode="ixsl:ontouchend"). The "onclick" templates were then disabled for a device which allowed touches.

In the redesign, we no longer need separate templates specifically for touch events. It is now standard for touch events to trigger click events (if they are not cancelled during an interaction, e.g. by moving the touch), so the click event handling templates are sufficient. (Perhaps this was not the case previously, when the Saxon-CE documentation app was originally designed; which was used as the basis for the Saxon-JS documentation.)

This has also improved the usability of the documentation app on touch devices in general - previously, scrolling the navigation menu would also trigger a page navigation (from the 'touch point'), but now this doesn't happen.

Bug fix applied in Saxon-JS 1.0.1 maintenance release.