touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #98180
[Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Milestone: None => ww40-2015
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Bill Filler (bfiller)
** Changed in: canonical-devices-system-image
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1485222
Title:
Using ContentStore disables silently any StateSaver capability
Status in Canonical System Image:
New
Status in content-hub package in Ubuntu:
In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
Invalid
Bug description:
1. Create the default template project
2. Add on the page (with an id):
TextField {
id: foo
StateSaver.properties: "text"
}
3. run the app, type something in the field, xkill it, restart
-> the TextField content is restored by the StateSaver.
4. import Ubuntu.Content 1.1
-> StateSaver still works
5. add anywhere on the page:
ContentStore {
id: appContentStore
scope: ContentScope.App
}
-> The state is not restored anymore (note that it may be the first time, restoring when there was no ContentStore at kill time), then it constantly fails to restore.
There is no warning or anything that reported an issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1485222/+subscriptions
References