click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Schmidt (JIRA)" <>
Subject [jira] Commented: (CLK-520) Button should be rendered as "button"
Date Fri, 17 Apr 2009 16:10:14 GMT


Joseph Schmidt commented on CLK-520:

> Doubt ActionButton is used much
I use it in almost every page. (also in quite a few pages I have more of them).
An ActionLink is much harder to style to render so that it looks and behaves like a button.

> however Submit is used for submitting Forms and one of the most used controls. 
Yes, but because it's an Input, instead of button, it's impossible to add an icon to it (e.g.
for 'add', 'save', 'edit' etc. icons. Most commercial applications require this too.)
Also I'm curios why the 80/20 rule doesn't apply here anymore ?
*Most* of the users would benefit if the Button would be really a "button".

> Button should be rendered as "button"
> -------------------------------------
>                 Key: CLK-520
>                 URL:
>             Project: Click
>          Issue Type: Bug
>            Reporter: Joseph Schmidt
> Button controls should be rendered as "button" HTML elements not as "input".
> The actual implementation seems to use "input" of type "button" but that is quite misleading
since with
> that type of tag, it's not possible to embed icons or span tags or something else(the
"button" tag would normally allow) in the button to make it look better or what the requirements
> The "input" element seems to have only a "value" attribute.
> E.g. adding an icon before the button text (in the button body) it's a very common requirement
(so I think it should work as default).
> Button tag also has "type" (e.g. of 'submit', 'cancel' , 'button'), so derived controls
of class Button would behave as before.
> thanks,
> Joseph.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message