canmove, Confirmed users
901
edits
WebAPI/PlannedWork: Difference between revisions
→Untriaged
No edit summary |
|||
| Line 103: | Line 103: | ||
** MessagePort and MessageChannel ({{bug|741618}}, {{bug|911972}}) | ** MessagePort and MessageChannel ({{bug|741618}}, {{bug|911972}}) | ||
** finish Blob porting ({{bug|1047483}}) | ** finish Blob porting ({{bug|1047483}}) | ||
===The following came from a discussion with some Gecko and Gaia developers in May 2014=== | |||
* DataStore in workers (rewrite in C++: {{bug|990554}}) | * DataStore in workers (rewrite in C++: {{bug|990554}}) | ||
* child process support for FileHandle | |||
** FileSystem proposal is a potential future standard that can be used here | |||
** ex. stream into IDB, hand off fully-formed blob from IDB to download manager | |||
*** baku says magical Blob feature Jonas wants will make this easy | |||
* apps knowing how much memory they're using (probably a debug-only feature) | |||
* audiochannelmanager (maybe?) feature to allow video/audio recording to be muted when a phone call or alarm happens | |||
** setVisible is used as a workaround here right now | |||
** make oom priority controllable by system app (on mozapp mozbrowsers) | |||
* notification of interruption by events like phone call or pressing home button or alarm | |||
** needs UX consideration around visibility of notifications, etc. | |||
** having an API for an app to save its state can help here (notably in OOM situations) or perhaps some state on the visibility change event indicating why that change happened | |||
* Passing CSS transform dimensions as typed arrays or making the current JIT faster in parsing values out of strings | |||
* Calendar API for writing a privileged calendar app | |||
** mozCalendar? | |||
** some primitives like storage (can DataStore work with its onchange notifications?) | |||
** sync | |||
*** what features do we need for some sort of local store to easily be able to sync? | |||
** seems like writing libraries that we can provide to apps is the best solution here | |||
* make DataStore available to privileged apps | |||
* media player API | |||
** e.g. rdio on the lock screen | |||
** Google has put forward an idea here about sending media key events | |||
** alternative is a widget | |||
*** but then each player (e.g. rdio *and* songza *and* spotify) has to write their own custom widget | |||
** communication: IAC (Inter-App Communication API)? | |||
* A standardized share Web Activity | |||
** see https://etherpad.mozilla.org/sharing | |||
* Figuring out what we should do for apps that want to run when the device is locked (context: activities opened from lockscreen widgets, etc.) | |||
** deal with exposing permissions when running in locked more (we can't prompt because prompts will go under the lockscreen.) | |||
* attention screen (not sure what was meant here) | |||
* localization | |||
** We should look into what fast path localization support we could add to our parser/dom code. This will be a significant project given how long we've fought with figuring out the right approach here. | |||