Comment 17 for bug 895733

Not really sure if this should be fixed for 0.2 given the already large amount of work to be done for the release and the relatively short amount of time until the release (of course no due date is set but I know we all want it out relatively soon), but bugfixing an already-implemented feature does have more priority than a general feature request... I'd have no objections if this was worked on any time immediately after 0.2, I just think the focus should be elsewhere for now... on 0.2's release.

If this is deemed an important issue for 0.2 though, then that's a different story and that's for the developers to choose.