If a file was processed that had no chunks, it would be listed as

whitespace-only. This was because the logic computing this would default

to whitespace-only, and then override that if it found any non-equal

chunks that contained real changes. For empty files, there were no

chunks to process, so this flag would be incorrectly set.
Even if the flag was correctly set, it still looked broken, as the

message describing that it's whitespace-only would be hidden by default.

The CSS rule for this has been removed.
While here, I also fixed up the labels for the toggles to not have such

varying mixed caps. That's been bugging me.

Viewed an interdiff that resulted in files without chunks. They no longer

appeared as whitespace-only.
For valid files with that flag set, I saw the helpful text.
The toggles stopped bothering me as much (though they still bother me.)