Opened 17 years ago

Closed 16 years ago

#52 closed defect (wontfix)

web operations' result pages should be capable of reload

Reported by: price Owned by: ecprice
Priority: minor Milestone: Demo-able
Component: web Version:
Keywords: Cc:

Description

Currently

  • the create operation on /list
  • the power on/off operations on /info

lead to pages that look like the pages the user started from, but are obtained by POST and from a different, otherwise useless URI; in particular, reload doesn't work.

It's good that these operations are POST requests. Probably the response to such a request should be a redirect to the appropriate /list or /info URI, not a 200 with the latter page's contents.

Change History (3)

comment:1 Changed 17 years ago by price

  • Milestone set to Demo-able

comment:2 Changed 17 years ago by price

Done in r407 for operations with back='info'.

The create operation on /list gives a message that has some usefulness, since the command's effect is in among a potentially long list of VMs. Maybe we want a way to keep that message while going back to the /list URI.

Actually, the best thing is probably to highlight that row in the VM list. That doesn't even have to be based on having created the VM "in this request"; it can be based on having created it "recently", time-wise, like Trac seems to do with its ticket list.

comment:3 Changed 16 years ago by broder

  • Resolution set to wontfix
  • Status changed from new to closed

Moved to LP blueprint more-ajax (​https://blueprints.launchpad.net/invirt/+spec/more-ajax)

Note: See TracTickets for help on using tickets.