Closed Scrolling over notice carousel can be blocked or feel broken

Mbx

Active member
Licensed customer
Affected version
2.3.7
The notice is rendered inside a draggable carousel container. Because the carousel viewport is marked as draggable, the whole notice area gets treated like something the user can grab/drag.

This is problematic for notices, because notices are usually meant to be read and clicked, not dragged like an image gallery. When the mouse is over the notice, normal page scrolling may no longer behave as expected or can feel interrupted. This is especially annoying when the notice contains text, images, or links.

The issue appears to be related to the carousel styling/behavior around .f-carousel__viewport.is-draggable, which applies a grab cursor, and the notice slide being rendered as .f-carousel__slide.

Expected behavior:
The user should be able to scroll the page normally while the mouse is over a notice. Links and buttons inside the notice should behave like normal clickable elements.

Actual behavior:
The notice area behaves like a draggable carousel area. This can make scrolling over the notice feel blocked or unreliable, and it also makes links inside the notice feel less natural to interact with.

Suggested fix:
For notice/carousel content, avoid showing the grab cursor by default and only use a dragging cursor while the carousel is actively being dragged. Links and buttons inside the carousel should keep the normal pointer cursor.

.f-carousel__viewport.is-draggable {cursor: move; cursor: grab}

to this:

.f-carousel__viewport.is-draggable {cursor: default}
 
Automated triage: As designed

Scrolling notices can be dragged with the mouse to move between them, which is why the grab cursor shows. The mouse wheel is not captured over them, so the page should still scroll normally. Links keep their usual pointer cursor.

This is an automated assessment. A member of staff may review and update it.
 
Back
Top Bottom