-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions inside a panel are divided between different pages in question-per-page mode #9557
Comments
Hi @SamMousa,
From what I gather, even though you enable the |
Correct, this used to be the behavior; and I also think it makes sense. |
@SamMousa If we decide to work with a "panel" like with a "question" then it should be another mode, "elementPerPage". Thank you, |
For us this is the primary use case: questionPerPage where matrix and panel etc are NOT split. We are currently unable to upgrade because this feature was broken / changed. I'm open to the arguments for the change, but it really isn't a minor change when the behaviour of all our surveys change 😅 |
@SamMousa That is true. I will take a look and see what we can do here. If there will be not many changes we could implement this functionality in a week or two. Thank you, |
If it cannot be resolved we will not be able to upgrade, which means we'll have to fork (and we do not have the resources or required skills for that) so I really hope you find a solution! Thanks for your efforts |
@SamMousa We decided to revert the previous behavior. We will may add an option if somebody complains. Thank you, |
Describe the bug
Before the big rework questions inside a panel were always shown on the same page. Since the rework they no longer are.
Steps to reproduce
https://surveyjs.io/published?id=70a80007-8ca6-4d68-99cd-c25564b365d5
Expected behavior
Panels are often used to create a kind of "composite" questions, it makes no sense to split them across multiple pages. Furthermore this is an undocumented (and I expect unintentional) change of behavior
The text was updated successfully, but these errors were encountered: