Camino 0.9a1 Available

How does it compare to Safari 1.3? How does it handle JavaScript?

It seems a lot speedier. It's has one of the best Javascript implementation around since the inventor of JavaScript works on the javascript engine found in Camino. Please notice that a1 stands for Alpha One.

I got it, used it for a bit and couldn't take the constant beach-balling. I prefer the constant fan with Safari.

Web browsing on this Mac is the WORST experience

P.S. PB 17" 1.33 1GB single stick 80GB 5400rpm

Constant beach balling in Camino? Never seen Camino beachball once, even on an old G3 iMac.

This Camino is fast and slick for me.

Does anyone know if the bookmark bar uses a background image that can be changed? I like the smoothness of Firefox's toolbars better (though I don't like actually using Firefox on a Mac).

camino is (woah, i was going to say something good about camino, not now, it is slow as molasses and blinking cursor is killing me) by camino, or by this forum

you guys have got to get rid of the smilies, it was those that were ****ign with the computer I am sure, camino is great, this forum is not, we dont need 50 flashing smilies at the ready for each post

I was going to mildly flame you, Magnificante, until I reread your post and noticed you qualified your statement by limiting it to that particular PowerBook. So what's wrong with it thermally?

I agree. However, you can disable these (and other) annoying gif-animations by putting this in your user.js:

code:

---

user_pref("image.animation_mode", "none");

---

Speedy indeed. Typing is still painfully slow with any animated gifs. I'll have to check out brutal's tip.

I must say that I'm trying it for the first time in a long time and I find it quite speedy and pleasant overall.
Would like Spell Check. Would like RSS. Otherwise, every bit as nice or nicer than Safari 2.0

Trying to type posts in some fora with Camino is futile; each letter is a few seconds behind

I wonder what's wrong with this PB ?

Install Camino ExtraPrefs and set image animation mode to Once (under Display). That will fix the problem. Or you can modify your user.js file as someone suggested.

Thanks for the suggestion. Just reinstalled Camino and downloaded that app, changed the setting, and the results are the same

Unbelievably slowwwwwwwwwww typing and constant fan.

My PB sux I guess ...

Nah. Text fields sucking is a known issue in Camino. Fixing it is nontrivial... but we can always hope it'll be fixed for 1.0

On my powerbook, the latest camino 0.9a keeps hogging the processor, even when I am not doing anythingelse. The CPU usage goes from 20% to 78% in some sort of cycle. Going back to 0.8.4 for now.

Screenshots, please!

Here.

But that's not 0.9, Mr. Steal!

Huh? 0.9 is the same UI.

You sure? I think it's different.

Download and try it out.

0.9a1 uses the new tab-style. The screenshots show the old tabs.

Still no spellcheck

0.9 also has the unified toolbar under Tiiiigeerrrrr!

I'm keeping G4 Optimized FireFox build + very nice OS X only skin + array of extensions (AdBlock, All-In-One-Gestures, TabBrowser Prefs and BugMeNot).
While not as polished as Safari, it's the only browser I feel comfortable with.

It'll never get Default Browser Status on my box till that fawking text area lag is fixed!

Other than that, it really is a beautiful browser.

Yeah, I'll happily jump back to Camino once they use native textarea widgets.

The Camino team knows that the text lag is a major problem and we are working on solving it, it's high priority.

As far as native widgets for camino, it will never happen Why you might ask, well believe it or not but insiders say the Safari team abandoned the use of native widgets and have chozen for the custom drawing of them similar to what we do. They did that because native widget cause enormous rendering speed issues, in past versions of safari it was really hard to get it at the speed it was. You won't notice the difference.

In more recent nighlies we made an effort to further improve the look and use of our form widgets, and you can expect to see more improvements over time eventually including spellcheck. But we are a small team with little time and we have other bugs that are more important.