Concerns: pushword/core, @pushword/js-helper
bleed or img-stretched no longer scrolls sidewaysAffects every site, whether or not it uses the horizontal scroller. Both utilities are 100vw wide, and 100vw counts the classic vertical scrollbar — so on any platform whose scrollbars take up space (Windows, Linux without overlay scrollbars) they have always been a scrollbar wider than the content box, giving the page an unwanted horizontal scroll of exactly that much. macOS and mobile never showed it.
js-helper now clips it away:
body:has(.bleed, .img-stretched) {
overflow-x: clip;
}
clip rather than hidden: it creates no scroll container, so position: sticky inside keeps working and the vertical axis is untouched. The :has() scopes it to pages that actually bleed.
Rebuild your assets to pick it up. If a page of yours deliberately scrolls horizontally at the page level, override it — body { overflow-x: visible } on that template.
wrapperClass on the horizontalScroll view moved to the wrapperOnly affects sites already passing wrapperClass to pages_list(…, 'horizontalScroll'), which shipped one release ago in rc837.
It used to land on the scrolling <ul>. It now lands on the positioned wrapper around it, because that is what the ::scroll-button() arrows are laid out against: a layout class on the row — bleed being the obvious one — widened the cards and left the arrows pinned to the narrow box. The row keeps its own class untouched.
Nothing to do unless you were passing a class meant for the row itself (a gap-*, say); move that into your own CSS on .horizontal-scroll.