QA/Fennec/Milestones/2.0/TestPlan:PlatformIntegration: Difference between revisions

Jump to navigation Jump to search

QA/Fennec/Milestones/2.0/TestPlan:PlatformIntegration (view source)

Revision as of 18:09, 10 November 2010

2,033 bytes added ,  10 November 2010
→‎Anroid
Line 84: Line 84:
* Text selection (in fields, perhaps in arbitrary text) (?)
* Text selection (in fields, perhaps in arbitrary text) (?)


===Anroid ===
=== Anroid ===
* Integration of notifications into the system bar.
** Notification for any downloads(add on download as well as file download) should be displayed into the status bar of Android.
** Updates(when available) notifications should be displayed (not sure about this).
** Tapping on notification should take you to the respective managers(download manager or add-ons manager)
* Hardware buttons functionality.
** Menu button (WIP)
*** The Menu button should handle find in page, share page.
** Back button
*** The back button should be able to move the pages back according to the session history.
*** After opening a link in a new tab, back button closes the new tab and returns to the original tab.
*** If on the home page or on a page that does not have a session history, the back button should act as a way to close the browser.
*** If there is a modal dialog box or pop up, the back button should dismiss the dialog box leaving the user on whatever as underneath.
*** If the awesomebar or bookmark manager are opened, back button closes them, but the browser stays on the same page. If hit back again, it goes back in session history.
** Search (WIP)
* Variants of onscreen keyboard.
** When typing into the awesome bar, use the keyboard with .com button
** When entering a phone number, pop up the numbered keyboard


* Use menu key as shortcut accelerator
*Integration of notifications into the system bar.
** For hardware keyboards, shortcuts should be supported( For eg. - Menu+L = open location bar, Menu+T = new tab etc.)
**Notification for any downloads(add on download as well as file download) should be displayed into the status bar of Android.
**Updates(when available) notifications should be displayed (not sure about this).
**Tapping on notification should take you to the respective managers(download manager or add-ons manager)
 
*Hardware buttons functionality.
**Menu button (WIP)
***This is the menu button that is present on the android phones. Pressing this buton should bring up the app menu for fennec.
***The availability and contents of the app menu depend on what section of the Fennec UI is active. The contents of the menu will change over time and can be modified by add-ons. Here are the contents for the initial release:<br>'''1. Main browser UI''':<br>  o Site Options - opens the identity panel / site menu.<br>  o Preferences - opens the preference panel <br>  o Add-ons - opens the add-on manager<br>  o Downloads - opens the download manager<br> '''2.Awesomescreen''':<br>o No menu for this release. (Nothing happens when "Menu" key is pressed.)<br>'''3.Tool panels''' (prefs, add-ons, downloads, console, etc.):<br>o No menu for this release. (Nothing happens when "Menu" key is pressed.)
*** Pressing the menu button shows the app menu and locks the titlebar to the top of the screen.
*** Pressing the menu button again hides the app menu and unlocks the titlebar.
*** Touching outside the app menu hides the app menu and unlocks the titlebar.
*** Opening any panel or popup (e.g., opening the awesomescreen by pressing the system "Search" key) hides the app menu and unlocks the titlebar.
*** Tapping on a menu button makes the menu disappear, unlocks the titlebar, and executes the button action.
*** If you touch a menu button and then move your finger off the button before releasing it, the tap is canceled and nothing happens (just like any other button in Fennec).
 
**Back button
*** Pressing the system "Back" key hides the app menu and unlocks the titlebar.
***The back button should be able to move the pages back according to the session history.
***After opening a link in a new tab, back button closes the new tab and returns to the original tab.
***If on the home page or on a page that does not have a session history, the back button should act as a way to close the browser.
***If there is a modal dialog box or pop up, the back button should dismiss the dialog box leaving the user on whatever as underneath.
***If the awesomebar or bookmark manager are opened, back button closes them, but the browser stays on the same page. If hit back again, it goes back in session history.
**Search (WIP)
*** Pressing the search button on the browser UI should bring up the awesome screen with the virtual keyboard shown
** Pressing the search button, when the user is in the awesome screen area, should bring up the search options - the same as the opens that comes up when you tap the magnifying glass key at the right side of the URL bar.
** Pressing the search button on the preferences menu(prefs, addons, downloads, beta tools) should bring up the awesome screen with the soft keyboard visible.
 
*Variants of onscreen keyboard.
**When typing into the awesome bar, use the keyboard with .com button
**When entering a phone number, pop up the numbered keyboard
 
*Use menu key as shortcut accelerator  
**For hardware keyboards, shortcuts should be supported( For eg. - Menu+L = open location bar, Menu+T = new tab etc.)


=== OS Integration Factors ===
=== OS Integration Factors ===
Ashah
451

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/266956"

Navigation menu