January 4, 2017
Replied to a post on github.com :
I know this was fixed in a prior version, but it looks like it's slipped back in again in v3.0.2? Perhaps it was fixed in one of the dev versions I downloaded from Github, but it's not in the production version on WordPress.org at the moment.