juuser
Well-Known Member
I know you guys/girls are busy atm, but I'm still adding it now, so I won't forget.
Users are complaining that when they open a form or list in front-end and try to make some interaction (e.g. click on the tab or focus on a field) they often get a JavaScript alert "Page is still loading. Please wait a few moments!".
After investing this a bit, I see that there is a blocking script added in F4:
\media\com_fabrik\js\dist\blockuserinput.js
And it's called from:
\components\com_fabrik\fabrik.php for lists and forms.
It is adding an overlay with the click event to "alert function" until the page is fully loaded.
I can sure understand that this is pretty annoying from the UX point of view and the regular users are just wondering like "It wasn't there before, why it's like that now. Updates always screw things up..."
I have disabled this feature and made several tests with multiple forms with different elements and I couldn't create any issues.
Is there any specific reason why this feature was added in front-end for F4? If there is, maybe it's possible to e.g. add the overlay only to action buttons or some other solution depending on what issues was it made to solve.
Thanks!
Users are complaining that when they open a form or list in front-end and try to make some interaction (e.g. click on the tab or focus on a field) they often get a JavaScript alert "Page is still loading. Please wait a few moments!".
After investing this a bit, I see that there is a blocking script added in F4:
\media\com_fabrik\js\dist\blockuserinput.js
And it's called from:
\components\com_fabrik\fabrik.php for lists and forms.
It is adding an overlay with the click event to "alert function" until the page is fully loaded.
I can sure understand that this is pretty annoying from the UX point of view and the regular users are just wondering like "It wasn't there before, why it's like that now. Updates always screw things up..."
I have disabled this feature and made several tests with multiple forms with different elements and I couldn't create any issues.
Is there any specific reason why this feature was added in front-end for F4? If there is, maybe it's possible to e.g. add the overlay only to action buttons or some other solution depending on what issues was it made to solve.
Thanks!
Last edited: