Troubleshooting
Why swipe scrolling fails on a touchscreen web HMI page
Short answer
When other browser windows scroll but a scrollable region on the HMI page will not swipe, the touch panel and driver are fine and the fault is layered: the browser is not delivering touch events (Chrome stopped exposing them by default), the visualization object has no gesture handling enabled, or an overlapping object swallows the swipe. Fix all three, then verify with a finger only — a mouse wheel hides the fault.
On this page
When every other browser window on the panel scrolls with a swipe but a scrollable region on the HMI page sits still — scrollbar drawn, finger doing nothing — the touch panel and its driver are working. The fault sits above them, in three layers: the browser has to deliver touch events to the page, the visualization object that owns the scroll region has to have gesture handling enabled, and nothing may overlap the region and swallow the swipe. Chrome-based browsers no longer expose touch events by default, which makes the first layer the usual culprit. Work the checks below in order, then verify with a finger only, because a mouse wheel hides this fault on the bench.
Separate the panel fault from the page fault #
Test in two places on the same panel: a plain, long web page in the same browser, and the scrollable region on the HMI page.
| Test result | What it means | Where you go next |
|---|---|---|
| The plain page scrolls; the HMI region does not | Driver and OS gesture settings are fine; the fault is in the page's touch handling | Browser touch-event delivery, then the object |
| Nothing scrolls anywhere, in any application | The fault is below the browser: touch driver or input mode | Fix the panel's touch input first |
| Taps register, but no swipe scrolls anywhere | The panel may be emulating a mouse and sending no touch semantics | Driver mode, then the browser touch-event setting |
For the second row, fix the panel's input stack before you open the HMI project — the driver-level ground is the same as in getting a touchscreen working under a Linux HMI runtime.
Make the browser deliver touch events #
The most common cause of this exact symptom is that the browser never hands the finger to the page as touch events. The scrollbar is a mouse-style control — wheel and mouse drag work without any touch events, which is why the page passes a bench test with a mouse and fails under an operator's finger.
Work through these, in order:
- Read the HMI vendor's browser configuration topic, alongside its commissioning notes for the HTML functions used, and set the browser exactly as documented; it names the interface the runtime expects.
- On a Chromium-based browser, open chrome://flags, find the Touch Events API entry, set it to enabled and restart. In a kiosk launch the same setting rides on the
--touch-eventscommand-line switch — confirm its accepted values against your browser version's documentation before editing the shortcut. - Open developer tools on the panel, log input events, and swipe once slowly across the region. One slow swipe should produce one
touchstart, a run oftouchmoveentries, and onetouchend. If the console logs nothing of the kind, the browser layer is the fault; if the events fire and the content still does not move, the page logic is. - Restart as a fresh process after any change. A launch switch never reaches a browser that was already running, and kiosk wrappers that attach to the existing instance ignore it silently.
Turn on gesture handling for the scroll object #
Touch events reaching the page are only input; the visualization object holding the scrollable content still has to interpret them. Open that object's properties and enable its gesture or swipe handling — the web visualization documentation carries a "Visualization object with Gestures" topic plus a "Detecting swipe gestures" FAQ for the detection logic. Without that setting, the object draws its scrollbar, accepts a mouse drag, and never maps a swipe to a scroll.
| Layer | Where it lives | Symptom when it is wrong |
|---|---|---|
| Touch-event delivery | Browser flags or launch switch | Page logic receives no touch input at all |
| Gesture handling | Visualization object properties | Input arrives but is never interpreted as a swipe |
| Overlap above the region | Page z-order | The touch is captured before it reaches the scroll content |
Touch behavior in a browser visualization has neighbors here: if a held finger opens a context menu instead, that is a separate setting, covered under long touch opening a right-click menu in a web visualization.
Clear the overlaps and the CSS that blocks panning #
A transparent rectangle, a button background or a frame placed above the scroll area captures the touch before the scroll content sees it, and a swipe that starts on a button usually scrolls nothing because the button consumes the press. The diagnosis is the same as fixing overlapping graphics hiding HMI symbols: check the z-order and what sits on top.
- Start the swipe in an empty part of the region, not on a button or a text field.
- Temporarily hide or move the objects above the region and swipe again. If the content moves, rework the layout so the scroll region has no covering input objects, or enable gesture forwarding on the objects that sit above it.
On pages that embed HTML content, check the container itself: the scroll region needs overflow: auto or overflow: scroll, and no ancestor may carry touch-action: none, which tells the browser not to pan on touch whatever the scrollbar suggests. Script that calls preventDefault() on touchmove reserves the gesture for its own logic, so it belongs there only if the script actually implements the scroll.
Verify with a finger, then from a cold boot #
- Download the changed project and reload the page on the panel; clear the browser cache if the old behavior survives the reload.
- Disconnect the mouse. Wheel and scrollbar drag are mouse input and will mask the fault.
- Swipe from five start positions — top, upper middle, center, lower middle, and directly on a button — in both directions. That is ten swipes (5 × 2), plus one slow drag and one fast flick at the center.
- Drag the scrollbar itself with a finger and confirm it tracks.
- Reboot the panel and repeat the finger test on the first page load after boot. Launch switches and autostart shortcuts only prove themselves on a clean start.
If the content follows the finger from every start position after a reboot, all three layers are aligned and the fix is done. If the scrollbar drags by finger but the content still will not pan, the remaining fault is in the container CSS — touch-action or overflow — not in event delivery, and no browser flag will change it.
Questions asked
Why does the scrollbar still respond to the mouse when swiping fails?
The scrollbar, the wheel and a mouse drag are mouse input, delivered without touch events ever being consulted. Touch-event delivery only matters to a finger, so the page passes every bench test with a mouse and still fails for the operator. That is also why the verification procedure disconnects the mouse before the final swipe tests.
I set the touch-events switch and nothing changed. What did I miss?
A launch switch reaches only a browser process that starts after the change. Kiosk wrappers and shortcuts that attach to an already running instance ignore it, and so does a process restored from the background. Close every browser process, check the task manager for leftovers, relaunch, then reboot the panel and retest on the first page load.
A swipe near the screen edge goes back a page instead of scrolling. Why?
That is overscroll history navigation: a horizontal fling at the edge triggers the browser's back action and throws the operator off the HMI page. The #overscroll-history-navigation entry in chrome://flags that used to disable it no longer appears in current versions, so keep operational swipes inside the content area or consume the gesture in the page logic before the browser does.
Does my page need touch events enabled if it uses pointer events?
No. Logic written against pointer events receives pointerdown and pointermove for a finger without the Touch Events API being turned on; the flag governs touchstart, touchmove and touchend. What decides is the HMI runtime, so set the browser the way the vendor's browser configuration topic documents, and confirm in developer tools which events actually fire on a swipe before changing anything else.