Confirmed users
681
edits
User:Timdream/Blocking Features: Difference between revisions
Jump to navigation
Jump to search
User:Timdream/Blocking Features (view source)
Revision as of 05:20, 29 January 2015
, 29 January 2015update
(up) |
(update) |
||
| Line 49: | Line 49: | ||
* '''Status:''' '''<font color=red>NOT STARTED</font>''' (The mozAPI work is not going since the origin project(tako) request is canceled) | * '''Status:''' '''<font color=red>NOT STARTED</font>''' (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 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. | * '''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. The alternative approach is improving mozSettings performance {{bug|1122570}} therefore all mozSettings call are improved. | ||
== deprecate mozChromeEvents {{bug|928433}} == | == deprecate mozChromeEvents {{bug|928433}} == | ||