I can confirm that the 3.6 alpha build contains the fix.
I suspect that a 3.5 point release will not contain this fix, unless we petition the Mozilla developers to incorporate it. The Ubuntu Mozilla Team could also cherry-pick the fix (when somebody identifies it) into the Ubuntu build, but I suspect they would be weary of diverging from upstream's code too much, for a relatively insignificant issue.
I can confirm that the 3.6 alpha build contains the fix.
I suspect that a 3.5 point release will not contain this fix, unless we petition the Mozilla developers to incorporate it. The Ubuntu Mozilla Team could also cherry-pick the fix (when somebody identifies it) into the Ubuntu build, but I suspect they would be weary of diverging from upstream's code too much, for a relatively insignificant issue.