Property:Feature requirements

From MozillaWiki
Jump to: navigation, search

This is a property of type Text.

Pages using the property "Feature requirements"

Showing 25 pages using this property.

View (previous 25 | next 25) (20 | 50 | 100 | 250 | 500)

ARMv6 support - phase 1 +lower minimum system requirements to 600 MHz, 256 MB RAM, 240x240 resolution  +
Add appTab via distribution.js +`  +
Add-on SDK in Firefox + * Add-on SDK loader and API libraries are shipped inside Firefox, removing the necessity of packaging them inside each add-on. * SDK development continues on Github. * SDK continues to be developed and reviewed by the SDK team.   +
Additional distribution points +1. Registration costs 2. setting up automatic updating for these distribution points. 3. to be filled in  +
Addon Console +The Add-on Console will allow add-on authors to view logged objects and messages in a console GUI on par with, or identical to, the console we provide to web content. The console will allow for rich inspection of logged objects, as opposed to the current Firefox error console's simple string output.  +
AddonSDKCryptoAPI +`  +
AndroidPasswordStorage +`  +
Anti-minimalistic redundant app button and home tab +`  +
App Vertical Tuts +Create an entry point for developers seeking to build web apps that quickly gets them into the vertical-specific app creation track they are looking for.  +
App Walkthrough +`  +
Ark +`  +
Arrow Panel Redesign +`  +
Async Jetpack +`  +
Attachment Browser +Level of difficulty: hard. Skills required: JS, HTML  +
Auto hide scroll bars +`  +
Awesome Bar v2 +`  +
B2G App Security Model + *An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app *App store needs to be able to revoke an app *App store must be able to set the default permissions for an app *A user needs to be able to make a trust decision at install time, so they also need to be able to verify the authenticity, integrity and privileges of an app *User has control of the permissions of the app throughout its lifecycle, overriding those set by the app store if desired *Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment *Permissions need to be expressed to the user in a way that they can realistically be expected to comprehend (perhaps with options for power-users) *Permissions requested / set need to be enforced. *Apps should not be vulnerable to common web vulnerabilities when granted significant privileges *Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties   +
Big File Providers +Level of difficulty: medium to hard, depending on the provider API and how well it maps to our provider interface Skills required: JS  +
Browser translation +`  +
CC perf improvements +`  +
CSS3 3D Transforms +`  +
Chrome Style Editing +`  +
Click-to-play part II +`  +
CloudServices/Universal Account Page + *Browser agnostic   +
Complete Send In Background + * Save email locally * Send email in the background without interrupting user * Attempt to re-send email without user interaction if the send fails * Gracefully handle persistent failures   +