Comment 22 for bug 294712

Any chance to get this fixed in upcoming Firefox 3.1 release?