Search by property

Jump to: navigation, search

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.

Search by property

A list of all pages that have property "Feature open issues and risks" with value " * No module owner for distribution.js currently ". Since there have been only a few results, also nearby values are displayed.

Showing below up to 26 results starting with #1.

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

    

List of results

  • Improved Mac installer  + ( * Needs a developer to pick up the existing patch and make it work. ==== Risks ==== Mostly testing on all the hardware and OS variations, making sure the download and unpack is smooth from Safari (and less important, Chrome). )
  • Platform/Features/Meter Element  + ( * No native style on GTK and Windows XP: the default style might be ugly... * Windows Vista/7 can have a native style but could be perceived as a dirty hack. * MacOS X has a native style. Patch being written. )
  • Firefox/Features/New Tab Page  + ( * Performance or memory degradation )
  • Features/Desktop/64bit Firefox Windows 7  + ( * Plug-in support will be a major issue h …
    * Plug-in support will be a major issue here. We do not want users to have a worse view of 64-bit builds than they do of 32-bit. * Accessibility support will be an issue here. Some of the ATs inject their own DLL into Firefox's address space. That would break if they inject a 32-bit DLL into a 64-bit process. * Not sure what to do if users have both 32-bit and 64-bit Firefox installed
    ve both 32-bit and 64-bit Firefox installed )
  • Features/Thunderbird/Test Pilot  + ( * Privacy policy updates * Initial test of the system * Add-on approved on AMO * Visibility of background on Mac )
  • Firefox/Features/keywordurl follows searchbar  + ( * Privacy: implication of sending data from Location Bar to search engines other than Google, about:rights changes )
  • Features/Services/Notifications  + ( * Product Decisions Needed ** who is firs …
    * Product Decisions Needed ** who is first real consumer? *** AITC has expressed interest, B2G has expressed interest ** B2g question: are they adopting it? is an addon feasible? ** Desktop client - is an addon really a good idea? ** Android client - is an addon a good idea? ** [strawman] Definition of Success (one was not set) *** Someone out side of mozilla consumes it by EOY **** bonus points for a major social web property (fb, twitter, etc) a year after release *** 1000 msg/day by EOY * Implementation Needs ** needs privacy review ** needs security review *** is pending for crypto, needs scheduling ** needs ops review *** petef is involved *** estimate: initial load ~100 msgs/day ** hardware for production has not been ordered? ** deployment timeline is in question * Process Needs ** needs a Product Marketing Manager and/or Business Development Owner
    g Manager and/or Business Development Owner )
  • Default Add-ons  + ( * Proposing a add-on by default also implies that the add-on will always be compatible. To prevent this, we'll not bundle the add-ons with Thunderbird distribution but rather point at them in a content tab, the 'Installation Tip of the Day'. )
  • Privacy/Features/HttpsGoogleSearch  + ( * Responsiveness: HTTPS connections have …
    * Responsiveness: HTTPS connections have a longer handshake time than HTTP connections. If we deploy Open Search right, we can cut a redirect out of the search submission process which will counteract any handshake-caused slowdown. * Availability: HTTPS is potentially not available to all locales for Google search.
    available to all locales for Google search. )
  • Platform/Features/Progress Element  + ( * Should we ship with a nice default UI (when non-native)? ([https://bugzilla.mozilla.org/show_bug.cgi?id=644361 bug 644361]) (''Mounir Lamouri'') )
  • Firefox/Features/Sync Setup Improvements  + ( * Should we wait until the desktop and mobile work is done before touching the m.com copy and videos? )
  • Privacy/Features/Shortened HTTP Referer header  + ( * Site breakage (tolerable? need to quantify this) * User confusion (make it hidden pref?) )
  • Features/Desktop/Expose prefs for tabs-on-demand  + ( * Talk to Paul about estimates & tracking * There are cases where you want all tabs to load in the background. We'd like to expose the preference to enable the old behavior for the people that prefer this. )
  • Firefox/Input/Standalone Feedback Button  + ( * The code in Test Pilot currently looks …
    * The code in Test Pilot currently looks at ''every'' loaded URL to see whether or not it's an Input website where data is to be filled in. This may be a performance issue, so we should test its impact and replace it with something more efficient if needed. * If the user has manually placed the Feedback button, should that preference override the channel setting? (I.e. the customization remains even if you switch channels?)
    ation remains even if you switch channels?) )
  • Platform/Features/Camera API - Phase 2 (getUserMedia)  + ( * The getUserMedia spec is still being de …
    * The getUserMedia spec is still being defined. We will prefix the first release. * Privacy UI/UX for this feature is a challenge since this involves camera and microphone data. Security will be difficult due to the wish for applications to be able to provide useful interfaces, in conflict with the need to guarantee users are safe with regards to access to their camera and microphones. This design is being discussed with the security team.
    is being discussed with the security team. )
  • Eliminate redundant title text  + ( * Too aggressive de-duplication * There might be sites using titles in ways we can't predict )
  • Services/Sync/EOL Sync Add On Phase 2  + ( * Users will stop using Sync because they think the service has been disabled. )
  • Platform/Features/WebRTC  + ( * VP8 is the only open, modern video code …
    * VP8 is the only open, modern video codec under consideration. There is heavy debate going on in the IETF working group about what video codec should be mandated by the spec. Some are arguing that H.264 should be selected because they prefer the patent licensing situation there (MPEG-LA) and more mature technology. Without a common video codec, the spec could fail to gain acceptance and adoption. * Overall system latency (delay) might be an issue; if it is architectural changes may be needed. Testing will need to be done. * Privacy UI/UX for this feature is a challenge since this involves camera and microphone data. Security will be difficult due to the wish for applications to be able to provide useful interfaces, in conflict with the need to guarantee users are safe with regards to access to their camera and microphones. This design is being discussed with the security team. * Good congestion control is essential for real-time video/audio communication. The algorithm for this is still being developed. We can’t make our first release until we have a good algorithm implemented in the Firefox code.
    algorithm implemented in the Firefox code. )
  • Services/AndroidSyncFP  + ( * Where do we store passwords? * What are …
    * Where do we store passwords? * What are the privacy etc. implications of using the system data stores? * Will the mobile team decide to switch data stores? * How do we do distribution? If it's linked to Fennec, how do we handle uninstallation, clearing data, etc.?
    handle uninstallation, clearing data, etc.? )
  • Fennec/Features/touch  + ( * [https://bugzilla.mozilla.org/show_bug.cgi?id=653009 bug 653009] - Make preventDefault for touch events compatible with WebKit/Opera )
  • DevTools/Features/CSSDoctor  + ( * can this work with multiple selected nodes? )
  • Features/Firefox/PlugincheckLinkInAOM  + ( * limited number of localized plugincheck pages may make it difficult for users to understand feature * increased traffic to plugincheck may affect performance; needs assessment * string changes require l10n work )
  • Features/Platform/CSP Sandbox  + ( * need iframe sandbox (bug 341604) to land )
  • Security/Features/XSS Filter  + ( *<span style="color: grey; font-size: …
    *[ON TRACK] Complete C++ implementation *[NEW] Test the feature in the Aurora channel to assess its compatibility with existing websites. *[NEW] Measure the average overhead of the filter? (Can we use telemetry to find this out?)
    re the average overhead of the filter? (Can we use telemetry to find this out?) )
  • Security/Features/Sandboxing of content processes  + ( *E10S is slow going, so only slow progress can be made *Threat model needed )
  • Services/Sync/Sync Setup Improvements Desktop  + ( *Should we wait until the desktop and mobile work is done before touching the m.com copy and videos? )
Retrieved from "https://wiki.mozilla.org/Special:SearchByProperty/:Feature-20open-20issues-20and-20risks/*-20No-20module-20owner-20for-20distribution.js-20currently"