Comment 1 for bug 1261579

Kurt Griffiths (kgriffs) wrote :

This should be fixed under v1.1 API - let's leave 1.0 behavior in place.