Ticket #6982 (closed enhancement: wontfix)

Opened 5 years ago

Last modified 5 years ago

Location in a document is not remembered

Reported by: ffm Owned by: morgs
Priority: high Milestone: Future Release
Component: read-activity Version:
Keywords: usability Cc:
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

(This is analogous to ticket 6981 for the Browse activity)

When a activity is resumed, Browse should resume at the same area the user was at when the activity was closed.

Use Case:

Matt reads free textbooks via the internet (or his school server). Some of these documents are very long (many printed pages) and it is difficult for him to find where he left off. Fortunately, Read resumes his prior activity exactly as he left it.

Change History

Changed 5 years ago by gregorio

  • milestone deleted

Milestone Never Assigned deleted

Changed 5 years ago by marco

  • next_action set to never set
  • milestone set to Future Release

Changed 5 years ago by morgs

  • owner changed from rwh to morgs

Read will save and resume the current page as soon as I've fixed the current datastore issues I'm having.

Changed 5 years ago by morgs

Hmm, now I remember the report that the metadata for this doesn't survive rebooting...

Changed 5 years ago by morgs

  • status changed from new to closed
  • resolution set to wontfix

The actual problem here is #4662 - the datastore doesn't preserve custom metadata across reboots. I'm closing this as I can't do anything about that in Read :(

Note: See TracTickets for help on using tickets.