You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the behaviour of hx-boost scroll to is not user friendly (unless I miss something). When you have, for example a menu, and use hx-boost. When something below the menu is replaced then whenever you use hx-boost it will jump to the div but your menu will not be in the screen anymore. Only can mitigate this by adding a # to the url or using one of the settings.
I think it would be better not to have this scroll functionality by default False on hx-boost and to turn it on explicit or have hx-scroll attr that you can set on particular hx-boost.
We also have to help:
htmx.config.defaultFocusScroll
htmx.config.scrollBehavior
The text was updated successfully, but these errors were encountered:
I think it would be better not to have this scroll functionality by default
That would be a debatable matter, unfortunately we can't change defaults at this would be a breaking change for existing htmx-powered apps.
If you don't like this scrolling behavior, note that you can turn htmx.config.scrollIntoViewOnBoost to false.
Note that you can also specify element-specific scrolling behaviors using the scroll/show modifiers of hx-swap
I think the behaviour of hx-boost scroll to is not user friendly (unless I miss something). When you have, for example a menu, and use hx-boost. When something below the menu is replaced then whenever you use hx-boost it will jump to the div but your menu will not be in the screen anymore. Only can mitigate this by adding a # to the url or using one of the settings.
I think it would be better not to have this scroll functionality by default False on hx-boost and to turn it on explicit or have hx-scroll attr that you can set on particular hx-boost.
We also have to help:
htmx.config.defaultFocusScroll
htmx.config.scrollBehavior
The text was updated successfully, but these errors were encountered: