monkinetic weblog | redmonk.net

Camino is a web borwser for the Mac that wraps a native OS X interface around the popular Gecko rendering engine. It’s fast, and renders 99.8% of sites exactly like Firefox. After 1.0 came out, Idecide to try it out as my main web browser.

End result? I liked the interface a lot, but two things brought me back to Firefox:

• Find-As-You-Type (FAYT): I had grown completely dependent on this before moving to Camino as my main browser. Even after a month, I was typing to find stuff. Muscle memory is hard to change.
• Also in the muscle-memory category: Camino does not focus the address-bar when creating new tabs. My shortcut for a new Google search (a surprising percentage of my “new tab” activity) was Cmd-T-tab. I simply could not get my fingers to do Cmd-T-Cmd-Shift-F.
• Visual irritations: In the dock, I could not seem to stop clicking on that bright orange-and-blue globe. The click-area on the Camino icon seems smaller, and the blue icon blends in with about 8 other deep-sky-blue app icons.

I still detest the form elements in the Mozilla strain of Gecko. But apparently my fingers care more than my eyes do in this case.

Trying out a new browser: Flock

It has some interesting features: built in blog editor, del.icio.us integration, flickr integration.

Technorati Tags: browsers, del.icio.us, flickr, tagging

Josh Aas: Camino, Firefox on Mac OS X, and My MF Employment:

“I’ll also be working on making pages load faster, and Mac OS X rendering in general. This most likely includes making the gecko rendering engine use the Quartz API intead of Quickdraw. This will bring a lot of benefits, including making use of your graphics card to do a lot of the work that your CPU is doing right now because we use Quickdraw.”

This is great news! Both Camino and Firefox are great browsers, and they’re going to be getting better. Josh will also be helping to make Firefox look even more like a “Mac” app, with native widgets, etc.

You can’t use DHTML to change the contents of <table> or <tr> elements in IE6.

MSDN says this: “However, because of the specific structure required by tables, the innerText and innerHTML properties of the table and tr objects are read-only.”

Of course, the Safari and Mozilla/Firefox engineers seem to have been able to make the “structure required by tables” work for them, as my javascript works just fine there.

|Jodi| just a switched to Firefox:

I have tabbed browsing again! Popup ads will be blocked (more effectively than I.E. I hope), and the Google search box doesn’t take up space where the browser window should be.

You go girl.