I'm not sure where to re-assign this bug, as in, what needs to happen for it to be solved.
In any case, the Firefox use case is now solved with Firefox 3.5's "private browsing".
I'm not sure where to re-assign this bug, as in, what needs to happen for it to be solved.
In any case, the Firefox use case is now solved with Firefox 3.5's "private browsing".