-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Wizard Step 5: Page often does not load forms below top area #5768
Comments
I experienced similar issue. And when I clicked on the "+" sign to add a new track, room, or session, it took a long time before the new field appeared and sometimes it didn't appear until I clicked the Save button. For some reasons it ran very slowly in the back |
The issue is there since last release as well, so not related to new changes. The reason is that the forms on this page are very complex (calendar and wysihtml) and ember renders them synchronously, so till each and every component is initialized and all callbacks are settled, only then it is visible to the user, so it can take 4-5 seconds. I searched a lot but couldn't find any way of deferring rendering in ember. Leaving others to have a go at it |
In that case I wonder if we need to split the form. However, from the logic things somehow belong together I think. |
I think just delaying rendering of stuff for 500-600 ms will work |
ok |
looking into it |
const speakersCallPromise = this.getOrCreate(data.event, 'speakersCall', 'speakers-call'); the problem is in getOrCreate because, it is used with cfs and copyright only and both two shows same error - |
The wizard step 5 often has problems loading content below the first section. It loads the top area and then loads the footer. All forms in-between do not show up.
This happens possibly when Internet connection is not very fast or if there are a number of sessions and rooms added. Hard-refreshing the page solves the problem, but even if the user refreshes the system it sometimes only loads the top area. This problem seems to be appearing since the redesign of the Call for Speakers area which can now be activated or deactivated.
The text was updated successfully, but these errors were encountered: