Mobile/UI/Designs/TouchScreen/Fennec 1.1+: Difference between revisions

Some older work here: https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/workingUI/CSM  

Open bugs  

 

*{{bug|461854}} - Need context menu UI

Open bugs  

 

*{{bug|460966}} - mouseover css drop down menu doesn't work with fennec, but works with iphone

== Add Copy and Paste support ==

We should have Copy (and Paste) support in Firefox Mobile.Direct communication with other applications offers a better User Experience than Copy and Paset(it eliminates excise) But C&P would give the possibility to exchange data with applications which (currently) don't connect with Firefox Mobile. It would fit into the existing aims for having a cursor support for webpages with pannable areas or general cursor driven interaction.  

== Changes for Portrait use ==

Open bugs  

Open bugs  

=== Awesome bar/view<br> ===

&lt;TBD&gt;<br>  

=== Tabs bar (Left side pane)<br> ===

&lt;TBD&gt;<br>  

 

&lt;TBD&gt;<br>  

'''Description''': Session restore - the ability to pick up what you were doing before a browser restart - is a very useful feature and a signature capability of Firefox. Session restore as-is from the desktop doesn't make sense on mobile though. Simply reloading all previously open tabs doesn't make sense in a data-constrained environment, on top of which the user is more likely to be interesting in a quick transactional interaction with the browser anyway.  

Some possibilities for different approaches include  

 

Open bugs  

 

*{{bug|541421}} - Session restore functionality

'''Description''': Firefox project do make this the new autocomplete method: [https://wiki.mozilla.org/Firefox/Projects/Awesomeformcomplete link] - in 1.9.2  

 

*{{bug|466770}} - fix content autocomplete

'''Description''': I think the primary usecase here is just wanting a permanent off-line available copy of a webpage (so a receipt, or a boarding pass). It's probably not necessary, or very useful, to support full html+CSS+images saving out of a webpage.  

Open bugs  

 

Design proposals  

 

*Proposal 1  

**Put a "Save Page" option in the site menu (see Extended Site Menu)  

**Just treat the saved file as a download, using a default download directory rather than opening a file picker, and use Fennec's existing download system: [http://www.flickr.com/photos/madhava_work/4351394977/ [[Image:|4351394977_d8bd245234.jpg]]]

'''Description''': Access probably to be provided through the extended site menu  

 

*{{bug|541817}} - Fennec needs find in page functionality (CTRL+F)  

*can't find the original bug

In addition to Larry, the site menu should contain options the desktop Firefox provides in the menus or elsewhere in the chrome. These options apply to content browser is displaying and can be provided by the content (such as subscription to feeds made available with link tag in the head of HTML file) or browser UI (such as Save as). The menu could contain options also for activating browser features such as "Find in page".  

*Proposal 1: [[Mobile/UI/Designs/TouchScreen/Fennec 1.1+/Extended site menu|Extended site menu]]  

**comments on this proposal:  

**the set of options should be vertically pannable once the number of options exceeds the available screen space  

**sites can offer several feeds and search providers, but we don't want each one of these to get its own slot in the menu. In both of these cases, if the site only offers a single option, then tapping the associated menu item should subscribe to it or add it, etc. If there are multiple, the menu item explain that and bring up a selector widget.  

**we have to make it visually clear that this menu is on top of the browser underneath and not another webpage (when there are enough options that it takes up the whole screen).

<br> [http://www.flickr.com/photos/madhava_work/4351405309/ [[Image:|4351405309_0cf41b25c1_o.jpg]]]  

Where, if there are multiple feeds or search providers, tapping the option in the menu brings up a chooser overlay:  

[http://www.flickr.com/photos/madhava_work/4352154856/ [[Image:|4352154856_5c61f69146.jpg]]]  

== Accommodate a virtual keyboard ==

'''Description''': full problem statement coming  

For more information, see [[Mobile/UI/Designs/TouchScreen/Fennec 1.1+/Option B for Awesome screen layout revision|Option B for Awesome screen layout revision]].<br>  

Open bugs  

 

*{{bug|436076}} - Certificate Management  

*{{bug|478938}} - Add ability to choose client certs

Previous UI work: https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/workingUI#Client_Certificates

 

 

previous UI work: https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/workingUI#Username.2FPassword

 

 

 

== scroll indicators  ==

*{{bug|515166}} - Support scroll indicators in XUL richlistboxes and scrollboxes

== controls for video  ==

Open bugs  

*{{bug|465839}} - Controls for video content are missing

*proposal 1

== Feed subscription ==

*{{bug|477714}} - Provide UI for subscription to feeds (RSS, atom, etc.)

== Edit or clear site-specific prefs  ==

'''Description''': There currently is not a way for users to undo site-specific choices they've made in response to prompts from Firefox. Examples include:

*and more!

The simplest model for mobile would just be to let users clear all site-specific prefs, and this is what the listed bug proposes to do, via an extended site menu

Open bugs  

*{{bug|456077}} - No mechanism to edit popup preferences

*{{Bug|479975}} - add an explanatory UI for the gesture engine

== Improve discoverability of side-areas ==

Open bugs  

*{{bug|478037}} - allow zooming out to past the page edges so that controls are all visible

On multitouch devices, pinch to zoom is the defacto standard here, and we should do the same. On non-multitouch devices, we still need some way of zooming by increment, rather than to structure.

*{{bug|497479}} - can't do a deep zoom into a paragraph of text

*{{bug|533560}} - Volume control does not control zoom level

== Replace modal dialogs with modeless alternatives ==

== Shorter mobile-appropriate messages  ==

== More helpful network error pages  ==

 

 

 

 

 

 

Only a few are actually important. Candidates:  

 

*mail  

*RSS  

*calendar

== Improved in-content theme ==

Open bugs  

== Support personas  ==

*Connection to Session Restore thinking

== Improved visibility of and access to add-ons catalog  ==

== Haptic feedback  ==

== Multitouch gestures  ==

 

 

*full screen standalone for webapps - no sidebars, etc. - just a system toolbar

The behaviour detailed above can be really confusing from the user point of view, because sometimes s/he has to swipe the left-side pane to the view and sometimes press the button in the top-right corner to exit the view for selecting the content for the tab. It would improve usability, if the user could cancel the selection for the tab content in the same way in all cases.

 

 

 

 

 

 

Fennec can be run on operating systems which reserve the top area of graphical user interface for showing a functional Status bar (or other suchlike short/flat element taking full width of the view) provided by the platform (cf. e.g. Android or Windows mobile). The system-provided Status bar can provide the user with useful functions and/or features but it also disables showing Fennec in full Full screen mode.

The user may want to use the Fennec

*'''with''' the system-provided Status bar because it provides useful functions and/or features she needs/uses frequently and she sees it as an advantage rather than an disadvantage that the element is shown constantly in the view.

*'''without''' the system-provided status bar because she does not see it as a critical feature for using the device (i.e. no added value for her) and she wants to reserve all screen estate completely for the actual content.

Because it depends completely on the needs of user whether the Fennec should run in full "Full screen" or not, browser should not decide on behalf of her to hide the system-provided Status bar but let the user user to decide what is best for her.

Fennec should provide the user with a setting for enabling/disabling the system-provided Status bar or other corresponding platform-provided functional element. The setting should be available in the browser settings.<br>