On Tue, February 24, 2009 10:57 am, David Dorward wrote: > Nick Fitzsimons wrote: >> Actually, the specific purpose of the button is to allow one to have >> buttons that *don't* look like ordinary buttons: >> >> "Buttons created with the BUTTON element function just like buttons >> created with the INPUT element, but they offer richer rendering >> possibilities: the BUTTON element may have content. " >> <http://www.w3.org/TR/html401/interact/forms.html#edef-BUTTON> >> > No, you can have richer rendering possibilities without giving up > looking like ordinary buttons. The typical case is a button with an icon > on it. > > http://www.packagekit.org/img/kpk-confirm.png for example. >
True; I didn't phrase that very well. The point I was really trying to make is that to suggest that the value of the button element is that it *looks* like a button is to miss the point; the point is that it *behaves* like a button. In other words its purpose is to provide a specific kind of functionality, not a specific kind of appearance. Cheers, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/ ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
