andrewlucking.com

Today, nearly 4 years, 123 comments and 42 votes after having been opened, Mozilla bug 228684 – Remember overrides of Certificate Domain Name Mismatch was updated to Resolved.

It seems there is a conflict between the beta of the Flash Player 8 (Maelstrom) plugin for FF and the adblock extension. A quick google turned up this entry in Sean Corfield’s blog which contains a short discussion of the issue in the comments section. Current solution: disable Obj-tabs (under adblock options).

Speaking of the player beta I’ve been checking out some of the various Maelstrom examples (in between testing existing content of course) but haven’t come across any news of the ECMAScript for XML (E4X) functionality that was suspected to be included. I wonder if thats beacuse it’s not ’sexy’ enough for the current Maelstrom ‘discovery’ commotion or perhaps it didn’t make it in?

update: Ahh, no E4X yet - Darron Schall pointed to a comment from David Mendels in Brooks Andrus’ blog. David is an executive VP at Macromedia. (I sure hope someone over at Adobe’s taking notes).

I’m catching up on my reading so this may be old news.

It looks like an alpha of mozilla.org’s Devmo site has gone live here:
http://developer-test.mozilla.org/
They’ve gone with a wiki format and have posted a list of the Netscape DevEdge material that they’ve brought over thus far. Woot, the core javascript docs are in there:
http://developer-test.mozilla.org/docs/JavaScript

update: Woops, I forgot to title this entry. Fixed that.

Here is a link to a mozillazine.org knowledge base article detailing the various about: links supported by FireFox (and Mozilla):
http://kb.mozillazine.org/About_Protocol_Links

Those cache links are good to know about - they’ll come in handy when debugging. The award for kookiest goes to about:kitchensink. And you know what? The length of that bugzilla thread discussing it does not surprise me one bit.

flex-mx.com points to a recent entry in Mitchell Baker’s blog providing some good news about the Netscape DevEdge material. Apparently AOL has agreeed to grant a license to the Mozilla foundation allowing them to host and maintain the docs. The devedge.netscape.com material was one of my primary JavaScript references before the site went dark back in the fall.

From the update post it seems like the DevMo content will most likely be hosted at http://developer.mozilla.org/. Presumably the links here will start working again.

Excellent.

I tend to use the secure web interface that my webhost provides for checking my email rather than go through the effort of configuring an email client on my computer. (It must be some sort of commitment thing).

Anyhow, while the interface is on an encrypted URL within my domain the security certificate belongs to dreamhost.com. This triggers a domain name mismatch warning in Firefox each time I check my mail. I did some poking (and googling) around to see if there was a way to store that I have accepted the mismatched cert but it doesn’t seem to be possible. I did come across this thread in a readlist.com archive but responses seemed to come more from the “I don’t think you need to do this” point of view. Perhaps I’m missing something but to me it makes sense to add a “don’t ask me again for this domain” checkbox (or the like) on the dialog. There’s a freakin’ “ok” button that accepts the certificate on a per session basis so obviously the message is a warning.

Any ideas or is this just another nudge for me to get on with it and install Thunderbird?

update: Solved. The Remember Mismatched Domains extension is over here:
http://www.andrewlucking.com/archives/2005/08/remember-mismatched-domains/

Brandon over at devnulled.com blogged about a simple way to improve firefox page loads in this post. I just made the suggested tweaks and had to join the clamour. A definite improvment! It would appear that the suggestion originated here.

update: To shed some more light on how this tweak works John Dowdell points to a mozilla.org FAQ item on pipelining: http://www.mozilla.org/projects/netlib/http/pipelining-faq.html

Wow, that was easy. I had installed 1.0 when it was released last week but rolled it back to the PR (preview release) when I found some of the extensions I consider essential were not yet updated. I took the 5 minutes to do it again this morning and we are back in business. Wish I could write software that was as pleasant.

peace.