Category Archives: firefox


>Firefox was released. Nothing much, ‘just’ a single security issue was fixed, a crash in the JavaScript garbage collector.

Leave a comment

Posted by on 21 April 2008 in firefox, firefox2, mozilla, release, security


>Firefox released

>Firefox was released. No features added, just some security vulnerabilities fixed.

Leave a comment

Posted by on 28 March 2008 in firefox, firefox2, security


>Color spaces in Safari and Firefox 3

>Since long, Safari 3 has supported support for color profiles (see the WebKit blog entry Color Spaces). Now the Firefox 3 betas also come with support for it, although it’s disabled by default.

To enable support for color spaces in Firefox 3 beta 4, do the following:

  1. Go to about:config
  2. Confirm you want to edit settings
  3. Set the option “gfx.color_management.enabled” to “true”
  4. Restart Firefox

Now check out some sites. Like with Safari 3, colors in sites may look quite different, since an extra step is applied to convert the colors from the original color space to the color space for your screen.

For web developers this smart behavior introduces some challenges, since sites now look different on different browsers on the same platform. Of note, Safari and Firefox implement color space support differently: Safari only adjusts images (such as PNGs), while Firefox also adjusts CSS colors.

So even between Safari and Firefox 3 with color space support enabled, there are differences, as reported in Firefox bug report #424356 (see the attached screenshot) Firefox seems to do a better job here than Safari, because with the latter the colors of different elements on a web page may mismatch, as can be seen (with Safari 3.1) on a website like

For web developers, here’s a pragmatic approach:

  1. make sure your images do not include a color profile (saves ~4KB)
  2. do not specify colors in CSS if there is an image that needs to match the color, instead use a dot image with the exact same color

Still your site will look different on browsers with or without color space support, but at least you work around the problem in Safari 3.1.


>Improve website performance with Yslow

A while ago I blogged about Firebug, a great Firefox extension for analyzing web pages (including CSS and JavaScript) and the interactivity between a browser and web servers.

Yahoo! have built on Firebug to produce a tool that goes even further. They call it: YSlow for Firebug.

Based on “Thirteen Simple Rules for Speeding Up Your Web Site” YSlow analyzes a web page, produces some reports (with a score card) and gives advice on improvements. This can be a great help in improving your website’s performance and reduce it’s bandwidth usage.

Also see this blog entry:


>Firefox find-on-page highlighting like Safari 3

>Although I’m not too enthusiastic about the new Apple Safari 3 beta, one simple feature I do appreciate a lot is the way it highlights find-on-page results. It really makes day-to-day browsing more productive.

I wonder if there is any Firefox 2.0 plugin that can do something similar. So far I haven’t been able to find anything.


>Configuring a new iMac 20-inch [updated]

>For a customer I bought an iMac 20-inch (2.16 GHz C2D, 2GB), which I’m now configuring. On top of Mac OS X 10.4.9, iLife and iWork ’06 I’m customizing the machine as follows, to suit his needs:

Some challenges I’m still facing:

  • Which version of Office 2007 should I choose? I expect only Word or Excel is occasionally needed.
  • How do I convert all current faxes from WinFax Pro 9 to the Mac?
  • How can I use VNC through the DSL modem and firewall? — Update: this is fairly easy with an SSH tunnel.
  • (How well) does VueScan integrate with PageSender? Or how well can I make them integrate using Automator?

>Firebug is great!

>Any webdeveloper trying to debug CSS, JavaScript or AJAX should use a good tool like Firebug, a Firefox extension. It works for sure under Firefox 2.0.

One screencast says more than a thousand words:

Leave a comment

Posted by on 23 March 2007 in ajax, css, firebug, firefox, javascript, Web Development


>Minor QuickTime annoyances

>If you read previous of my posts, you must have concluded I seem to enjoy listing (minor) issues I find in applications. Somehow I indeed do. I’d like to report these issues to their creators, but then this typically costs a lot of time and effort. Just listing stuff on your blog is easier and then you can still use that information later to submit some issues later on.
Here’s some feedback on QuickTime issues:

  • When I right-click in a QuickTime area on a web page, then I get a number of options in a context menu. However, if I want to choose none of the options, there’s no way to get rid of the context menu. It seems I have to click one option. Even worse, even if I move to a different tab, the context menu does not go away and still shows up on the other tabs.
  • When a QuickTime movie is not completely loaded (yet) but still starts playing and then gets to the end of the already loaded content, it restarts at the beginning of the clip. That’s plain annoying.
  • When the loading of a movie does not seem to progress, for example after the internet connection has been disrupted, there’s no abvious way to see whether it is still loading and no obvious way to make it continue the loading without restarting.
  • With a paused QuickTime movie on a web page, scrolling makes the movie appear and disappear, showing the background behind the movie instead of the movie itself.
  • A movie cannot be saved until it is fully loaded.
  • The plugin context menu has two similar items: Save as source and Save as QuickTime-movie. Both save as a file with the .mov extension. The difference is not obvious at first glance.

This is QuickTime (Pro) 7.1.3 with the QuickTime Plug-in 7.1.3 on Firefox 2.0.

Leave a comment

Posted by on 2 December 2006 in apple, firefox, firefox2, macos, macosx, qt, quicktime


>Firefox on Mac OS X

>I’ve been running Mozilla Firefox 2.0 on Mac OS X 10.4.8 for a couple of weeks now. Overall it works quite well, but there’s a couple of issues:

  • It requires a forced stop on a regular basis (like once a day).
  • When searching (Cmd-F), the back key combo (Cmd-LeftArrow) does not work anymore.
  • When editing a text field in Blogger Beta, switching to a different tab keeps the blinking cursor visible.

Still I prefer using Firefox over Safari. One of the reasons is that in Safari, the Blogger Beta post edit screen does not properly show the icons (bold, italic, etc.) properly.