Saturday, December 16, 2006

Random Computing Annoyances

Windows Media Player 11 doesn't play well embedded in Firefox 2.0. (It's fine in Internet Explorer, however.) In Firefox, embedded media players often lose their toolbars (they appear initially, but disappear moments later or when clicked), thus rendering them unusable. In addition, the toolbar nearly always "floats up" when it does work. Neither one of these bugs happen in IE 6 or 7. Lame.

I was pleased as punch to notice that Firefox 2.0 fixed the annoying "can't search in a textarea" bug that older versions had, which is nice, but Firefox 2.0 introduced the even-more-annoying "clicking a link jumps you to the top of the page instead of following the link" bug. Lame.

Thunderbird Portable 1.5.0.8 doesn't do well with more than just a few RSS feeds - it gets really slow (to the point of being unusable). It also isn't very reliable with Usenet newsgroup posting. 1.5.0.8 did fix an annoying problem with displaying newsgroup messages that was quite a problem in the older 1.5.0.5 (replying to a message would not allow you quote a previous message or even display it), but it's still not completely right.

And another thing - Thunderbird doesn't truly display plain text, even on the plain text (stripping out all HTML) setting. Some of the text is bold and some isn't. (There is no bold in plain text.) Thunderbird also seems to unexpectedly close sometimes (albeit rarely) when working with newsgroups that have a large number (roughly 5,000 or more) of messages in them (like "microsoft.public.internetexplorer.general" - LOL). Frustrating.

UPDATE: Thunderbird will close unexpectedly every time if you're using newsgroups and use the "click here to remove all expired messages" feature. It then opens up a second window (weird in itself), and then both windows will disappear moments later. Yeah, that's quality programming for ya. (Not.)

ANOTHER UPDATE: Another bug with Firefox (2.0.0.0 & 2.0.0.1) is that if Firefox gets a 404 error, it just doesn't display anything. The user has no way of knowing that the page couldn't be found, it just sits there and doesn't update anything - you're still sitting on the last page you were at. This is very deceiving, as the page displayed is not what's at the URL in the address bar.   =/

No comments: