I can't name one piece of UI in iCab that doesn't look like complete crap, honestly. Camino can do better than this.
I have to agree that iCab LOOKS like something cobbled together by a committee (ironic, really, given that it isn't!) and it is WAY behind in its support for almost any standard less than five years old, but in terms of useful functionality, it has support for a good many things that Camino just doesn't approach at all. (Page verification; accesskey support; link tag support...)
Personally, I'd rather see less consideration given to Camino's appearance and more to its underlying functionality. I have to say that love it as I do, currently Camino seems to offer little really, beyond a re-skinning of Mozilla. The only advantage it offers over Mozilla, that I can see as of this moment, is its awareness of the Network control panel settings, which means that I can safely move between locations with my laptop and have Camino immediately pick up the changing proxy configuration. The cost of that benefit is quite high, as far as I'm concerned, in terms of support for XML/XSLT (Camino can't render my latest web pages, whereas Mozilla / Firefox / Netscape all have no problems) and lack of support for anchor links' tabindex and accesskey attributes (thus making mouseless navigation a pain) to name but a couple.
So, if you'll indulge me, rather than delve ever deeper into how I think Camino should look (hell, just give us a collection of skinning options and let everyone pick their favourite widget set and colour scheme) I'll give my wish list for things it should DO. As I have a number of suggestions, each largely independent of the others, I'll split them over a number of messages for convenience of subsequent thread following...
-Steve -- _______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
