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 users and use cases" with value "People who care about performance. Makes the browser not lock up.". 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

  • Platform/Features/IonMonkey  + (Goals: * Provide a backend that can match
    Goals: * Provide a backend that can match or beat the Trace JIT or Crankshaft in speed. Sub-goals: ** Fine-grained specialization and de-specialization. ** Integration with type inference. * Clean, textbook IR so optimization passes can be separated and pipelined with well-known algorithms. * Document and comment well so the implementation and its side effects can be easily understood. * Recompilation, debugging, bailouts are all related - and should be solved up-front. * First SpiderMonkey JIT that starts off with peer reviews! * (Unknown feasibility) Act as a baseline compiler to replace JM2. * Manage memory much better, in part to avoid range problems on x64. Avoiding these: * Aggressive stores. We should move state syncing to bailout points.
    ould move state syncing to bailout points.)
  • Features/Platform/Graphite font shaping  + (Graphite support is targeted primarily at
    Graphite support is targeted primarily at minority-language user communities in South-East Asia and other areas where complex writing systems are used, and industry standards are still a long way from providing adequate support. Examples include minority groups in Myanmar (Burma) using variants of Burmese script[3] and communities in Thailand using the Lanna script.[4] Graphite is also likely to be valuable in implementing scripts such as SignWriting[5], used by some sign-language communities. In addition, Graphite can be used by font designers to provide improved support for complex behaviors such as calligraphic styles and placement of multiple diacritics even in "simple" scripts. [3] http://scriptsource.org/scr/Mymr
    [4] http://scriptsource.org/scr/Lana
    [5] http://en.wikipedia.org/wiki/SignWriting
    lt;br> [5] http://en.wikipedia.org/wiki/SignWriting)
  • Features/Platform/NavigationTimingAPI  + (Implement W3C spec. Let web developers get detailed real-life timing information on their website so they know what they can do to speed it up.)
  • Platform/Features/AzureD2DCanvas  + (Improve the performance of the 2D canvas context on common benchmarks and demos when using Direct2D.)
  • Platform/Features/OpenGLLayersX11  + (Improve the performance of the scrolling and compositing of complex pages on X11 without regressing performance or stability on other pages.)
  • Labs/Deuxdrop  + (Intended for the smart phone and desktop user for almost real-time one-to-one and group messaging. Users connect with contacts they wish to communicate with and then can message those people directly or in group chats.)
  • Features/Jetpack/Jetpack-Chrome-mods  + (It is part of the initial work to identify what the users and use cases are here.)
  • More useful tabs  + (It will inform the user faster.)
  • DevTools/Features/Debugger  + (JavaScript developers)
  • Features/HTTP Digest header verification  + (Jim downloads LibreOffice but the file doe
    Jim downloads LibreOffice but the file doesn't seem to work. Jim contacts the LibreOffice support group and they suggest that Jim manually validates the hash. Jim uses Microsoft Windows, so they tell him to download a small program since nothing comes with the OS to do this. Jim installs the program, and after figuring out how to use it & select the file to hash, figures out that the download is corrupt. He contacts LibreOffice support & they tell him to re-download the file again, and manually check it again until the hash is correct. Jim has an unreliable internet connection, so it isn't until his third try that the download completes without errors. Janie downloads VLC and as a technical user, she recognizes the SHA-1 hash on the download page: http://get.videolan.org/vlc/2.0.6/macosx/vlc-2.0.6.dmg "If you have a problem, click here. SHA-1 checksum: 65742a2194185790925a4dcd6105ca27eb3e386a" As a seasoned Unix user, she knows she may open a terminal and type a command to manually verify that the download completed without errors. Luckily there are no errors, so she uses the file. Janie wishes her browser automatically took care of this for her, even though she knows how to do it. Behavior with this feature: User initiates a binary file download. A hash is supplied in a 'Digest' header. Once the download completes successfully, Firefox automatically uses the hash to validate the file. If there is an error during transfer, a retry option can be given. If the file is complete and without errors, it can be shown as a typical completed download.
    , it can be shown as a typical completed download.)
  • Features/Desktop/improve readability  + (Johnny wants to spend an hour or two readi
    Johnny wants to spend an hour or two reading articles from the New York Times. The current view is cluttered and not well optimized for long stretches of reading. Johnny would have a much better time if we dimmed or removed irrelevant content and styled the article content to be more readable.
    d the article content to be more readable.)
  • AddonSDKCryptoAPI  + (Labs will need to create prototype Addons
    Labs will need to create prototype Addons that handle generateKeypair(), sign() and verify() in order to support Identity in the browser. A addon author needs to allow users to easily sign or encrypt then verify or decrypt data that is submitted to a service or exchanged between users online.
    service or exchanged between users online.)
  • Notifications  + (Lots of use cases, but here are some examp
    Lots of use cases, but here are some examples of incoming messages from: Ping/Pulse/Bounce *real time chat *asynchronous (but important) direct messages through social networks Ambient *asynchronous email *asynchronous (and not important) messages through social networks *various random niche sites that need to notify you of events
    he sites that need to notify you of events)
  • Security/Features/Certs Disallow Weak Keys  + (Make the web safer. Kill weak keys.)
  • Firefox/Features/Replace old profiles  + (Marcos used Firefox up until version 3 whe
    Marcos used Firefox up until version 3 when he decided to switch to Chrome. He's been using Chrome for a couple of years now but heard that Firefox 4 was blazing fast and had some great new features. He downloads Firefox but when he launches it, it has his three year old Facebook and Bank of America passwords stored which don't work any more. It's also missing all his new favorite websites and what's even worse than that is the awful Ask toolbar that just showed up in Firefox one day back in 2008. He decides Firefox still sucks and goes back to Chrome. Julia was a Firefox 4 that decided to Give IE 9 a try and found she loved it. Since moving to IE 9, she's amassed about 1500 new favorites and a bunch of new logins. Hearing that Firefox 6 is the bomb, she downloads it. When starting Firefox for the first time, it asks her if she'd like to migrate her IE 9 settings and data. She says yes and Firefox does. She has no more reason to go back to IE 9 and so she makes Firefox 6 her new default.
    nd so she makes Firefox 6 her new default.)
  • Identity/Features/Web-based Verified Email Client  + (Mark gets a tip from a friend about SaladF
    Mark gets a tip from a friend about SaladFans.com, a place to review and share your favorite salad bars. Mark visits the site and is eager to contribute his own reviews as well as connecting with friends to find out which salad bars they like. Mark sees a "sign in" button on the SaladFans site, and when he clicks on it a Mozilla ID pop-up dialog comes up telling him that the site is asking for a verified email address to sign-in. Mark hasn't used Mozilla ID before, so he clicks the "register" button. Mark now types in his email address, and chooses a password for his account. After he's done, Mozilla ID tells him that a verification message has been sent to his email, and he needs to click on a link there before proceeding. Mark checks his email and clicks on the link in the message Mozilla ID sent him. The link opens up a new pop-up replacing the previous one, which welcomes him to Mozilla ID and asks him if it's OK to disclose the email address to SaladFans.com. Mark clicks OK, the dialog closes, SaladFans.com reloads, and Mark is now signed into SaladFans.com! Key Points: * Easy set-up from scratch * All HTML flow, works on a variety of browsers * Flow centered around verified email disclosure
    centered around verified email disclosure)
  • Security/Features/TLS 1.2  + (Modernize TLS in Gecko so that web sites can provide better encryption.)
  • In-content preferences  + (Modifying Firefox, using add-ons)
  • DevTools/Features/CodeEditor  + (Most web developers will benefit from this and anyone doing significant JavaScript work will benefit most.)
  • Security/Features/Revamp Security Hooks  + (Motivations - * Enable new hooks to better
    Motivations - * Enable new hooks to better handle redirects and response observing/filtering * Replace necko observer-service notifications with something more high-performance * Enable implementing CSP, local-network-CSRF-protection and https-everywhere to be implemented using standard necko hooks * Replace nsIContentPolicy with something e10s friendly * Replace nsIProtocolHandler with something e10s friendly * Remove ability/need for protocol handlers to implement custom nsIURIs and nsIChannels * Enable starting network requests directly from worker threads and other non-main-threads * Enable off-main-thread network requests to never hit the main thread unless JS-based addons which explicitly request it are installed * Make redirect handling simpler and more consistent * Get rid of nsIChannel.owner * Provide consistent observer hooks that work for all channel types, including file:, http:, chrome:, data: etc. This is useful for the devtools team. * Provide observer hooks with fewer edge cases, even when a request is loaded from cache.
    even when a request is loaded from cache.)
  • Feature Creep  + (Mozilla Developers: teams that are working
    Mozilla Developers: teams that are working on new features that involve changes to UX need an efficient way to access a broad spectrum of users for feedback. End Users: enthusiasts may be interested in accessing and providing feedback on upcoming Firefox features or experiments that are meant to improve the appearance or usefulness of Firefox, without the need to install nightly builds.
    ithout the need to install nightly builds.)
  • Features/Platform/Page Load and Crash Probes  + (Mozillians will benefit from metrics pulle
    Mozillians will benefit from metrics pulled from these probes, as we'll be able to better understand crash "pain". All users should transparently report the number of page loads and crashes on a regular basis. Users will obviously benefit from the probing of of these two metrics as we'll be able to better prioritize crash efforts.
    e able to better prioritize crash efforts.)
  • Privacy/Features/Shortened HTTP Referer header  + (Nice document from Dan Aurbach: https://bu
    Nice document from Dan Aurbach: https://bug822869.bugzilla.mozilla.org/attachment.cgi?id=694472 ; Leaking search terms : From [https://bugzilla.mozilla.org/show_bug.cgi?id=587523#c0 bug 587523#c0]: "An example of this can be seen by searching for 'no knead bread' with Google, and clicking on the 4th search result, which takes you to www.breadtopia.com/basic-no-knead-method/, a page which "helpfully" lets you know that it is aware of the search terms that brought you to the site." ; Outbound link anonymization : Many sites like gmail send outbound links through a common redirect to strip off any information that may be present in the URL. Supporting rel="noreferrer" reduces the need for extra HTTP traffic and redirects.
    need for extra HTTP traffic and redirects.)
  • Support/Kitsune/SUMO API Feature page  + (Other Mozilla Domains Product Page Article
    Other Mozilla Domains Product Page Article Snippets (similar example: http://www.mozilla.com/en-US/firefox/security/) - A new product is going to be launched and a site is created - SUMO content is created for the product. - Engagement wants to include some FAQs in the new site. - To ensure that the content is up to date the Title for the link and an snippet is pulled from the SUMO FAQs, calling for an specific article. - The content is then formatted with the CSS of the page. Article Content (example: http://www.mozilla.com/en-US/mobile/sync/) - In the same product page, engagement decides to explain how to configure the new feature. - They decide to include the steps in a template stored at SUMO. - Instead of hardcoding the steps, they include a call to the API to fetch an specific article that is always updated. - The content will be customized based on the user reading it (i.e. user agent) and the page's CSS. Top Questions - The team working on BrowserID wants to include a page for Users explaining what it is. - SUMO has content explaining how to use it and how to troubleshoot it. - BrowserID team decides to include a widget with the most popular topics. - They embed a query to the SUMO database that presents a configurable (amount of items, tags) list of the top articles relevant to the product. - The list can be formatted with the CSS to match the look and feel of the site. Auto Customization - The AMO team has created a dashboard where you can see all the add ons that you have downloaded. - They want to include a list of relevant SUMO articles. - To fetch the list they use the SUMO API and they include the codenames of the add-ons as part of the query. - Based on this additional parameters (signals), the API will provide the most relevant articles based on a previous manual configuration. Contributors with their Own site Contributor Widget - David is a contributor - He wants to show on his site a set of articles where he has contributed. - He uses the code snippets that SUMO provides and paste it on his site. - The widget allows David to configure: - View by Most Recent or More Visited. - Filter by keyword - The widget also shows the Karma level of this user. Search box redirecting to SUMO - David is a big fan of providing Firefox support. - Because of it, he wants to make sure that anyone visiting his site can find answers to their Firefox questions. - The search box in his site allows users to search in SUMO the same way as if they were at support.mozilla.com - For David, including this search box is a simple as including a code snippet in his site. - The search results would be displayed in SUMO. Search box returning article list - James is a big fan of providing Firefox support and he is an avid developer. - He wants to help users but he also wants to keep the traffic on his site. - The search box in his site allows users to search in SUMO the same way as if they were at support.mozilla.com - For James, including this search box is a simple as including a code snippet in his site. - The search query will return a list of article links matching the search criteria. - James can customize a landing page so the results are displaying with the same look and feel as his site. Local Mozilla communities Mozilla Hispano wants to render the spanish content in SUMO in their own site, but instead of replicating SUMO or sending traffic to SUMO they want to present it in combination with their own content.
    it in combination with their own content.)
  • SecurityUI-UX  + (Our UI falls into two main areas: *inline
    Our UI falls into two main areas: *inline: user is notified of some security or privacy relevant event, and (may) want/have to take action
    *task driven: the user wants to perform some specific task such as changing a setting or understanding their situation Some areas to investigate: *context information about the current site ("am I on store.com") *is the current site "secure" ("should I enter my password/credit card") *historical information ("what information has this site stored on my computer") *incident driven ("I read about this security issue and I want to disable a cert/feature/etc") *inline warnings (this is a phishing/malware site, this site wants to install an , mixed content, etc.) Note the above parenthesized examples are not intended to be exhaustive (or even good).
    ples are not intended to be exhaustive (or even good).)
  • Async Jetpack  + (People who care about performance. Makes the browser not lock up.)
  • Features/Thunderbird/Social search  + (People who want to search more than one type of search engine at the same time.)
  • Features/Thunderbird/One Line Address  + (People who want to send email to one perso
    People who want to send email to one person, or more than four people. People who want to send email to one person will see more of the content of the email. People who want to send email to more than four people will see more than four addresses at a time.
    ll see more than four addresses at a time.)
  • Privacy/Features/Tracking Map  + (Quantifying how much web sites know about
    Quantifying how much web sites know about you is hard. This tool will help figure that out and act upon the sites you don't trust. # Alice has turned on the DNT header, but wants to know if sites are honoring it. One way to check is to see if she's still being tracked (but measuring that is hard). This tool helps visualize who's got your cookie info. # Bob doesn't want to disable cookies, but periodically wants to delete cookies from third parties who he encounters on many web sites. Making a list and blocking cookies from just those sites is hard (since he has to maintain it himself). Opening this Tracking Map and clicking on the sites whose cookies he wants to block is much easier.
    cookies he wants to block is much easier.)
  • Features/Firefox/In-content UI Visual Unification  + (Quoting from [http://blog.stephenhorlander
    Quoting from [http://blog.stephenhorlander.com/2010/06/in-content-ui-visual-unification/ shorlander's blog post]: "The goal is to create something that looks appealing, connects the variety of different types of UI, is recognizably in-content UI and can be styled per platform." This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.)
    xperience, and Connect" vision statement.))
  • Security/Features/Intranet CSRF Blocker  + (RFC 1918 defines the set of CIDR blocks wh
    RFC 1918 defines the set of CIDR blocks which are not publicly addressable from the Internet and which are generally used to address hosts found on private home or enterprise networks. Included in this range are: 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8. Starting around 2006, security researchers, notably Jeremiah Grossman and Robert Hansen, began pointing out an architectural weakness in the Web that allowed (untrusted) websites on the public Internet to cause requests to be sent to hosts on these private networks, which would otherwise be protected by NAT. Malicious requests of this type can be used by an attacker for: port scanning internal networks, reconfiguring home routers, sending print jobs to network printers, and CSRF to applications that use network access as authentication. For more background, see: * [http://www.blackhat.com/presentations/bh-usa-06/BH-US-06-Grossman.pdf "Hacking Intranet Websites from the Outside"] * [http://www.blackhat.com/presentations/bh-usa-07/Grossman/Whitepaper/bh-usa-07-grossman-WP.pdf "Hacking Intranet Websites from the Outside (Take 2)"] * [http://www.symantec.com/avcenter/reference/Driveby_Pharming.pdf "Drive-By Pharming"] * [http://ha.ckers.org/blog/20080108/cross-site-printing/ "Cross site printing"]
    ross-site-printing/ "Cross site printing"])
  • Features/Security/Low rights Firefox  + (Related bugs * Sandboxing in general: http
    Related bugs * Sandboxing in general: https://bugzilla.mozilla.org/show_bug.cgi?id=730956 * OS X 10.5 Sandbox: https://bugzilla.mozilla.org/show_bug.cgi?id=387248 * Use seccomp to sandbox on Linux : https://bugzilla.mozilla.org/show_bug.cgi?id=742434 The use case : Protect users post-exploitation without compromising their Firefox experience or deprecating any functionality. Core assumption : The sandbox is intended to mitigate post exploitation, threats ie when complete control of the sandboxed process has been taken by the attacker via the successful exploitation of a vulnerability, including avoiding all other OS level mitigations such as ASLR, stack protection, etc. In this situation, the Firefox.exe process containing the vulnerable code is completely compromised and the attacker can do anything that process (by default, really meaning the user running Firefox) is allowed to do.
    he user running Firefox) is allowed to do.)
  • Silent Update not now prompt  + (Sandra is using Firefox to check her email
    Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version. However, as Firefox runs through the installation process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with the new version of Firefox. Given there are incompatible add-ons, Firefox will not update Sandra to the latest version of Firefox and enter a 10 day grace period that will continue to check in the background if her incompatible add-ons become compatible. There are a few things to note here: *If both add-ons become supported within the 10 day grace period and the Firefox update happens in the background successfully, Sandra will be able to continue to user Firefox as if nothing happened. *Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will prompt her to update at that point with some language "warning" language that her browser is not secure and she could be vulnerable to attacks. She has the option to "remind me later". *If she selects "remind me later", Firefox will defer for 10 additional days and on day 20, Firefox will automatically update her to the latest version and disable any add-ons that continued to be incompatible. Firefox informs her via the notification bar that certain add-ons were disabled due to a Firefox security update. Things to note here -- the reason to go down the path of a "required" update is the following: *Based on our data, we have learned over time that 99% of active add-on developers update their add-ons to become compatible with the latest version of Firefox. *To reduce product fragmentation and user confusion, our goal is to offer the most secure, feature-rich and optimized browsing experience that continues to move the web forward. All Firefox users should be offered that opportunity and we're fully aware that certain add-on functionality is critical to users' workflow and will do our best to work with developers to stay updated. *Users will continue to have the option to turn off 'Updates' in general, but are encouraged to leave that checked so they have the best experience. Not only will we continue to innovate by delivering new features, but enhancements under the hood like memory reduction/performance/etc. will help create new experiences across the web.
    /etc. will help create new experiences across the web.)
  • Security/Features/OCSP Must Staple  + (Security-critical sites will use this to make sure we can tell if their certificate has been revoked.)
  • Identity/Features/NativeSignInToWebsite  + (See https://wiki.mozilla.org/Kilimanjaro/ProductDraft#All_your_devices_recognize_you_and_enable_access_to_your_ID-attached_services)
  • Privacy/Features/DOMCryptAPI  + (See https://wiki.mozilla.org/Privacy/Features/DOMCryptAPI/UseCases)
  • Security/DNSSEC-TLS  + (Server administrators can put key/certificate information in DNS records they control (e.g. TLSA records). This information is verifiable through DNSSEC. The browser can then use this in place of or alongside certificate chain validation.)
  • Features/Desktop/Panel Menu  + (Simplifying the ability for users to find what they're looking for, increase relative discoverability for the important items, have a predictable and consistent approach to interface customization.)
  • Smooth scrolling  + (Smooth scrolling is the animated sliding e
    Smooth scrolling is the animated sliding effect when you roll the scrollwheel. Without it, the page jumps one or several lines at a time when scrolled. It's a subtle effect, but it makes it easier to follow content as it moves and is a more enjoyable effect. It also compares more closely to touch-based scrolling and so increases consistency across PCs and touch-based devices.
    stency across PCs and touch-based devices.)
  • DevTools/Features/CSSDoctor  + (Some relevant discussion in [http://groups.google.com/group/mozilla.dev.apps.firefox/browse_thread/thread/f80de82af4b6a19d# "CSS developer tools" thread on dev-apps-firefox])
  • Labs/Cherrypicker  + (Someone who wants to try a webapp but is u
    Someone who wants to try a webapp but is uncomfortable sharing their primary email address, or for whom the expected impact of possibly getting junk/spam/bacn is a deterrent to exploring the web. Someone who is an eager user of webapps, but who'se drowning in an overflowing inbox and wants help sorting the wheat from the chaff.
    nts help sorting the wheat from the chaff.)
  • Speedy Session Restore  + (Starting up the browser is a common experi
    Starting up the browser is a common experience for all Firefox users. Many Firefox users have session restore turned on and we intend to make that the default in an upcoming release. Session restore can cause the browser to start up more slowly than without session restore. Changes that make session restore have less of an impact on startup time will allow us to enable session restore without users being bothered by slower startup times.
    rs being bothered by slower startup times.)
  • Platform/Features/DOMBindingsNodeListAndArrayBindings  + (Stuff is slow. We want it to go faster.)
  • Services/AndroidSyncFP  + (Sync to and from your Android device for (in priority order): * Bookmarks * History * Passwords (Q1? Still waiting for feature definition to firm up.) * Tabs (Q1) * Form Data (Q1) * Prefs (Q1))
  • Services/Sync/AndroidSyncPushToDevice  + (Sync-enabled mobile users. Push-to-device is one of the key value propositions for Fennec and Sync.)
  • Features/Jetpack/Easy Page Mods  + (Target audience is add-on developers who i
    Target audience is add-on developers who iteratively change their add-on's scripts to test changes. Allowing the developer to more quickly/easily test their changes to contentscripts will allow them to finish their job more quickly, saving them from the frustration of waiting for Firefox to start and install the add-on.
    r Firefox to start and install the add-on.)
  • Browser translation  + (Target users: people who need to browse we
    Target users: people who need to browse webpages in their non-native languages. User Research Process: - Interview 6 non-native English speakers in SF to understand their online browsing behaviors, potential needs for translation help. User Research Findings: - People who don't speak English neither visit any English websites, nor try to read anything in English. - Language block access. They still care about things happening in the rest of the world, such as news, travel, also shopping, education. However, searching these content in native language does not help find reliable/official information. - Non-native speakers still need extra help, online dict, translation add-on, etc. -I use many social networking websites like Google plus and Twitter. I do follow peoples who are not use English as their main language. When I get their updates my news feed, I need to translate it. The 'Selected Content Translation' feature will come to use here. A real-world user scenario: Parents are browsing the web, looking for information about traveling to Japan, such as local weather. Their goals are to get most genuine and reliable information from Japanese local content providers before going on a trip.
    content providers before going on a trip.)
  • Features/Thunderbird/Instant messaging in Thunderbird  + (Targeted users are people who use Thunderb
    Targeted users are people who use Thunderbird for their emails and may IM the same set of contacts. ====Presence information==== * Seeing that the sender of an email is online can help decide an IM conversation will be better than an email reply. ====Unifying data storage==== * All contact information handled in a single place * All archives searchable in a single place: this removes for the user the burden of remembering which communication medium was used. ====Leveraging links between IM conversations and emails==== * Keeping links between emails and the related IM conversations can simplify further processing of the exchanges: ** when rereading the whole discussion ** when forwarding it * A link can either be strong, when it comes from an explicit user action (eg. the user started a chat from the presence info of an email header) or weak if Thunderbird assumed it (eg. an IM conversation happened between 2 emails with the same people involved). * Accessing the list of recently exchanged emails when a chat begins can save time: ** if the user was about to ask a question that's already answered in an unread email ** if the contact starting the chat is following up to a recent email (See also the "How can this bring additional value for users?" question on [[Talk:Features/Thunderbird/Instant_messaging_in_Thunderbird|the discussion page]] for some related discussion and a few possible future use cases).
    sion and a few possible future use cases).)
  • Improve display of location bar results  + (Targets all users of the location bar.)
  • Features/Platform/CSP Sandbox  + (The CSP sandbox attribute is designed to allow sandboxing of content that cannot necessarily be wrapped in an iframe sandbox, or that can be accessed directly, avoiding any sandboxing that may be done by a containing iframe.)
  • Features/Jetpack/Jetpack-Mobile-Simple-Prefs  + (The Developer defines the preferences need
    The Developer defines the preferences needed for their add-on in their package.json file. Those preferences are then converted upon run-time to a native preferences screen which allows those preferences to appear in the Native settings dialog below the other Firefox Preferences in an Add-on Settings option(with the add-on's name displayed).
    option(with the add-on's name displayed).)