Ran into this problem with v7.0. 

Bottom Crop only accepts values between 1.0 and 1.0—uhhhh, ooookay.

Could not input normal values like .5 or 0.5.

That one is also available in version 6.

Top < Bottom <= 1 e.g bottom value should be between top and 1.0. A top = 1.0 has no rational sense: any bottom is inavalid

Igors is correct that Navstar’s example shouldn’t work, and the issue Navstar brings up is still an issue.  If I type an incorrect number (i.e. 2) into the dialog box, I can not type a decimal number into the subsequent ‘out of range’ dialog box.  This is a minor annoyance.

Take care,
Yon

Feature suggestion - would be nice if crop could be expressed in pixels for increased precision - I’m currently doing a job involving a large canvas that I need to crop into and it means lots of converting pixels into decimal fractions…

It would also be cool if I could just draw a crop box right in the viewport.