Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

List of results

• Fennec/Features/readability  + ( * [https://bugzilla.mozilla.org/show_bug. …
  * [https://bugzilla.mozilla.org/show_bug.cgi?id=578179 bug 578179] - Option to wrap text to screen width rather than container width * [https://bugzilla.mozilla.org/show_bug.cgi?id=611555 bug 611555] - should reflow on zoom [see dependencies for related bugs] * [https://bugzilla.mozilla.org/show_bug.cgi?id=627842 bug 627842] - Allow minimum font size based on size of frame * [https://bugzilla.mozilla.org/show_bug.cgi?id=598736 bug 598736] - Use higher-quality image scaling. (Affects readability of text in IMG elements.)
  fects readability of text in IMG elements.) )
• Services/Sync/Push to device  + ( * [https://bugzilla.mozilla.org/show_bug. …
  * [https://bugzilla.mozilla.org/show_bug.cgi?id=507471 bug 507471] - Send tab to device * [https://bugzilla.mozilla.org/show_bug.cgi?id=677372 bug 677372] - Send tab to device: UX Design * [https://bugzilla.mozilla.org/show_bug.cgi?id=676375 bug 676375] - Send tab to device: Core API * [https://bugzilla.mozilla.org/show_bug.cgi?id=686704 bug 686704] - Send tab to device: support tab state
  04] - Send tab to device: support tab state )
• Fennec/Features/Gestures  + ( * [https://bugzilla.mozilla.org/show_bug. …
  * [https://bugzilla.mozilla.org/show_bug.cgi?id=653282 bug 653282] - Swipes should navigate the awesomescreen. * There are some interactions and dependencies between [[Fennec/Features/touch|touch events]] and gestures. ** When we expose multi-touch events to web content, web pages that consume the touch events may prevent gestures from invoking their default UI actions. ** The implementation of gestures might depend on exposing multi-touch events to Fennec's chrome JavaScript.
  touch events to Fennec's chrome JavaScript. )
• Privacy/Features/Handshake checkpoint API  + ( * [https://bugzilla.mozilla.org/show_bug.cgi?id=644640 bug 644640]: Implement extension point for extensions to influence trust decisions in PSM )
• Features/Mobile/webapps  + ( * [https://bugzilla.mozilla.org/show_bug. …
  * [https://bugzilla.mozilla.org/show_bug.cgi?id=583750 bug 583750] - Tracking bug for web app support in Fennec * [https://bugzilla.mozilla.org/show_bug.cgi?id=584767 bug 584767] (FIXED in Fx8) - Basic web-app front-end * [https://bugzilla.mozilla.org/show_bug.cgi?id=663571 bug 663571] (FIXED in Fx8) - Basic web-app back-end * [https://bugzilla.mozilla.org/show_bug.cgi?id=609043 bug 609043] (ASSIGNED) - Add support for Mozilla Labs' new Open Web Apps manifest format and API
  support for Mozilla Labs' new Open Web Apps manifest format and API )
• Simple module loader  + ( * https://bugzilla.mozilla.org/show_bug.cgi?id=638742 * https://bugzilla.mozilla.org/show_bug.cgi?id=672443 )
• Platform/Features/MPAPI  + ( *The user's device must have the codec needed for playback already installed, or else this feature will appear not to work. )
• Support/Kitsune/SUMO API Feature page  + (- For internal sites we would require owners of the site to apply this new method.)
• Services/Sync/Features/Addon Sync  + (; Sync GUID added to XPI Provider : Sync requires non-deterministic IDs to be affiliated with synchronized records. XPI add-ons currently don't have a suitable ID so once will need to be created.)
• Security/Features/CA pinning functionality  + (<strike>HSTS.</strike> This feature should not be tied to HSTS, but the two technologies should work together.)
• Services/Sync/Sync Setup Improvements Mobile  + (<table class="fullwidth-table sortable" …

  Dependency	Owner	Status
  Provide updated setup flow to Web Dev	Jen	Due date TBD
  [http://www.mozilla.com/en-US/mobile/sync/ Sync Web Page] Copy Updates	PMM (Jaclyn?)	Due date TBD
  Updated Sync Mobile Setup Video on [http://www.mozilla.com/en-US/mobile/sync/ Sync Web Page]	PMM?	Due date TBD
  Provide updated set up flow to Support	Jen	Due date TBD
  Update support documentation	Ibai Garcia	Due date TBD
  Provide l10n team en-us copy	Jen?	Due date TBD
  Update l10n Sync pages	Axel?	Due date TBD
  Update blogs of changes	Jen	Due date TBD

  Garcia</td> <td>Due date TBD</td> </tr> <tr> <td>Provide l10n team en-us copy</td> <td>Jen?</td> <td>Due date TBD</td> </tr> <tr> <td>Update l10n Sync pages</td> <td>Axel?</td> <td>Due date TBD</td> </tr> <tr> <td>Update blogs of changes</td> <td>Jen</td> <td>Due date TBD</td> </tr> </table>)
• Services/Sync/Sync Setup Improvements Desktop  + (<table class="fullwidth-table sortable" …

  Dependency	Owner	Status
  Provide updated set up flow to Support	Jen	Due date TBD
  Update support documentation	Ibai Garcia	Due date TBD
  Provide l10n team en-us copy	Jen?	Due date TBD
  Update l10n Sync pages	Axel?	Due date TBD
  Update blogs of changes	Jen	Due date TBD

  ?</td> <td>Due date TBD</td> </tr> <tr> <td>Update l10n Sync pages</td> <td>Axel?</td> <td>Due date TBD</td> </tr> <tr> <td>Update blogs of changes</td> <td>Jen</td> <td>Due date TBD</td> </tr> </table>)
• Features/Jetpack/Jetpack-Mobile-Add-on-Tab  + (Add-on Tab API (currently being worked on at time of this writing))
• Firefox/Features/Expose Add-on Performance  + (Add-on testing capabilities, manual or automated. An AMO API for "warned add-ons" and for "doubly warned add-ons" AMO and Firefox code to access this API, get the lists, and display UI based on the lists.)
• Platform/Features/Camera API - Phase 2 (getUserMedia)  + (Android and Desktop both need: *UX/UI design work which is being determined now Desktop support also needs *part of WebRTC to land)
• Platform/Features/SPDY  + (Because all of SPDY runs on SSL, having SSL False Start done would be helpful: https://bugzilla.mozilla.org/show_bug.cgi?id=658222 Also requires NPN support: https://bugzilla.mozilla.org/show_bug.cgi?id=547312)
• Features/Desktop/Enhanced Customization APIs  + (Before release, we need to make sure that we communicate this feature to all developers, specially those who don't list their add-ons on AMO. We need to have a policy of not accepting any bypassing of these new APIs.)
• Services/Sync/AndroidSyncPushToDevice  + (Completion of [[Services/Sync/Push_to_device|P2D work on desktop]].)
• SecurityUI-UX  + (Current Permissions Available to Users and …
  Current Permissions Available to Users and their locations: * History Settings (Preferences->Privacy) * Always Private Browsing (Preferences->Privacy->Use custom settings for history) * Disable Third Party Cookies (Preferences->Privacy->Use custom settings for history) * Disable Cookies (Preferences->Privacy->Use custom settings for history) * Awesome bar settngs (Preferences->Privacy->Location Bar) * View Cookies / Remove Cookies (Preferences->Privacy->Use custom settings for history->Show Cookies) * Clear private data (Preferences->Privacy->Use custom settings for history->Clear history when Firefox closes->Settings) * Do-not-track (Preferences->Privacy) * Per Site permission information (about:permissions, doesn't provide info for all sites, just top sites) * Enable/Disable Javascript, Images, pop-up windows (Preferences->Content) * Enable/Disable Javascript to move firefox windows (Preferences->Content->Enable Javascript-Advanced) * Firefox Session Liftime (Preferences->General->When Firefox starts) * Add-on install warnings (Preferences->Security) * Safe browsing (block sites) (Preferences->Security) * Password Management (Preferences->Security) * Submit crash reports / performance data to Mozilla (Preferences->Advanced->General) * Warn on redirects/reloads (Preferences->Advanced->General) * Warn when website wants Offline Storage (Preferences->Advanced->Network) * Updates (Preferences->Advanced->Update) * SSL and certificate preferences (Preferences->Advanced->Encryption) * Share Location Data with sites (about:config geo.enabled preference) * Remove per site permission for Location Data/Cookies/Offline Storage, etc (When on the website, Tools->Page Info->Permissions) * Per site certificate info (When on the website, Tools->Page Info->Security)
  ine Storage, etc (When on the website, Tools->Page Info->Permissions) * Per site certificate info (When on the website, Tools->Page Info->Security))
• SMS support  + (Depending on the implementation, the chat team may need to get involved in some manner.)
• Firefox/Features/Media Controls Refresh  + (Full-screen mode will require [https://bugzilla.mozilla.org/show_bug.cgi?id=545812 bug 545812], security review will happen there.)
• Security/Features/Application Reputation  + (Google maintains an extension to Safe Browsing that tracks binary file reputation. We can harness their API to provide application reputation whitelisting for Firefox users.)
• B2G App Security Model  + (Heavily dependent on the Open Web Apps security model and ecosystem (including Marketplace), and on BrowserID as well.)
• In-content preferences  + (In-content UI Visual Unification: https://wiki.mozilla.org/Features/Firefox/In-content_UI_Visual_Unification)
• Testing/Client-side XPI Construction  + (JavaScript variant of the CFX tool.)

• App Vertical Tuts  + (MDN, WebDev, UX, Engagement)

• Investigate Designing a Home Tab  + (Maybe the inclusion of app tabs in Thunderbird, but this can be bypassed. The Launchers are dependent on their related features.)
• Services/Sync/Features/MigrateToDigestAuth  + (Must discuss replacement authentication protocol with security people (bsmith?))
• Security/Features/TLS Telemetry  + (N/A)
• Privacy/Features/Pref to limit number of fonts loaded per tab  + (None)
• Security/Features/SSL Error Reporting  + (Not necessarily a dependency, but need to …
  Not necessarily a dependency, but need to keep in mind: * There's an [http://tools.ietf.org/html/draft-ietf-websec-key-pinning-04#section-3 IETF key-pinning draft] in the works that can report pinning errors. See [https://bugzilla.mozilla.org/show_bug.cgi?id=846501#c5 bug 846501#c5]. If we use a format for the general SSL error reporting that is compatible with the IETF standard for reporting key pinning errors, we may be able to avoid writing that code twice. * [https://wiki.mozilla.org/Security/Features/CA_pinning_functionality Certificate Pinning] will need this capability.
  ficate Pinning] will need this capability.)
• Security/Features/Sandboxing of content processes  + (Older project description: https://wiki.mozilla.org/Security/ProcessIsolation<BR> Early draft of threat model: https://wiki.mozilla.org/Security/ProcessIsolation/ThreatModel)
• Features/Security/Low rights Firefox  + (Other references * http://www.chromium.org …
  Other references * http://www.chromium.org/developers/design-documents/sandbox * http://dev.chromium.org/developers/design-documents/sandbox/osx-sandboxing-design * https://blogs.adobe.com/asset/2010/10/inside-adobe-reader-protected-mode-part-1-design.html * https://blogs.adobe.com/asset/2010/10/inside-adobe-reader-protected-mode-%E2%80%93-part-2-%E2%80%93-the-sandbox-process.html * http://msdn.microsoft.com/en-us/library/bb250462%28v=vs.85%29.aspx * http://msdn.microsoft.com/en-us/library/bb625964.aspx
  .microsoft.com/en-us/library/bb625964.aspx)
• Web Apps integration  + (Platform and Apps work: * -webapp mode ([h …
  Platform and Apps work: * -webapp mode ([https://bugzilla.mozilla.org/show_bug.cgi?id=725408 bug 725408]) * navigator.mozApps ([https://bugzilla.mozilla.org/show_bug.cgi?id=697383 bug 697383], LANDED) * Add-on implementation: https://github.com/mozilla/openwebapps/tree/develop/addons/jetpack/lib UX * Mac & Win: The user is prompted if they are sure they want to install and perhaps some messaging as to where the app will be installed * Mac & Win: Post-install message tells user where the app was installed or the OS can show the user where the app was installed
  e OS can show the user where the app was installed)
• Features/Platform/CSP Sandbox  + (Requires the sandboxing infrastructure from https://wiki.mozilla.org/Features/Platform/Iframe_Sandbox)
• Fennec/Features/TabletUI  + (See the [https://bugzilla.mozilla.org/showdependencytree.cgi?id=655762 complete dependency tree].)
• URL Preview within Thunderbird  + (Should interract with the App Tabs gSoC project http://www.google-melange.com/gsoc/project/google/gsoc2012/trungnn/8001)
• Features/Platform/Graphite font shaping  + (The Graphite2 library: http://projects.palaso.org/projects/graphitedev)
• Features/Jetpack/Browser-e10s-Support  + (The feature depends on platform support (specifically the Electrolysis work) for loading and executing the correct elements into the correct processes.)
• Features/Jetpack/Out-of-Process Addons  + (The feature depends on platform support for loading and executing add-ons in separate processes. It may also depend on decisions we make about providing a more web-page-like environment to addons.)
• Features/Jetpack/Add-on SDK Localization API and Service  + (The feature depends on work to be done in the SDK, AMO, and a localization service with which AMO interacts to solicit and retrieve localizations.)
• Features/Jetpack/SDK Support for Firefox for Mobile Addons  + (The feature may depend on landing support …
  The feature may depend on landing support for specific interface elements in the FFM interface. While there are elements to having support for out-of-process addons that will be necessary in the long run. We have determined that having e10s support is not a blocker to getting minimal support for mobile addons working.
  minimal support for mobile addons working.)
• Features/Add-ons/Add-ons Default to Compatible  + (The operational side of this feature, how to detect and handle incompatibility cases, is detailed on the [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible/Detection_and_Mitigation Detection and Mitigation] page.)
• Features/Desktop/BYOB-for-Firefox9  + (This Feature depend on the following bugs: …
  This Feature depend on the following bugs: * [https://bugzilla.mozilla.org/show_bug.cgi?id=696705 bug 696705] modifying distribution.ini results sometimes in extra quotations in prefs * [https://bugzilla.mozilla.org/show_bug.cgi?id=666909 bug 666909] update video for Firefox * [https://bugzilla.mozilla.org/show_bug.cgi?id=668180 bug 668180] update partner-repacks * [https://bugzilla.mozilla.org/show_bug.cgi?id=671511 bug 671511] update search engines on byob * [https://bugzilla.mozilla.org/show_bug.cgi?id=668181 bug 668181] update addon installer * [https://bugzilla.mozilla.org/show_bug.cgi?id=593230 bug 593230] update byob homepage * [https://bugzilla.mozilla.org/show_bug.cgi?id=592707 bug 592707] need BYOB FAQ
  ug.cgi?id=592707 bug 592707] need BYOB FAQ)
• Features/Add Sync to Home Tab  + (This bug is a blocker for the [[Firefox/Features/Sync_Setup_Improvements| Sync Setup Improvements]])
• Privacy/Features/Sync Compromise Alerts  + (This can be implemented by itself, but the alerts could be generated inside the clients and pushed to the other devices using [[Services/Sync/Push_to_device]].)
• Privacy/Features/HSTS Preload List  + (This depends on HSTS, which landed and shipped with Firefox 4.)
• Simplified Sync  + (This feature depends of [https://wiki.mozilla.org/Identity/Architecture/SignIntoBrowser Sign In to the Browser] as it will use that method to access the data.)
• Firefox Social Integration  + (This feature depends on: # The Social API …
  This feature depends on: # The Social API back-end implementation # UR and UX work to test and design the experience for discovery and enabling social features, each of the 4 social touch points, disabling the social feature, and switching between social providers. # Labs and Firefox engineers to implement the front-end of the Social API # Social providers to offer up an Open Web Application Manifest - which contains the name, icon, and service data needed for the browser to communicate with the web property.
  wser to communicate with the web property.)
• Thunderbird Metro  + (This feature may require some or all of the Gecko, Necko, scripting engines, etc. to be somewhat modified. These should be reusable from Firefox metro.)
• DevTools/Features/StyleInspector  + (This is an element-centric tool. That means that while it's possible to select an element with a command and then open this tool, practically speaking we need to have the Highlighter working first.)