Troubleshooting
Why a WebIQ button stays highlighted after touch release
Short answer
The blue left on a WebIQ iq-button after touch release is the widget's default active-state animation, not the variable-driven stylesheet fill. Reproduce the latch with Chrome's touch simulation, then apply the vendor's documented fix for color change on button press on touch panels, or adopt the cx-Visuals package with its required cx-tools dependency. Leave the tag binding and style condition untouched, and verify on the physical panel.
On this page
- Why does a WebIQ button stay blue after you release it on a touch screen?
- Is the stuck highlight a tag fault or a styling fault?
- How do you reproduce the stuck highlight before changing the project?
- Which fix clears the highlight on an iq-button?
- When should you pick the workaround and when cx-Visuals?
- How do you apply the fix without disturbing the tag binding?
- How do you verify the fix on the panel PC?
- Why does the highlight still stick after the fix is applied?
- Questions asked
A WebIQ iq-button that stays blue after you lift your finger has not stuck because its tag is still true. The lingering color is the widget's default active-state animation, a browser-side touch highlight that stays latched until you tap somewhere else; the stylesheet only paints the fill from the bound variable. Reproduce the latch with touch simulation in Chrome's device toolbar, then clear it with the vendor's documented fix for color change on button press on touch panels, or with the cx-Visuals package and its required cx-tools dependency. Verify on the physical panel: release clears the blue without a blank-area tap, the mouse path still works, and the fill still follows the tag.
Why does a WebIQ button stay blue after you release it on a touch screen? #
The lingering blue is the iq-button's default active-state animation, which on touch input stays latched to the last element you pressed until you tap another one, while the variable-driven stylesheet fill and the touch highlight are two independent layers the browser and the project manage separately.
The reported setup is a Windows 10 panel PC serving the HMI in Chrome 123. The button carries a stylesheet that turns its background blue when its bound variable is True, and that layer kept working the whole time. What stayed after release was WebIQ's own default blue pressed-state animation, a different layer. Under a mouse, release ends the active state; under a finger, the browser keeps the last pressed element active until the next tap, so the highlight outlives the press until something else is touched. Web HMI platforms split this way generally: in Ignition Perspective, the styling the browser applies to components lives behind the psc- prefix, not the project stylesheet.
| What you observe | Which layer it belongs to | What it tells you |
|---|---|---|
| Fill follows the tag's True and False | stylesheet and binding | binding and style condition are healthy |
| Default blue persists after release | iq-button active-state animation | not a tag fault |
| Tapping a blank spot clears the blue | browser active state | the latch resets without any project change |
| Mouse press and release clears normally | mouse event path | the fault is touch-specific |
Is the stuck highlight a tag fault or a styling fault? #
It is a styling fault when the tag monitor reads False while the blue remains, because the stylesheet can only paint the colors its binding drives and the leftover blue is WebIQ's default animation, which no style condition controls.
Check it directly: open the project's tag monitoring or the PLC diagnostics, watch the bound variable through one touch and release, and compare it with what the button shows. If the variable goes True and back to False while the blue stays, the binding is healthy and the fault lives in the interaction layer. The reverse holds too: a correct tag value does not prove the animation resets, so verify both, separately.
Treat screen color as indication only: confirm the actual point in the PLC before you act on what a highlighted button appears to say. A highlight that outlives its press is exactly the false state indication that designing HMI screens for clear operator decisions addresses.
How do you reproduce the stuck highlight before changing the project? #
Reproduce it on the bench with Chrome's touch simulation: open the project on the panel PC, enable touch simulation from the device toolbar in the browser's developer tools, then touch and release the button and watch whether the default blue outlives the press.
Run the sequence the reported case used:
- Record the bound variable's value and the button's fill before touching anything.
- Touch and release the button without touching elsewhere, and note whether the default blue stays.
- Repeat the same press and release with a mouse on the same project and button.
- Turn on touch simulation in the browser's device toolbar and repeat the touch sequence; the reported case reproduced the latch there, which separates the browser touch path from the physical screen.
- Tap a blank area and note whether only the highlight clears or the tag moves too.
If the tag moves unexpectedly, stop and chase the binding; if only the highlight persists, stay on the interaction path.
Worked example, with the counts that decide it: on the reported panel PC (Windows 10, Chrome 123) the iq-button's bound tag read False, so the stylesheet should have been showing the base fill. The sequence produced three deciding observations: 2 of 2 touch paths latched the blue (the physical screen and the touch simulation), 0 of 1 mouse trials latched it, and the blank-area tap cleared the blue while the tag still read False. The arithmetic is 2 latched touch paths minus 0 latched mouse paths = 2, a touch-only signature, and a tag the monitor shows in its False state drives no special fill at all - the persistent blue cannot be coming from the binding.
Which fix clears the highlight on an iq-button? #
Two documented routes clear it: the vendor's fix for color change on button press on touch panels, which addresses this same latched active state, or the cx-Visuals package, which needs the cx-tools package and ships in the Rexroth template for cartesian robots.
The first route is the vendor's published workaround for the earlier button-press color issue on touch panels; take its steps from the vendor's WebIQ documentation and apply them as written, rather than inferring event handlers, parameter names or style rules from the symptom. The second route adds a widget package: cx-Visuals depends on cx-tools, and without cx-tools present the package will not run. Neither route is a stylesheet edit, because the stylesheet drives the variable fill, not the default animation; if you open the styling anyway, WebIQ Designer styling entries follow their own naming rules, which is what why names go missing in WebIQ Designer IO styling covers.
Do not expect the touch-action CSS property to help: it sets how an element's region can be manipulated by a touchscreen user, covering gestures such as pinch zoom and pan, and it does not touch the active-state latch.
When should you pick the workaround and when cx-Visuals? #
Pick the vendor workaround when it clears the same latched highlight without adding packages to the project, and take cx-Visuals only when you can also carry cx-tools, because a dependency you cannot maintain turns a cosmetic fix into a project risk.
| Route | Requirement | Choose it when |
|---|---|---|
| Documented button-press color fix | the vendor's published steps | it targets the same stuck touch active state and adds no dependency |
| cx-Visuals widget package | cx-tools installed first | the project already builds on the Rexroth cartesian-robot template, or you accept the dependency |
Decision: apply the documented workaround first on a standard WebIQ project, and reserve cx-Visuals for projects already built on the Rexroth template, where the package and its cx-tools dependency are toolchain you already maintain.
How do you apply the fix without disturbing the tag binding? #
Apply exactly one interaction-related change at a time and leave the binding and the style condition as they are, because the diagnosis shows they work and any edit there hands you two variables to untangle when the test fails.
- Save the project, and record the button's binding, the style condition and a baseline screen so you can compare before and after.
- Take the documented workaround steps from the vendor's WebIQ documentation and confirm they address the latched touch active state on the iq-button; do not reconstruct handlers or parameter names from the symptom.
- If you chose cx-Visuals instead, add cx-tools first through the project's supported package workflow, then configure the button according to that package's own documentation.
- Change nothing in the tag binding or the stylesheet condition unless a separate test proves them faulty.
- Deploy to the same panel PC, browser and browser version you reproduced on, then rerun the touch and mouse tests.
How do you verify the fix on the panel PC? #
Verification passes only when touch release clears the default blue without a blank-area tap, the mouse path still behaves, and the fill still follows the tag's True and False states - three checks, run on the physical panel PC and in touch simulation alike.
- Touch and release: the blue clears at release, with no blank-area tap needed.
- Press and release with the mouse: the same button returns to normal.
- Force the tag True and False from the PLC or the tag monitor: the fill follows, and the pressed animation still shows while the finger is down.
- Rerun all three checks in Chrome's touch simulation, so the next project change can be regression-tested at the desk.
If touch simulation passes but the physical panel still latches, the project side is fixed and the device side is not; the next section is the one that applies.
Why does the highlight still stick after the fix is applied? #
Then the remaining fault is in the device's browser and touch input path rather than the project: retest on that panel PC's own Chrome install, confirm the fixed project actually reached the panel, and only then suspect the touch hardware or its driver.
Video and touch arrive separately on a panel PC, so a screen can render the page perfectly while its touch side misbehaves; why HDMI video works but USB touch does not walks the same separation for the case where touch input is missing entirely. The reported fault surfaced on Chrome 123 on Windows 10, so test the browser build the machine actually runs before you conclude anything about the hardware.
Questions asked
Does a latched highlight mean the press event never reached the PLC?
No. The latch is a visual state in the browser, so it proves nothing about the command. Check the result where it matters: watch the bound tag or the PLC point the button writes to. If the tag or PLC value changed as expected, the press reached the controller and only the animation failed to reset; if neither moved, chase the binding separately.
Why does tapping a blank area of the screen clear the blue?
A touch display keeps its active state on the last element that was pressed, and the browser moves that state when the next element is touched. A tap on empty space pulls the active state off the button, so the highlight releases even though nothing in the project, the tag or the stylesheet changed.
Will recalibrating the touch screen remove the stuck highlight?
No. Calibration only maps where a touch lands, and in this fault the tap arrives at the right place; it is the button's active state that fails to release afterward. Recalibrate only when touches register in the wrong spot or miss small buttons. A latched highlight needs the documented interaction-state fix, not a new calibration.
Can the same latched active state appear on widgets other than iq-button?
Yes. The latch comes from how the browser handles touch, not from one widget. Any element that shows a pressed or active state can hold it after a touch release until the next tap, so after applying the fix, exercise every interactive widget on the page, not only the button where the fault was first seen.