Modified Date and Size compare generates "Unable to compare files" when file size is 0

[mach128x]

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.

[sdottaka]

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?