User:Timdream/Blocking Features

Gecko features blocking Gaia Blockers

The goal of this page is to collect wanted Gecko features that could fix blockers that cannot be fixed in Gaia apps along. We will try to use this list as a source when prioritize FxOS Gecko works (no, there are no promises, unfortunately -- but someone has to collect the list first).

IMPORTANT: To prevent this become a platform feature wish list, please only list a bug if it, or any bug that has any depend on it, has been nominated as a blocker.

Activity OOM timing: bug 892371

• Status: NOT STARTED
• What is being blocked:
• What this bug will solve:

System message target: bug 931339

• Status: NOT STARTED
• What is being blocked:
• What this bug will solve:

Visibility API update: bug 1034001

• Status: ?
• What this bug will solve:

Orientation API update: bug 1043102, aka Skate Jumper bug

• Status: NOT STARTED
• What is being blocked: Incorrect orientation of lock screen/system UI with an easy-to-produce STR, consistently being nominated as blockers by partners in multiple previous versions.
• What this bug will solve: By allowing System app to take part of deciding whether or not to allow a given app to lock the orientation, we will be able to block orientation lock happens right at the time app goes to background.

Audio Channel API update: bug 1089539

• Status: on going, see <<insert update page here>>
• What is being blocked:
• What this bug will solve:

Nested oop apps: bug 1020135

• Status: ?
• What this bug solves: Gaia apps like Settings app hosts many of the settings for other apps. It would be more technically sound if the Settings app could embed the said app instead, for the sake of code clarity and security model etc (bug ?). We would also need this to stop using activity to launch & go back from the keyboard settings panel (bug ?). It would unlock the 3rd-party app setting embedding as well (bug 1020063).

mozApps.getAll needs a filter based on "role" and "type": bug 1094562

• Status: NOT STARTED
• What is being blocked: Performance issues involving mozApp.getAll() calls during start-up.
• What this will solve: In settings app there are cases in which we have to find specific role or type of apps like homescreens, themes, or addons. Currently the only way would be getting all apps and check their properties one by one, which leads to performance issues. Providing a filter solves the performance issue during start-up.

Date & time format API: bug 1118214 bug 1122570

• Status: NOT STARTED (The mozAPI work is not going since the origin project(tako) request is canceled)
• What is being blocked: Apps displaying date and time now rely on a shim from gaia. The shim introduces additional loading time, potential racing, and settings migration issues.
• What this bug solves: It should provide robust API for gaia apps to query the current date/time format. Moreover, it can also provide functions that generate localized date and time strings based on the current language setting.

deprecate mozChromeEvents bug 928433

• Status: ?
• What is being blocked:
• What this bug solves: (is this bug really had blocked any blockers?)

Migrate mozSettings values in Gecko: bug 1112092

• Status: NOT STARTED
• What is being blocked: Performance issues that could be blockers in the next release.
• What this bug will solve: The DB_VERSION of mozSettings is hidden inside Gecko, therefore to upgrade a settings in Gaia we would have to read the setting every time the phone boots or the app start ups. This contributes to boot time a lot and we are very close being asked to block a release for this (see the depending bugs of that bug). We would either have to patch Gecko to put all the migration there or we would have to expose something non-trivial to Gaia instead.

Unlock Console API for Gaia: bug 1066581

• Status: NOT STARTED
• What is being blocked: Lot's of previous MTBF bugs.
• What this bug will solve: From time to time, we are asked to debug MTBF issues with log. Currently, we have always have to work submit a patch with lines-to-print and ask QA engineers to re-run, instead of having these logging check into the tree. According to measurement in the bug, adding console.log() will slow down main thread significantly. There has been time where racing bugs simply unreproducible when the log was added as well. The fix proposed here is to make logging faster, at least not noticeable until it's turned on from Gecko. Our logger in apps, currently, unfortunately, have to wire their own logging to a app script with it's own, special switch.