2.4.8 fixes the sign-in windows that open when you connect an account on a website. In 2.4.7 some of them stayed blank, and the first fix made them close themselves.
What was going on
Many sites open the sign-in window empty, straight from your click, and send it to the real sign-in page a moment later, once their server has answered. S3 had its own checks on top of the browser's: a window could only load the address it was opened with. Because that address was empty, the real sign-in page that came a second later was refused.
Our first fix tried to recognize that second step more cleverly, and it still missed the real flow: the window opened, flashed white and closed. So we stopped guessing. A window you open with a click now behaves as it does in Safari. Once it is open, it can go wherever the sign-in takes it, and it stays linked to the page that opened it, so it closes and hands back to that page when you're done.
Windows a page tries to open without your click are still blocked. If the click came from another site's embedded part of the page, S3 asks once before opening anything. Every pop-up decision is now written to a local log with just the site names and a reason, so a problem like this can be traced directly next time instead of guessed.
Open blocked window
When S3 blocks a window, a small Open blocked window button now appears on the right of the address field. If S3 knows where the window wanted to go, it opens that page in a new tab. If not, it offers to allow pop-ups on that site, so you can press the site's button again.
Download S3 Browser 2.4.8 · or choose Restart to Install when S3 offers the update.