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 "All users that use panels.". 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

  • DevTools/Features/ToolsWindow  + (==== User with Multiple Monitors ==== A user with multiple monitors wants to put their tools on one monitor while they have their main browsing window open on the other monitor.)
  • Features/Desktop/Ability to run concurrent channels  + (==== Web Developer use case ==== Here are
    ==== Web Developer use case ==== Here are the defining characteristics of pretty much every web developer that I have contact with in my other open source projects and consultancy companies: # They rarely want to give up the stability of their setup. They '''need''' a functional Firefox with a stable, predictable Firebug. It's their bread and butter, and they need this to always work. # They don't know about the profile manager (I'm always surprised about this, but it makes sense, since it's invoked via command line, and you have to know it exists in the first place to look for it) # They'd like to test in multiple versions of Firefox at once, especially once we hit beta, so they know what to expect from the sites they are working on, so their clients won't come back and yell at them 1 month later when the new version is out. # Having their history, bookmarks and settings available in the Beta, Nightly or whatever version they are testing is a bonus, but not super important to them. How I'd like us to solve this: # Make the solution conceptually simple, and make it easy to identify what browser you're actually using. # Make running the various versions in parallel dead simple, and make this '''the default behavior'''. # Use Sync to transfer data and settings, and don't try to reuse the same profile across different channels. ==== How it would work for them, step by step ==== I'm a web developer. I have the latest stable version of Firefox installed. I have two paths to discovering the Aurora/Beta channels: # By downloading it from the Firefox web site # By following a link or selecting an option in the About dialog ...both of which would give me a downloadable installer instead of trying to switch the release version I have with something else. Let's say I decide to test the Beta: * I get the downloadable installer, branded "Firefox Beta" everywhere. No version numbers anywhere. * I install the thing, and end up with an entry called "Firefox Beta" in my start menu. * When I click the Firefox Beta entry, it starts '''in parallel with my existing, running Firefox'''. It has a blank profile that is associated only with the Beta. * The first page I see is "Congratulations, and thanks for helping us test Firefox Beta. Here's how to set up Sync if you want your data & settings to exist in all of your Firefox setups." * I set up Sync, have my data & settings available, and I'm able to quickly switch between Firefox and the upcoming Firefox+1 (= Beta) to see if the project I'm currently working on is working the way it should in the upcoming version ** I can even run an experimental new Firebug in the Beta, and have my stable Firebug in the Release version. * When e.g. Firefox 4 release upgrades to Firefox 5, my Firefox Beta will automatically be what will become Firefox 6. * I can keep these start menu entries around essentially forever, and always be able to test the latest on each channel, with a minimum of confusion, since the application name always reflects what I'm looking at. ==== Summary ==== If someone was testing all of our variants, their start menu on windows would then look something like this: * Firefox * Firefox '''Beta''' * Firefox '''Aurora''' * Firefox '''Nightly''' These entries would have the respective logos of the various channels. It would appear in a similar way in the Mac OS X dock. They would update on their respective channels, in a mostly silent manner. These would: # All be separate binaries, with their own directories named accordingly. # Never mention the version name in the start menu or app name. # Have separate process names, like firefox-beta.exe, firefox-aurora.exe, etc. # All of them would run in separate profiles '''by default'''. I believe this is conceptually simpler for the end user, easier to work with for us, and solves the testing use cases in a better way than what replacing the binary from under you will accomplish.
    placing the binary from under you will accomplish.)
  • Features/Thunderbird/BigFiles  + (==== When a user attaches a 'Big File' ===
    ==== When a user attaches a 'Big File' ==== If the file is above a certain size, warn the user and offer to use online storage instead of attachment. Note: The size could be an arbitrary value, or set by the user, or even retrieved on the fly by analyzing recipients domains ( for example has a limit of 25MB). ==== When an email is bounced ==== If Thunderbird detects that the bounce reason is a 'File Too Big', offer to resend via BigFile. ==== On-the-fly setup/signup ==== If the user is about to use BigFiles but has not configured TB for it, allow the setup or signup procedure to happen on the fly, in such a way that the user should not have to bother pre-confguring BigFiles before first using it. A list of pre-configured online storage services should be proposed for setup or signup. ==== File detach to the cloud ==== Detaching a file from an email should be possible both on local/network drives and in the cloud. Detaching to the cloud will save local storage space and make the document accessible from the cloud. ==== Quota management ==== Detect over quota situations (mostly in the case of consumer online storage services free offers) and guide towards resolution (signup for premium service, file deletions...) ==== Advanced features ==== Some cloud storage services offer advanced features. For example, some consumer online storage services offer document tracking (YouSendIt for example). Making this information available through Thunderbird might be interesting for these users. ==== Faster attachment transmission ==== - File is uploaded once regardless of how many users are on the 'To/Cc/Bcc' list - Sending the same file through different emails (to different set of recipients) could reuse already uploaded file, saving the upload time. - File upload/download is binary vs. encoded when using email attachment: twice as less data transfered
    attachment: twice as less data transfered)
  • DevTools/Features/TimelineView  + (==== Why is my app slow? ==== Browsers ar
    ==== Why is my app slow? ==== Browsers are quite complex environments. The timeline view can help developers visually spot why their application is slow. By plotting things like: * network traffic * JavaScript * GC pauses * reflow/repainting together, users can correlate events that cause user interface slowness.
    events that cause user interface slowness.)
  • DevTools/Features/ScratchpadReRun  + (==== Writing experimental code ==== The u
    ==== Writing experimental code ==== The user is creating a new function in JS. They write the initial version of the function and run it. The results are not what they want, so they go back and make some changes. They want to quickly redefine the function and run their test. ==== Gathering data via Ajax ==== The user has functions on their page that collect up information from the server, and they are experimenting with some changes to the page. They need to keep re-running commands that gather the data from the server and perform some action once it has arrived.
    d perform some action once it has arrived.)
  • Platform/Features/WebRTC  + (==Phase 1== We will support applications t
    ==Phase 1== We will support applications that do the following: * Call a friend using a social API like Facebook. From the chat/online window the user can click on a person and start a video call with them in the browser. The video/audio/data should be securely transmitted. * Video conferencing / sharing slides from inside an app. The user calls someone from inside an app and is able to share files, images, slides, etc through the P2P connection as he/she is talking via the data channel. * Games that integrate video, audio and data sharing. For example a chess game where you see the video and hear the audio of your opponent and play the game live using WebRTC’s data channels. Note: Basic Interoperation between Firefox's WebRTC code and Chrome's WebRTC code will be supported as part of phase 1. This should include video, audio, and data channels interop if Chrome supports data channels in time. The following is a nice-to-have use case that we may or may not support in phase 1. If we don't support it in phase 1, we will support it in phase 2: * Remote assistance/co-pilot - you "look over the shoulder" of someone as they browse (optionally controlling the mouse/keyboard), while also talking with them over audio or audio+video. ==Phase 2== * Support for Android Mobile devices. * Probably support for B2G Mobile devices (TBD) For reference only: * [ IETF Use Case Document]
    ts/?include_text=1 IETF Use Case Document])
  • Ark  + (A developer has the following thought: "I really need a tool/library/module for doing _____." --> the developer should be able to fill in that blank (whatever it is) by visiting the Mozilla Ark.)
  • DevTools/Features/ScratchpadAutocompletion  + (A simple example is a JavaScript user enters "document." in the Scratchpad. In the Web Console, typing "document." will popup a small window with the properties of the document object. In the Scratchpad, it should do the same.)
  • Security/Features/OCSP Stapling  + (A site wants to use OCSP but not rely on 100% availability of the OCSP responder or a fast enough connection to the CA.)
  • Security/Features/SSL Error Reporting  + (A user browses to a secure website, but ge
    A user browses to a secure website, but gets the warning: "This Connection is Untrusted". If the user has already opted-in to sending telemetry data to Mozilla, then Mozilla telemetry will collect the appropriate information. Another use case will be when [ Certificate Pinning] is available. When the set of keys in the certificate chain do not intersect with the set of keys 'pinned' in the browser, then an alert will be displayed to the user, and provide a "report to Mozilla" option. The user should be warned that their interaction with the website might be watched, so they should avoid entering personal data, but they should be able to accept the risk and go forward to the site. Note that the reporting mechanism could possibly get blocked by a malicious actor (or for some other reason), and if that happens the user should be notified that the reporting mechanism may be being blocked, and the information should be made available (in a file?) so the user can email or submit the information to us some other way.
    bmit the information to us some other way.)
  • Features/Desktop/Firefox reset option on reinstall  + (A user determines that "something" is wron
    A user determines that "something" is wrong with Firefox, so they attempt to fix it by reinstalling. When Firefox (or the installer) detects that the same version of Firefox already exists on the computer it will offer the option to repair Firefox by resetting it to its default state.
    efox by resetting it to its default state.)
  • Platform/Features/File upload for a directory  + (A user wants to upload an entire directory
    A user wants to upload an entire directory to That user clicks on the upload button on the web site picks a directory of files to upload. When the dialog closes, the user sees a set a progress bar that shows both file upload progress and the overall progress. (This implies both per-file access and overall-size progress.)
    er-file access and overall-size progress.))
  • Lightbox  + (A web developer wants to create a lightbox
    A web developer wants to create a lightbox effect without a hassle and avoiding to add another js and css file to his site. So he adds the attribute data-* to all the thumbnails he wants to showcase and the effect is being taking care of natively by the browser.
    ng taking care of natively by the browser.)
  • Privacy/Features/Cookie tagging  + (API Use cases: * Set cookie with attribute / tag (via nsICookieService setCookieString, setCookieStringFromHttp / nsICookieManager2 add) * Read cookie attribute / tag * Check if named attribute / tag is set or present)
  • Features/Jetpack/Doorhangers  + (Add-on developers want to inform the user of information. Could be used as a first-run experience.)
  • Features/Jetpack/Addons In Toolbar  + (Add-on developers will use this to create awesome experiences for their users.)
  • Jetpack/Ship SDK via AMO  + (Addon developer Alex wants to write his ex
    Addon developer Alex wants to write his extension with the SDK locally (eg, not using the Addon Builder website). He writes his extension with SDK version 1.5. A few weeks later, SDK 1.6 is released, containing necessary changes to the SDK's libraries for compatibility with upcoming releases of Firefox. Alex then needs to manually repack his extension with the new version of the SDK. The way things are now, Alex needs to look for the release announcement for SDK 1.6 to find the download links to the 1.6 zip or tarball files, download that archive, extract it somewhere, activate 1.6's version of cfx, then repack the extension. Instead, if the SDK could be updated via AMO, Firefox could prompt Alex to download the new version of the SDK, Firefox then downloads the zip or tarball and possibly even automatically unpack it somewhere on Alex's hard drive. All Alex then needs to do is activate cfx and repack his extension.
    is activate cfx and repack his extension.)
  • Identity/BrowserID/Addon  + (All Firefox users who use BrowserID. This addon provides an in-browser experience for using BrowserID, making phishing and spoofing of the BrowserID site much more difficult.)
  • Firefox/Features/Theme Refinement and Evolution (Australis)  + (All Users)
  • Chrome Style Editing  + (All add-on authors will immediately benefit from this enhancement, as well our own Firefox developers.)
  • Addon Console  + (All add-on authors will immediately benefit from this addition, as the the only existing logging mechanism is the Firefox error console.)
  • Features/Thunderbird/Home Tab  + (All users)
  • Security/Features/Strange SSL Cert Change Alert  + (All users benefit whenever they trust an S
    All users benefit whenever they trust an SSL connection. The following are examples of situations which might prompt suspicion: - a site's certificate changes from one CA to another; - a site's certificate changes when it is not near expiry; or - a site's certificate changes from EV to DV. The following are examples of actions Firefox might take if a certificate is suspicious: - treat the certificate as untrusted; - contact a Mozilla-run notary to ask about the certificate; or - contact a Mozilla-run notary to warn about a suspected attack.
    n notary to warn about a suspected attack.)
  • Firefox/Features/Chrome migration  + (All users new to Firefox who have a Google
    All users new to Firefox who have a Google Chrome profile on their system. A Chrome user wants to try out Firefox so he downloads it and installs it. Unfortunately, for him and the 150 million other Chrome users who might want to try out Firefox, his Chrome settings and data are not migrated so when he goes to log into Facebook and his username and password are not pre-filled, he says "screw it" and returns to Chrome.
    he says "screw it" and returns to Chrome.)
  • DevTools/Features/GCLI  + (All users of the web developer tools.)
  • Tab Strip Visual Redesign  + (All users that use tabs.)
  • DevTools/Features/Highlighter  + (All web developers and designers of many d
    All web developers and designers of many different skill levels need to work with CSS and therefore will use the Page Inspector regularly. ==== Tracking Down a Styling Issue ==== The Page Inspector is part of the [ Font Fixing] use case. ==== Learning About a Page ==== Starting with the original "developer tool" for the web, View Source, people have always used tools to look at existing sites and learn about what makes them work. The Highlighter and the element-centric tools that are accessed through it can help with this. On the front page of [], there is an accordion widget. How does that get its sleek grey gradient? ==== Making Common Changes To Nodes ==== Add/remove CSS classes, manipulate the ID
    Add/remove CSS classes, manipulate the ID)
  • DevTools/Features/RulesView  + (All web developers use this view at one ti
    All web developers use this view at one time or other. ==== Exploring the Hierarchy of Styles on an Element ==== When picking up a page from someone else (either a third party or an earlier developer within an organization) the rules view helps discover the organization of the stylesheets.
    cover the organization of the stylesheets.)
  • DevTools/Features/CSSEditor  + (All web developers. ==== Working on a New Design from Scratch ==== ==== Experimenting with a Portion of an Existing Design ====)
  • Platform/Features/Dragging out of a page  + (An icon is displayed in gmail. You can drag the link to your desktop and the browser downloads the file to your desktop.)
  • DevTools/Features/RichInfobar  + (Anyone doing web design uses this feature.
    Anyone doing web design uses this feature. ==== Examine Hover Styles ==== It's common to set styles that appear only on hover, so the user needs a way to dig into those styles, see how they're being applied and possibly tweak them using the editing capabilities of other parts of the tools suite. ==== See the effect of a class ==== When tracking down styling issues, especially on elements with multiple classes applied to them, it can be useful to visually see the effect that a given class is having on an element. A convenient mechanism for toggling a class on an element is a good way to accomplish this. ==== Set an ID on an element ==== JavaScript developers often have collections of functions built up that are designed to take elements or element IDs. By being able to quickly set an ID on an element, these developers will have a handle they can pass into their functions.
    handle they can pass into their functions.)
  • DevTools/Features/PseudoClassLock  + (Anyone doing web design uses this feature.
    Anyone doing web design uses this feature. ==== Examine Hover Styles ==== It's common to set styles that appear only on hover, so the user needs a way to dig into those styles, see how they're being applied and possibly tweak them using the editing capabilities of other parts of the tools suite.
    ilities of other parts of the tools suite.)
  • Identity/Features/Sign into the browser  + (As a user, I want to know at a glance whet
    As a user, I want to know at a glance whether I am signed into the browser, or if someone else is. As a user, I want to be able to easily find the sign in button/link/option. As a new user, I want to be able to create an account by providing my email address and choosing a new password. As a new user, I want to be able to verify my email asynchronously, so that I can use the browser immediately. As an existing user on a new device, I want to be able to sign into my account using my email address and password. As an existing user returning to a device, I need to use my password (but not my email) to sign back in. As an existing user, I want to be able to reset my password if I forget it. As a new signed-in user, I want to know about the services and features now available to be by having signed in. As a returning signed-in user, I want to quickly get back to my personalized browser profile. As a signed-in user, I want to see my list of email addresses (and not a sign-in screen) when I click "sign in" at a Persona-supporting site.
    ck "sign in" at a Persona-supporting site.)
  • DevTools/Features/Layout  + (As with the Style Inspector, the use cases are similar: # a user is trying to fix a problem with their element's dimensions # a user is trying to learn about how another page is designed)
  • Features/Jetpack/Browser-e10s-Support  + (As with the work to make add-ons written w
    As with the work to make add-ons written with the Add-on SDK run in their own process, this should work with no input from the developer at all. While we want the developer to know that this is being done for her, she need not do any extra work for the elements she's using to run in the correct processes.
    e's using to run in the correct processes.)
  • Features/Desktop/About Version  + (Asa heard something about a new version of Firefox on the radio and he's not sure if he's got it or not. He opens the About dialog and is comforted to read that he is on the latest version of Firefox as of Firefox's last check 1 minute ago.)
  • Features/Jetpack/Module-Sharing  + (Bob is a developer who likes to create add
    Bob is a developer who likes to create add-ons for Firefox. He uses the SDK and wishes there were an easier way to do authentication with twitter for his new add-on. Bob, while using the SDK, makes a search for already written twitter authentication modules and finds that there are 2 of them. He sees that one module has been used more and reviewed well and decides that he will try it out. In his add-on code, Bob puts the URL for his chosen twitter auth module into his require statement. When he runs cfx to build his add-on, the module is retrieved from the repository, installed, and used as Bob has included in his code. Bob is happy.
    ob has included in his code. Bob is happy.)
  • Security/Features/CA pinning functionality  + (CA Foo is compromised and grants a certifi
    CA Foo is compromised and grants a certificate for to an attacker. The owners of have their site pinned to certificates from CAs Bar and Baz, so when the attacker attempts to use the certificate from CA Foo, he fails to satisfy the pinning requirement. Any users presented with his certificate will not have access to the fraudulent connection (hard fail). The spec does not necesaily ping the CA, it pins a subset of keys so that at least one of the keys pinned must be in the CA list of the certificate.
    must be in the CA list of the certificate.)
  • DevTools/Features/SourceMap  + (Case 1: Minified files A user can take .j
    Case 1: Minified files A user can take .js source files and compress them with the Closure Compiler. Errors and log messages in the Web Console will refer to the original .js files. Case 2: Languages which compile to JavaScript You can start with an original file which contains any language that compiles to JS (for example, CoffeeScript). Any logged output or uncaught errors will refer back to the original file, rather than the generated JS file which is actually being executed.
    JS file which is actually being executed.)
  • Privacy/Features/Handshake checkpoint API  + (Convergence: Moxie would really like an AP
    Convergence: Moxie would really like an API like this for simplifying the Convergence ( add-on implementation. He had to "jump through some pretty prolific hoops in order to replace the browser's default certificate validation with my own."
    fault certificate validation with my own.")
  • App Walkthrough  + (Create a go-to location for step-by-step instructions and resources that aid the user in every step of the app creation process, from an initial high-level introduction through publishing on the Mozilla Marketplace.)
  • Privacy/Features/mozCipherAddressbook  + (DOMCrypt (see [[Privacy/Features/DOMCryptA
    DOMCrypt (see [[Privacy/Features/DOMCryptAPI]] is a public key crypto API, which is useful as-is, but to enhance the user experience, a simple method to collect and store your contact's public keys would make DOMCrypt a bit more powerful. This simple API adds to window.mozCipher (which is provided by DOMCrypt): window.mozCipher.getAddressbook(); It also adds a browser-side notificationbar that is displayed when a "addressbook-entry" meta tag is encountered. This notificationbar asks the user to save or ignore the "contact entry". This is a very simple way for endusers to exchange public keys and is presented in a language that is easily understood. Users need each other's addressbook entry to exchange private message data. This simplifies the nomenclature greatly, which will help bring more user control and privacy to users who care to exchange data on the web in a more secure manner.
    e to exchange data on the web in a more secure manner.)
  • Features/Thunderbird/Improved Build System  + (Developers and building of Thunderbird.)
  • Security/Features/Application Reputation  + (Downloading popular, legitimate applicatio
    Downloading popular, legitimate applications: warnings should become less severe and less redundant. Downloading known malware or unknown applications: warnings should become more severe and clearer about the origin of the download. Perhaps more similar to the UI for installing Firefox addons (since the result is equivalent).
    x addons (since the result is equivalent).)
  • Features/Jetpack/CFX in JS  + (During first development phase, the very f
    During first development phase, the very first audience will be the Jetpack team. It allows us to dogfood the SDK itself while building such complex application. And as most of the team is Javascript oriented, it will be easier to modify and review code of cfx in future. On last iterations, addon developers will be able to build addons without any other dependency other than: Firefox and one addon, "cfx in JS". Currently, on the first hand, developers have to install python in order to build addons. This is particulary hard for people on Windows, where command line application using Python isn't that easy to install and use. On the other hand, they may use Addon-builder, whose only requirement is Firefox. But Addon-Builder is more limited than cfx (localization and preferences support is still to be done), and isn't always usable on slow/bad internet connections. On the half way of this project, CFX in JS will allow Addon-Builder to build addons on client side instead of server side. That's a key feature in order to allow Addon-Builder team to start working on an offline-capable version of this service.
    n offline-capable version of this service.)
  • Firefox/Features/InstallerUIRewrite  + (Enable product (stub installer) downloads over SSL)
  • Features/Desktop/Make Add-ons Awesome  + (End users are the primary target here, specially less knowledgeable users who are more likely to install malicious or unwanted add-ons unknowingly.)
  • Features/Desktop/Clearer Add-on Installation  + (End users are the primary target here, specially less knowledgeable users who are more likely to install malicious or unwanted add-ons unknowingly.)
  • Features/Desktop/BYOB-for-Firefox9  + (Enterprises, Organisations etc and in the later also the Partner Group with Creating Partner Builds)
  • Features/Platform/Chrome-only Plugins  + (Extension authors are the primary target f
    Extension authors are the primary target for this feature. This mirrors a feature provided by Google Chrome and provides a way for extensions to interact with native code which can be easier to use than ctypes and make use of existing plugin-development frameworks.
    of existing plugin-development frameworks.)