Brian Hogan wrote: > I have found that the best solution to this problem is to use an image > button for the submit button, and then use css to apply the same image > to the back link. It's accessible and requires no javascript.
That's not a bad approach. It would be one way to get a consistent look, although not a platform specific look. However, recently I've taken the up the practice that I see a lot of Rails developers using: I just accept the web by using a standard submit button, and standard hyperlink. Then I try to design my pages around that concept. There already exists a "mental model" around form buttons and hyperlinks. Trying to hide the differences between them behind a visual facade can actually work against the existing "mental model." Making a link look like a button might actually be more confusing. For example when I see a link I know right away that clicking it will simply take me to another page. It won't submit any information related to the form. At least that's the expected behavior. The "mental model," however, can be broken in a number of different ways. For example, it is possible to attach a script to a link that does actually submit information from the form, or change some state on the server. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
