Hi, I’m experiencing a scrolling bug after adding a widget via a Discourse theme component and could use some help fixing it. Paid.
Hi David, can you provide additional details. Like What component you added when this bug was noticed. Discourse version and build info.
It will give ppl a better idea if what you need help with as a scrolling bug is a bit vague.
.it is possible too that someone might have an easy fix by suggesting an alternative component.
You can also use your browser’s Dev tools to see if there are errors in the console.
4개의 좋아요
Hi Dan, thanks for the reply.
I’m using a theme component to display a widget that appears in the sidebar on desktops and at the top of the post on mobile.
The issue is that it seems to interfere with Discourse’s ‘jump to last read’ feature. When a user opens a topic they’ve read before, the page initially scrolls to the correct position, but then the widget seems to trigger a layout shift or a partial reload. This ‘glitch’ forces the page back to the top, losing the user’s place.
I’ve attached a video to show exactly how the jump occurs. I’m using the latest version of Discourse
Video:https://drive.google.com/file/d/1PjIkhRQPf4HFMDYDQ6oj3jsxgx0D8Zxr/view?usp=sharing
Live link: https://mytestsitetally.discourse.group/t/aave-14-test-eneded-proposal/27
1개의 좋아요
사용자가 Customization > Theme component 카테고리에서 나열된 것 중 하나를 사용 중이신가요, 아니면 커스텀 #customization:theme-component를 사용 중이신가요?
Custom을 사용 중이시라면, widget spu가 discourse의 변경 사항으로 인해 비추천(deprecated)된 것으로 기억합니다. 저도 아직 학습 중이라 정확하진 않지만, 이제는 glimmer component로 처리되는 것 같다는 생각이 듭니다.
저는 모바일로 보고 있습니다. 영상에서 확대하기가 어려우니 콘솔 오류의 스크린샷을 올려주시겠어요?
1개의 좋아요
Do you use plugin outlets to place the widget?
1개의 좋아요
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.