Hi Duane,
Actually there was an issue in Firefox 4 that I solved previously with a workaround, probably the same issue exists in Firefox 5 but the workaround in my code is only applied currently for FF 4 since FF 5 just came out very recently.
I haven't upgraded yet to FF 5 but I will test it when I do and see if the same workaround can solve it. But the solution would be included in the next release of mojoPortal, there is not a way to solve it in the current release. The next mojoPortal release will probably be in early to mid July.
Best,
Joe