The page is on the developer.mozilla.org wiki, so you're welcome to help improve it.

I made this using the On Notice Board Generator.

Despite all the problems, the summit in Whistler has been worth it:

• I finally got to meet Mozilla security contributor Paul Nickerson. He had interesting ideas about how to find and prevent JavaScript privilege escalation bugs, which we discussed with Blake Kaplan.
• Firebug developer John J. Barton and I figured out why Firebug showed user agent stylesheet rules on his machine but not mine. He fixed the bug on the spot. This should let me switch from the aging DOM Inspector to Firebug for reducing layout testcases, saving me time.
• Rob Arnold took one of my extra Apple remotes and said he'd try to get it working with Firefox on Windows.
• Dave Mandelin's session about Static Analysis was enlightening.

While preparing a presentation for the Mozilla summit, I found a pretty S5 theme called Glossdeck. More importantly, I learned that Opera supports the Apple Remote for switching between slides.

I'd love to be able to do the same using Firefox rather than Opera. Using Opera is somewhat painful because switching slides using the keyboard is awkward (it uses space and shift+space rather than arrow keys) and Glossdeck has to be modified to work in Opera. But Firefox on Mac doesn't have a full-screen mode or support for the Apple Remote.

Boris Zbarsky's work in bug 113934 for reparenting Firefox tabs between windows should pave the way for Firefox to have full screen on Mac. It would be great if Firefox had Apple Remote support as well, perhaps as a DOM event sent to the focused web page.

If anyone at the Mozilla summit wants an Apple Remote, I brought three extras. I hear they work with Keynote and PowerPoint too.

Some people thought the reference to guns made Firefox too violent. After much discussion, Beltzner changed the title to "This might void your warranty!", which was a suggestion from Phil Ringnalda.

Today, Christopher Aillon of Red Hat filed a bug about the "warranty" string. He says it has caused several users to contact legal departments or IT departments with questions that should have been unnecessary.

My suggestion is "Caution: Firefox internals may be hot". As a bonus, it fails to make sense in Iceweasel-branded versions.

Additional suggestions may be hidden in the Firefox source tree. When Beltzner made the change from "gun" to "warranty", he also added a note to localizers, suggesting that the title need not be a direct translation from English but "should be attention grabbing and playful". At least three localizers substituted their own phrases. I'm curious what the strings say when translated back into English.

The strangest part: Firefox wasn't the first major browser to support transparent. Safari was.

These sites were broken in Safari too — until the webmasters got emails from Firefox users. Is Safari's market share really so low that even when Safari is the first to make a change that affects compatibility, Firefox helps Safari more than Safari helps Firefox?

Of course, sometimes it's better to prevent the memory corruption entirely, e.g. by adding a run-time check or by making all builds abort (not just debug builds).