[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-user
Subject:    AW: Render commanButton as <button>
From:       "Günther,_Rene_-_Innflow_AG" <rene.guenther () innflow ! com>
Date:       2009-11-17 16:05:53
Message-ID: 008f01ca679f$d72c5bf0$858513d0$ () guenther () innflow ! com
[Download RAW message or body]

Yes, everything seems to work. I tried with save button (immediate = false), delete button (with javascript confirm) and cancel button (immediate=true). I tried in IE and Firefox. All navigation rules work and the action methods are executed as well.
Everything worked at once, which is probably worrying me the most ;)
I will post again if anything fails later.

Cheers
René


-----Ursprüngliche Nachricht-----
Von: Cagatay Civici [mailto:cagatay.civici@gmail.com] 
Gesendet: Dienstag, 17. November 2009 16:35
An: MyFaces Discussion
Betreff: Re: Render commanButton as <button>

I believe the javascript is for preserving the page scroll state,
type="submit" causes a page submit. Well if browser sends clientId as a post
parameter it should work. But again the doc says it may not be the case as
always. Does your action method get executed with your custom tomahawk
button?

On Tue, Nov 17, 2009 at 11:06 AM, "Günther, Rene - Innflow AG" <
rene.guenther@innflow.com> wrote:

> 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:cagatay.civici@gmail.com]
> 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" <
> rene.guenther@innflow.com> 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
> >
> >
>
>


[prev in list] [next in list] [prev in thread] [next in thread]