This may not be a bug, but a function that is not yet implemented.
Try a snapshot build to see if it has been changed.