[
https://issues.apache.org/jira/browse/ISIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-1285:
--------------------------------------
Fix Version/s: (was: 2.9.0)
Summary: [WON'T FIX] Provide the capability to disable the browser's
back button/ (was: Provide the capability to disable the browser's back
button/)
The long-term "solution" for this will be the Vaadin viewer.
> [WON'T FIX] Provide the capability to disable the browser's back button/
> ------------------------------------------------------------------------
>
> Key: ISIS-1285
> URL: https://issues.apache.org/jira/browse/ISIS-1285
> Project: Isis
> Issue Type: Improvement
> Components: Isis Core
> Affects Versions: 1.10.0
> Reporter: Daniel Keir Haywood
> Priority: Minor
>
> In the Estatio app (and presumably many others, too), when the user deletes
> an object then they are shown the "no results" page.
> What we have observed the user then do is to press the back button. This
> navigates them to the object just deleted; because it has been deleted, the
> Wicket viewer shows them an error page.
> With the RoutingService (introduced in 1.11.0) we have the opportunity to
> route the user to some other "more useful" object, eg the parent of the
> deleted object, or some other object recently visited, or the home page.
> Even so, if the user does press the back button, they would still see the
> same message.
> This ticket is therefore to provide an optional capability to have the back
> button disabled. Think it should be optional because not everyone (every
> programmer) will agree that back buttons should be disabled and in any case
> for some use cases, eg in read-only app, a back button is probably a good
> thing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
