Comment 4 for bug 261520

I fixed this during the update to 0.4 API.