On the other hand, one of the major plusses for Camino is that it is more tightly integrated with the OS than FireFox is, so it also uses the OSX form elements au-naturale. (And pays attention to the proxy settings in the OS, which is rather handy on my laptop.) I think what you really meant to say is that it treats the abuse of its own chrome with disdain... many of us still believe that styling of Chrome is a Bad Thing(tm)
Mike > -----Original Message----- > From: listdad@webstandardsgroup.org > [mailto:[EMAIL PROTECTED] On Behalf Of Nick Fitzsimons > Sent: Thursday, November 16, 2006 4:33 PM > To: wsg@webstandardsgroup.org > Subject: Re: [WSG] Safari DOM inspector > > On 16 Nov 2006, at 11:41:40, Barney Carroll wrote: > > > > > I do know that generally it [Safari] treats the styling of forms > > with disdain (plus I'm using javascript on them for display > > purposes, oo-er). Is there any other significant 'bug' I should > > know about? > > > > Long, long ago - well, within the last few years - there was a > general belief that styling of form controls was a Bad Thing from a > usability perspective, as it meant the user got an experience with > web form controls that wasn't consistent with the appearance of such > controls within their operating system. A number of cutting-edge and > utterly horrible examples of over-the-top styling of form > controls by > too-enthusiastic designers helped to reinforce the idea that it > shouldn't be done. > > In particular, Safari has always enforced the idea that a checkbox > (for example) is going to look-and-feel exactly the same in a web > page as it does in any other part of the OS user interface. > > Now that we've all grown up a bit, and (much more importantly) we > also know that (with appropriate usability considerations by > designers) users don't have a problem with pretty form controls, it > is generally accepted that it is an OK thing when done in > moderation. > Even Apple/the Safari team have accepted this, and the next version > of Safari will be much more permissive of widget styling, by > providing a mechanism to relax the enforcing of OS conventions > through the W3C standard method of providing vendor-specific CSS > extensions. > > Dave Hyatt, who left Mozilla to become lead developer (or > something - > don't know his actual title) on Safari, has blogged about it: > <http://webkit.org/blog/?p=17> > > Regards, > > Nick. > -- > Nick Fitzsimons > http://www.nickfitz.co.uk/ > > > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
