Skip to content
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

[stable23] Fix default toast message for failed uploads with HTTP/2 #32895

Merged
merged 1 commit into from
Jun 22, 2022

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #32878

Copy link
Member

@danxuliu danxuliu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and works 👍

This was referenced Jun 17, 2022
@blizzz blizzz added the 4. to release Ready to be released and/or waiting for tests to finish label Jun 17, 2022
@blizzz
Copy link
Member

blizzz commented Jun 21, 2022

/rebase

When an upload fails a toast is shown with either a specific message or
just the textual part of the HTTP error code (which comes from the
upload failure handler and set by "jQuery.ajax()". However, if there
is neither a message nor an error then the toast will show the default
message from the Toastify-js library, which is an undescriptive "Hi
there!".

When HTTP/2 is used Chromium does not provide the textual part of the
HTTP error code, so when an upload fails the toast can receive an empty
message and thus just show "Hi there!". Now an explicit message is
provided as a fallback to prevent that.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@nextcloud-command nextcloud-command force-pushed the backport/32878/stable23 branch from 29c4ce5 to 4cd8ad0 Compare June 21, 2022 17:34
@blizzz blizzz merged commit 63fb2e0 into stable23 Jun 22, 2022
@blizzz blizzz deleted the backport/32878/stable23 branch June 22, 2022 18:12
@skjnldsv skjnldsv mentioned this pull request Jul 5, 2022
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants