/validate wrongly passes, it actually fails (which is expected) due to the same error as /validate?valid=true fails.
The actual error is jsdom trying to getComputedStyle().WebkitTransitionDelay.split, where the WebkitTransitionDelay is undefined
If you open the generated page with a real browser, it behaves correctly in both cases.
I am unsure why it's the validate routes that trigger this, probably because they cause a transition when they resolve to the validated page or error page.
What do we do about this? How to report to jsdom?