canmove, Confirmed users
409
edits
Services/Sync/Push to device: Difference between revisions
latest status
(add tab context as minimum requirement) |
(latest status) |
||
| Line 3: | Line 3: | ||
|Feature stage=Definition | |Feature stage=Definition | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature version=Firefox | |Feature version=Firefox 10 | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note= | |Feature status note=Support for tab/session state in works (bug 686704). Waiting on final UX design. | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Line 37: | Line 37: | ||
* {{bug|677372}} - Send tab to device: UX Design | * {{bug|677372}} - Send tab to device: UX Design | ||
* {{bug|676375}} - Send tab to device: Core API | * {{bug|676375}} - Send tab to device: Core API | ||
* {{bug|686704}} - Send tab to device: support tab state | |||
|Feature requirements=* When a tab is pushed to a remote device, the full context/state of that tab is preserved. e.g. filled forms, etc. | |Feature requirements=* When a tab is pushed to a remote device, the full context/state of that tab is preserved. e.g. filled forms, etc. | ||
|Feature non-goals=* Need better clarity on use cases before filling this out | |Feature non-goals=* Need better clarity on use cases before filling this out | ||
| Line 91: | Line 92: | ||
|Feature engineering status=Blocked on UX imlpementation | |Feature engineering status=Blocked on UX imlpementation | ||
}} | }} | ||
*Need ops review | |||
** will be introducing new collection on server for tab state | |||
** do we define collection on server? | |||
** how much storage do we expect? | |||