RE: [agile-usability] Back button
- Sorry for the off topic everyone, I didn't notice reply went to group and not to the person. Won't happen again.Jade OhlhauserProduct ManagerRPM Softwarewww.rpmsoftware.com 403-265-6727
From: Jade Ohlhauser [mailto:jade@...]
Sent: Tuesday, November 23, 2004 4:17 PM
(will not be in history)<br>
<a onclick="location.replace('c.html')" style="color: #009; cursor: hand; text-decoration: underline">Next</a>C.htmlC<br>Jade OhlhauserProduct ManagerRPM Softwarewww.rpmsoftware.com 403-265-6727
From: Lisa Crispin [mailto:lisa.crispin@...]
Sent: Tuesday, November 23, 2004 3:56 PM
Subject: [agile-usability] Back button
How do most people handle problems that could arise from an end user
clicking the back button? Is there a simple trick? Like not
putting the page on the history or something?
We have a new feature where the end user has to go through a series
of pages. Each page has a sequential list of items, and each item
has a remove link to remove it. If you remove an item and advance
to the next page, then use the back button and try to remove another
item, bad things happen.
I've worked other places that had solved this problem but I don't
know how they solved it (magic, as far as I'm concerned).
- --- In email@example.com, "aacockburn" <acockburn@a...>
> --- In firstname.lastname@example.org, "Jeff Patton"
> wrote:I think yesterday's weather confirms your thinking.
> > Things to try:
> > Capture more durable information in wiki pages. [use the
> > wiki set up by Adina Levin? thanks for doing that btw]
> I'm thinking that the eGroup is good for noisy discussion and back-
> and-forth, and wiki is good for archiving.