Thanks Leo interesting points.
Imo if you have a security issue with a field being disabled then you have
a really weird app imo.
If JSF was used to define disabled then javascript hacks needs to be
prevented but if disabled was never set then I can't think of a use case
where it would be a risk
On Tue, Jun 10, 2014 at 4:38 PM, Leonardo Uribe wrote:
> The thing to remember here is "never trust on the client".
> No matter how intelligent we want the client to be, in cases like this one
> the state on the server is the king, and that will not change (because we
> can't!).
>
and this is wh
Hi
This is something complicated. If you disable a link on the server, you
don't want a javascript that enable it on the client side, submit it and
then found that something that you don't expect has happended on the
server, right?. Who manage "disable" attribute? The client or the server?
If an a
Howard, thanks for the links and interest.
In my case I already rewrote all my pages but I still think that error
message is wrong.
This is our use case:
[X] Use Defaults for everything
Once the user unclicks that checkbox 5 inputs are editable otherwise they
get default. Since they get default
Leonardo, what are your thoughts on this thread? thanks.
On Wed, Jun 4, 2014 at 11:43 AM, Karl Kildén wrote:
> Howard,
>
> To do that one would need a purpose. I fail to see the benefit other than
> bending the knee to a JSF limitation.
>
>
>
>
> On 4 June 2014 16:48, Howard W. Smith, Jr. wro
Another similar (really old) discussion where BalusC responded on the topic
in 2009.
https://community.oracle.com/thread/1719243?start=0&tstart=0
On Sun, Jun 8, 2014 at 6:34 AM, Howard W. Smith, Jr. wrote:
> Karl,
>
>
> http://stackoverflow.com/questions/10021634/jsf-when-disable-component-i
Karl,
http://stackoverflow.com/questions/10021634/jsf-when-disable-component-its-value-does-not-make-into-the-request-map-parame
see the question and BalusC's answer, please.
On Wed, Jun 4, 2014 at 11:43 AM, Karl Kildén wrote:
> Howard,
>
> To do that one would need a purpose. I fail to see
Howard,
To do that one would need a purpose. I fail to see the benefit other than
bending the knee to a JSF limitation.
On 4 June 2014 16:48, Howard W. Smith, Jr. wrote:
> Karl, if Javascript was written to enable field, why is there not
> Javascript to disable before submit?
> On Jun 4, 201
Karl, if Javascript was written to enable field, why is there not
Javascript to disable before submit?
On Jun 4, 2014 8:33 AM, "Karl Kildén" wrote:
> Hi,
>
> my app recently upgraded from JSF 1.2 had a broken page with this in the
> log:
>
> WARNING: There should always be a submitted value for a
Hi,
my app recently upgraded from JSF 1.2 had a broken page with this in the
log:
WARNING: There should always be a submitted value for an input if it is
rendered, its form is submitted, and it was not originally rendered
disabled or read-only. You cannot submit a form after disab
ling an input
10 matches
Mail list logo
