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
When doing a Content compare, the "Unable to compare files" warning when file size is 0 makes sense.
However when choosing the "Modified Date and Size" compare method, I am not expecting the content to be compared but still get the warning on 0 size files. In that context the warning does not make sense as it does not even apply. For that reason I consider this to be a bug.
The text was updated successfully, but these errors were encountered:
I cannot reproduce this problem.
Normally, "Unable to compare files" does not appear when comparing 0-byte files using the "Modified Date and Size" method.
I suspect you are comparing very special folders. What folders are you comparing?
When doing a Content compare, the "Unable to compare files" warning when file size is 0 makes sense.
However when choosing the "Modified Date and Size" compare method, I am not expecting the content to be compared but still get the warning on 0 size files. In that context the warning does not make sense as it does not even apply. For that reason I consider this to be a bug.
The text was updated successfully, but these errors were encountered: