Hi, based on Frank's last comment, I was hopeful that the release of 5.0.18 would contain a fix for this. I don't see bug 33299 in the release notes, however, so I'm guessing the answer is no.

Seeing bugzilla's listing for bug 33299 being "verified" on 5.0.17 led me to think it might be, though I may be understanding the bug lifecycle incorrectly, too. Any word on this? Thanks!