We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When AJAX response is not returned (timeout) or wrong (non-200 status code or wrong JSON/JS syntax)
then the response must be handled in Atk4 frontend JS and the original AJAX request must be canceled (when not-finished yet, like timeout)
demos/_unit-test/late-output-error.php can be used for Behat testing of wrong AJAX responses
demos/_unit-test/late-output-error.php
The text was updated successfully, but these errors were encountered:
another example is atk4/login@f475d95 and atk4/login/demos/admin-roles.php demo
atk4/login/demos/admin-roles.php
when
is clicked and then
is clicked, faded background is the only thing displayed, no error message, nothing, in network view the following shown:
for normal users, it is nearly impossible to tell the problem
Sorry, something went wrong.
another easy steps to reproduce/modal usecase described in #1883 (comment)
mostly fixed by #1925 and #1919
No branches or pull requests
When AJAX response is not returned (timeout) or wrong (non-200 status code or wrong JSON/JS syntax)
then the response must be handled in Atk4 frontend JS
and the original AJAX request must be canceled (when not-finished yet, like timeout)
demos/_unit-test/late-output-error.php
can be used for Behat testing of wrong AJAX responsesThe text was updated successfully, but these errors were encountered: