Fix asserts in test

[jakemac53]

A statement like 1 < 2 < 3 does not do what it appears at first glance ;). It actually compares 1 < 2, which returns true, casts that to a number (which gives 1), and then compares 1 < 3. This just splits up the asserts to do what I think was intended.

[jakemac53]

Heh, now the tests are actually failing as well :)

[jakemac53]

Looks like its assert.isTrue(giant.height <= 50); and assert.isTrue(giant.width <= 50); which are failing, I don't know where the 50 number came from or if its important, please advise me if you want the check to just change to a larger number (I get 58 as the actual value) or remove it entirely or what.

[bicknellr]

Can you rebase this? We just added box-sizing: border-box;, which I think the tester originally assumed; maybe it works now?

[bicknellr]

Whoops, actually we added box-sizing: content-box; - ignore my last comment. (Except for the rebase part.)

[jakemac53]

Ok I rebased, but it looks like the test is still failing. IMO this should still be merged even though it will turn the bots red, because it is a legitimate failure (its only green now because the test is broken...).

[notwaldorf]

Makes sense! Thanks for tracking this down!