Refenestration Daily.
If you’re running the nightly builds of Mozilla and it keeps crashing on exit, you’ve probably run into bug 182803 — “Mozilla crashes on exit if it connects to a SSL server” (either that or bug 156940, as both have over seven dupes).
And, I suppose your right-click context menus occasionally appear in weird places? Yeah, that’s bug 185107 — “Popup menu after right-click inside an iFrame is in wrong place”.
If you’re running a recent build of Mozilla and it’s been frequently crashing for you, you’re probably running into bug 179822 — “Flash4 / Flash5 crash Mozilla in recent trunk builds” (I ran into this on my parents’ machine).
The solution, of course, is to just download the latest Flash version (6). Either that, or don't run Flash at all ;).
Apparently, you can hit shift-enter in Mozilla’s URL bar to save the URL (I didn’t know that). Though its usefulness may not be obvious, this could be handy for saving XPIs to disk (they often insist on installing themselves if entered normally in the URL bar).
(Due credit to Bonsai Watch for making note of the bug-fix.)
Netscape 7 (final) has been released today. Compared with Netscape 6.2, this new version offers tabbed browsing, print preview, and full-screen mode (among other new features).
Of course, all of those features have been in Mozilla for ages ;). In fact, there’s little reason to try Netscape 7 (based on Mozilla 1.01) when Mozilla 1.1 is now available.
From The Register, anyone with a valid VeriSign SSL site certificate can forge any other VeriSign SSL site certificate in IE and Konqueror:
A chain is formed when an intermediate certificate is trusted between server and client. Supposedly, the intermediate is accepted only if it’s signed by the certificate authority as safe for the purpose. If it’s merely signed by another certificate’s key, it ought not to be trusted, or at least the user should be warned. Unfortunately, due to a preposterous security engineering oversight, IE and Konqueror don't bother to check this [&hellip]
Mozilla isn’t affected, as usual, though the author chides Mozilla as if maybe it’s a Mozilla quirk that is preventing the exploit. I would hope that The Register’s authors wouldn’t have such uninformed preconceptions :-/.