But avoiding session scoped beans makes much harder to develop an
application, and application will be slower then using session scoped
beans (especially in combination with EJB3 session beans).
Rene Guenther wrote:
The disabling of JavaScript is no problem for our intranet
application, since our application requires JavaScript. Maybe someone
will argue now that applications should not require javascript, but as
long as the clients are happy with the application, we are happy :-)
But you are right with the script not working anymore in > 2.0.4. I
just tested it, the strange thing is, sometimes it works. I dont know
why though.
If disabling of back button functionallity is not possible, probably
the best thing is to avoid session scoped beans as mentioned before.
Rene
On Tue, 07 Aug 2007 11:37:36 +0200
David Delbecq <[EMAIL PROTECTED]> wrote:
Both plain script a onload fail to prevent history navigation in
firefox. 2.0.0.4.
The user have to manually 'reload' the previous page to activate the
foward script. Once he has reloaded, it always prevent navigation.
Untilm user disable javascript and goes back to that page. At that
point, he can go back and forth as much as he want, reactivate
javascript. It will again not work until user click the reload button.
So, i won't build my application assuming user won't be able to use the
"back" button. Not to mention users usually don't like to be forbidden
the easy to use "back" button.
En l'instant précis du 07/08/07 08:35, Rene Guenther s'exprimait en ces
termes:
Hi Sergio,
we use on every JSF page the following javascript code:
<script>
history.forward();
</script>
When the user pushes back button he is automatically forwarded again.
Just a workaround though.
Regards
Rene
On Mon, 06 Aug 2007 15:15:31 +0100
Escalada Sergio <[EMAIL PROTECTED]> wrote:
Hello.
I am using MyFaces 1.1.5, Tomahawk 1.1.6 in my WEB Aplication, and
i have a requirement mandatory to disable the browser back button
while the user is interacting with the aplication. The requirement is
really serious and compromise the usability of the aplication, can
anyone tell me if it is possible to do anything to avoid the use of
the browser back button?, or at least to control the use of it trying
to avoid the consecuences it carry.
Thanks in advance, sorry for my english.
--
http://www.noooxml.org/
