I can't give you a fix off the top of my head... that being said.. Your designer should forage into usability.
You can style buttons - in a limited fashion and its not consistent across browser types - its a PITA! Don't do it! The last thing we need is buttons that don't look like buttons. The reason most apps (web and non web) use normal form controls is because users understand them and are familiar because their OS will look the same. In the same way links should 99% of the time have a blue underline. Instantly you know what its behaviour is. "Oh this submits a form, Oh this is a link it will take me to a site" I know there has been some "make web 2.0 button tutorial" stuff floating around recently - perhaps they've seen these and want to add some drop shadows and [EMAIL PROTECTED] :) but if your design really needs custom form submits to make it work...rethink the custom form design and make it standard. Form controls are a solved problem. In summary - regardless of the technology in use - in my personal view.. from studying this stuff for years.... custom buttons is a waste of time and is actually worse for your app from a usability stand point. Given the right argument I might be swayed in certain circumstances - but that's the general rule of thumb. I work very closely with a designer who was initially into making everything his canvas! Now he understands usability concerns - and also that it doesn't effect creativity, but actually makes the apps better. Edvin Syse wrote: > > Hi Ned, > > thanks for your reply. I agree with your point of view. Today, however, > we got bitten because the designer wanted to change all buttons by > hiding them with jquery, and adding an anchor right after it in the > dom-tree, so he could style them the way he wanted it (not possible with > buttons he tells me). > > You can see his lovely button on this page: > > http://sd.tornado.no/domorder/search/query/testdomain > > The way he then triggered the submit buttons is with the following > Jquery code: > > $('.btn.submit').click(function(){ > $(this).prev().click(); > }); > > This works most of the times, but sometimes, when the wicket ajax stuff > includes references to 'this', the approach doesn't work, and wicket > tells me that the ajax request was stopped 'because of precondition'. > > That's when he started bitching about the Wicket way of inlining > JavaScript, so I thought I'd be nice to hear some opinions :)) > > -- Edvin > -- View this message in context: http://www.nabble.com/Wicket-and-inline-JavaScript-tp17402101p17417072.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
