(In reply to comment #3) > It is working as expected in that release (albeit #78845 is still present). Bug 78845 fixed in 4.3.1 (see the whiteboard). If you still reproduce that issue with 4.3.1 release or daily, just drop a comment in that bug.
(In reply to comment #3)
> It is working as expected in that release (albeit #78845 is still present).
Bug 78845 fixed in 4.3.1 (see the whiteboard). If you still reproduce that issue with 4.3.1 release or daily, just drop a comment in that bug.