Hi Cagatay,
thanks for that. The question is now whether that different behavior is a
problem if I extend tomahawk's command button renderer.
The output of my renderer is:
<button id="documentList_1" name="documentList_1" type="submit"
value="View Documents"
onclick="if(typeof
window.getScrolling!='undefined'){oamSetHiddenInput('editUser','autoScroll',getScrolling());}"
class="positive"><img src="images/Right1_h.png" />
View Documents
</button>
So the content will be the same. The action is triggered by some javascript,
isn't it?
Thanks
Rene
-----Ursprüngliche Nachricht-----
Von: Cagatay Civici [mailto:[email protected]]
Gesendet: Dienstag, 17. November 2009 11:27
An: MyFaces Discussion
Betreff: Re: Render commanButton as <button>
Hi Rene,
>From w3c;
*Important:* If you use the button element in an HTML form, different
browsers will submit different values. Internet Explorer will submit the
text between the <button> and </button> tags, while other browsers will
submit the content of the value attribute. Use the
input<http://www.w3schools.com/tags/tag_input.asp>element to create
buttons in an HTML form.
On Tue, Nov 17, 2009 at 10:16 AM, "Günther, Rene - Innflow AG" <
[email protected]> wrote:
> Hi,
>
>
>
> just wanted to ask whether it could cause issues to overwrite the renderer
> of command button to write <button></button> tags instead of <input
> type="submit/image">? I tried it and it seem to work but I am worried that
> this might cause issues in certain scenarios which I don't know of.
>
> I did that to have more CSS / layout options available.
>
>
>
> Thanks !
>
>
>
> Rene
>
>
