You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a problem only with a particular file (or file type), use this form instead
Windows 7, 8 and 8.1 are no longer supported. This is not a question about Windows 8.1 or older.
Operating System
Windows 10
Steps to reproduce
Merge damaged files
Expected behavior
A while back I complained about it silently failing on some files. This was soon fixed, upon completion it gives a warning about the file size not being as expected. Unfortunately, this shows up on the merge complete notice--which soon self-closes. That means if you're not paying attention to it you won't see the error--come back to it and there's absolutely no difference between merge successful and merge unsuccessful.
If there's a warning leave the box open!
Actual behavior
See expected behavior.
Share log
Not relevant
The text was updated successfully, but these errors were encountered:
that's a good point, the only problem is that some people might not want a modal to block their whole flow just because of a warning. so need to find a way to still show it as a toast, but not auto-close it after x seconds.
I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first
Operating System
Windows 10
Steps to reproduce
Merge damaged files
Expected behavior
A while back I complained about it silently failing on some files. This was soon fixed, upon completion it gives a warning about the file size not being as expected. Unfortunately, this shows up on the merge complete notice--which soon self-closes. That means if you're not paying attention to it you won't see the error--come back to it and there's absolutely no difference between merge successful and merge unsuccessful.
If there's a warning leave the box open!
Actual behavior
See expected behavior.
Share log
Not relevant
The text was updated successfully, but these errors were encountered: