Michael,

Thanks for contacting us. We haven't tested it on that particular resolution and looking into the issue now.

This feature has been disabled in this release and will be made available in an upcoming build when we upgrade all the editors as well as the apex and visualforce parsers.

Sorry for the inconvience.