You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

Skip to main content

You are here: browser/composer front-end test cases > Test documentation for Navigator context menus

Testing Navigator Context Menus

Maintained by: Sarah Liberman

This test plan covers the functionality of context menus within the web browser (Navigator). Context menus are also known as contextual or popup menus, and refer to the menus that appear when right-clicking (Linux/unix or Win32) or Ctrl+clicking in Mac OS. Unlike the toplevel menus, context menus are currently implemented in a cross-platform manner; see the Toplevel Navigator menus test page for details.

Will test

Testing should cover these areas:

  • Cross-platform consistency among Linux, Mac OS and Win32 products. This includes look and feel.
  • Style, spelling, grammar, etc., of the items in the context menus.
  • Overall functionality, to the extent that a given context menu item will bring up the expected feature.

Will NOT test

The following areas will not be covered. Please refer to the appropriate test plan for further information:

  • Context menu items that appear in apps other than the browser content area, such as
    • Composer (editor)
    • windows pertaining to Mailnews, Address Book
    • toolbars
    • Sidebar
    • Bookmarks window
    • Chatzilla (Mozilla)
    • Instant Messenger (Netscape)
    • 3rd party plug-in content
    • etc.
  • Context menu items whose functionality is covered by another test area. Access to these are covered by this plan, but not how well/poorly they work. These include
    • Selection/Clipboard: including the intricacies of Cut, Copy and Paste
    • Bookmarking
    • Downloading/saving
    • Imaging capabilities
    • Form data management
    • Plug-in content, ie, 3rd party plug-in content

Issues, references & bug information

There are currently implemented UI specification is located at http://mozilla.org/projects/ui/communicator/framework/contextmenus/

There's a good chance that problems which you see with context menus might already exist as reported bugs (or even fixed).

The tracking bug for current context menu issues is 135841.

Typical Bugzilla components would include:

  • XP Toolkit/Widgets: Menus: Infrastructure.
  • XPApps: GUI Features (sometimes): Issues with the content of context menu items (eg, typos, labels, etc.), as well as functionality of [some of] the applications accessed from context menus.

The XP Toolkit/Widgets: Menus component (aka, XP Menus) is for bugs relating to the behavior/functionality (infrastructure) of the context menus themselves, not the applications that can be accessed from them. If there are problems with the functionality of the accessed applications, those bugs go to their appropriate component. For example, if you couldn't access Copy from a context menu, that'd be assigned to the Editor component, rather than XP Toolkit/Widget: Menus.

Keep in mind that the XP Apps: GUI Features component tends to be a general basket for many problems, so sometimes a bug filed here will be reassigned to a more appropriate component. We are currently investigating reorganization of the XP Apps components (see bug 68621 ). In the meantime, check out the Who to bug in Navigator page for some tips.

You might want to check out the Frequent Bugs List, as well as the following Bugzilla queries.

Important : Because these queries are based solely on the XP Toolkit/Widgets: Menus component, they'll also include bugs for toplevel menus. In addition, to find bugs concerning context menu content, you might need to run separate queries (eg, under the XP Apps: GUI Features component).

Test coverage & outline

Test coverage will occur on several levels:

  1. Acceptance tests, which simply covers breadth of functionality.
  2. Functional tests, which covers depth of functionality, including the various types of context menus.
  3. Stress, boundary and negative and other comprehensive tests (where applicable and when possible)
  4. Ad hoc testing
  5. Regression testing

Acceptance tests

Basically ensure the following:

  • Particular context menu items exist (or are disabled given particular milestones) in the expected contexts.
  • Able to bring up and dismiss menus and submenus.
  • Able to read and select context menu items.
  • Keyboard shortcuts to context menu: Hitting these commands should bring up the context menu for currently focused (or selected) item in the page --after which you can use either access keys or arrow keys to maneuver through the menu items.
    • Win32 and Unix: Shift+F10
    • Mac OS: Control+Space --since access keys are not implemented on Mac OS, you can only use the arrow keys to move through the context menu items.
    • The Esc key should dismiss context menus. If a submenu is expanded, then Esc would collapse that expanded flyout, returning to the primary (parent) menu listing.

Functional tests

Overall appearance

  • Look and feel/appearance (eg, opacity, flickering), consistency across platforms: captions, access keys (mnemonics), separators, order of context menu items.
  • Location of context menu with respect to where user clicks the mouse.
  • Note which are greyed out and which aren't.
  • Note access keys.
  • Spelling, grammar, typos.
  • Selection and cancellation of context menu items, including ease/difficulty, side-effects, etc.
  • Any focus effects.
  • Addition or omission of content-specific stuff appearing in the context menu (eg, filenames).

Basic types of context menus

As would be expected the particular menu items listed in a context menu are dependent on the context in which they are brought up. The following menus are based on those outlined in the UI spec for the browser content area, and comprise the more common, basic context menus seen. Access keys (mnemonics) are underlined, and unimplemented items are italicized. Other, not-as-common/complex menus are in the boundary section.

  • Content area context menu.
    • Show Menu Bar
    • Back
    • Forward
    • Reload
    • Stop
    • Bookmark This Page
    • Save Page As...
    • Send Page...
    • Win32 only. Create Desktop Shortcut
    • View Background Image...
    • Character Encoding...
    • Page Properties
  • Selection context menu. Note that these items are also added to other menus, depending on the context (e.g., frame context menu, image context menu, link context menu, etc.).
    • Cut
    • Copy
    • Paste
    • Select All
    • Highlight Selection
    • Web Search for "<selection>"
    • View Selection Source
    • Search Dictionary for "<selection>"
    • Send Quoted Selection...
    • Change Text Direction
  • Text as link context menu.
    • Open Link
    • Open Link in New Tab
    • Open Link in New Window
    • Bookmark This Link
    • Save Link Target As...
    • Send Link...
    • Copy Link Location
    • Bookmark This Page
    • Save Page As...
    • Send Page...
    • Link Properties
    • Page Properties
  • Inline image context menu.
    • View Image
    • Copy Image
    • Copy Image Location
    • Save Image As...
    • Send Image...
    • Send to Buddy...
    • Win32 only. Set as Wallpaper
    • Bookmark This Page
    • Save Page As...
    • Send Page...
    • Image Properties
    • Page Properties
  • Linked image context menu.
    • Open Link
    • Open Link in New Tab
    • Open Link in New Window
    • Bookmark This Link
    • Save Link Target As...
    • Send Link...
    • Copy Link Location
    • View Image
    • Copy Image
    • Copy Image Location
    • Save Image As...
    • Send Image...
    • Send to Buddy...
    • Win32 only. Set as Wallpaper
    • Bookmark This Page
    • Properties
  • Image as URL context menu. Mouse pointer needs to be over the image itself for this menu to appear; see bug 136986.
    • Back
    • Forward
    • Reload
    • Stop
    • Copy Image
    • Copy Image Location
    • Bookmark This Page
    • Save Image As...
    • Send Image...
    • Send to Buddy...
    • Win32 only. Set as Wallpaper
    • Image Properties
  • Text as mailto: context menu.
    • Compose Message...
    • Add to Address Book...
    • Copy Email Address
    • Copy Link Location
    • Bookmark This Page
    • Save Page As...
    • Send Page...
    • Link Properties
  • Form and input field context menu.
    • Undo
    • Redo
    • Cut
    • Copy
    • Paste
    • Delete
    • Select All
    • Spell Check
    • Change Text Direction
  • Frame context submenu. The submenu is labeled as This Frame.
    • Show Only This Frame
    • Open Frame in New Tab
    • Open Frame in New Window
    • Reload Frame
    • Bookmark This Frame
    • Save Frame As...
    • Send Frame...
    • Print Frame
    • Character Encoding...
    • Frame Properties

Implemented menu items. The following items currently appear in context menus, depending on (of course) the context. They should behave as labeled/expected. This list current as of what I've seen in recent builds, so these might change. As noted above, the actual functionality of many applications accessed via context menus is covered by other components. That is, XP Menus (or even XPApps) is not the correct component for such problems. Below I've denoted the Bugzilla components which should be used for application problems. All are in the Browser product unless otherwise noted.

  • Back. Application bugs go into History: Session.
  • Forward. Application bugs go into History: Session.
  • Reload. Application bugs go into Networking.
  • Stop. Application bugs go into Networking.
  • Cut. Application bugs go into Editor: Composer.
  • Copy. Application bugs go into Editor: Composer.
  • Paste. Application bugs go into Editor: Composer.
  • Select All. Application bugs go into Editor: Composer.
  • Web Search for "<selected text>" Application bugs go into Search.
  • Bookmark this Page. Application bugs go into Bookmarks.
  • Save Page As... Application bugs go into File Handling or Networking (depends on where the failure occurs).
  • Send Page... Application bugs go into the Mail Window Front End component of the MailNews product.
  • Bookmark this Link. Application bugs go into Bookmarks.
  • Save Link Target As... Application bugs go into File Handling or Networking (depends on where the failure occurs).
  • Copy Link Location. Application bugs go into Editor: Composer.
  • Copy Email Location. Application bugs go into Editor: Composer.
  • Open in New Window. Application bugs go into XP Apps: GUI Features.
  • Open in New Tab. Application bugs go into Tabbed Browser.
  • View Image. Application bugs go into ImageLib.
  • Save Image As... Application bugs go into File Handling or Networking (depends on where the failure occurs).
  • Copy Image Location. Application bugs go into Editor: Composer.
  • Send Image... Application bugs go into the Mail Window Front End component of the MailNews product.
  • Win32 only. Create Desktop Shortcut. Application bugs go into XP Apps.
  • Win32 only. Set as Wallpaper. Application bugs go into XP Apps.
  • View Background Image. Application bugs go into ImageLib.
  • View Page Source. Application bugs go into XP Apps: GUI Features.
  • View Page Info. Application bugs go into XP Apps: GUI Features.
  • View Selection Source. Bring up the source window displaying only the selection.
  • Properties. Application bugs go into XP Apps: GUI Features.
  • This Frame flyout:
    • Show Only this Frame. Application bugs go into XP Apps: GUI Features.
    • Open Frame in New Tab. Application bugs go into Tabbed Browser.
    • Open Frame in New Window. Application bugs go into XP Apps: GUI Features.
    • Reload Frame. Application bugs go into Networking.
    • Bookmark this Frame. Application bugs go into Bookmarks.
    • Save Frame As... Application bugs go into File Handling or Networking (depends on where the failure occurs).
    • Send Page... Application bugs go into the Mail Window Front End component of the MailNews product.
    • View Frame Source. Application bugs go into XP Apps: GUI Features.
    • View Frame Info. Application bugs go into XP Apps: GUI Features.

Unimplmented menu items. The following are proposed in the current spec, but are not yet implemented (so are not testable).

  • Show Menu Bar. Bug 137004. Available when the menu bar is absent or collapsed.
  • Open Link. Bug 137007. Default action for link context menus.
  • Send Link... Bug 137007. Sends link target address, but not the page file itself.
  • Compose Message... Bug 137010. Opens a mail compose window with the mailto: address as the addressee.
  • Add to Address Book... Bug 137010. Opens an address book card to add the selected mailto: address.
  • Send to Buddy... Sends selection via Instant Messenger.
  • View Newsgroup. Bug 137013. Opens news to the given newsgroup.
  • Copy Newsgroup Address. Bug 137013. Copies the news: link address.
  • Copy Image. Bug 135300. Copies the focused image to disk.
  • Redo. Repeat last editing command...don't think I've seen this appear...
  • Spell Check... If a spell checker were installed, this would be present.
  • Character Encoding... Should be off for English/US users, toggled via the toplevel View menu...
  • Highlight Selection. Bug 105580. Would bring up a color picker to allow user to highlight a selection in a chosen color.
  • Search Dictionary for "<selection>". Bug 105580. Perform a dictionary lookup for the selection.
  • Send Quoted Selection... Bug 105580. Bring up mail compose window with selection quoted in its composition area.
  • Change Text Direction. Switches the direction of the selection's text (left-to-right to right-to-left, or vice versa).
  • Page Properties, Link Properties, Image Properties, Frame Properties. At present, only a single Properties item is implemented, and displays the property info for the focused page, image, link or linked image.
  • Print Frame. Bug 137014. Print the active frame.

Stress, boundary & negative tests, etc.

When time permits, test the following areas.

  • Image as mailto: link context menu.
  • Text as news: link context menu.
  • Image as news: link context menu.
  • Context menus in file:///, HTTP and FTP listings, whether in HTML or XUL (outliner) format (file, folder, neither selected).
  • Additional context menus for selections.
  • Additional context menus for frames (incl selection, forms).
  • Long context menus: length/tallness of menu in a small browser window.
  • Long menu captions: width of context menu in a small browser window.
  • Behavior of context menus when browser is near screen border.
  • Context menus for HTML form controls, eg, droplists, input fields.
  • Context menus for other browser widgets, eg, items within toolbars, scrollbars.
  • Rapid clicking or dragging.
  • Extended duration of holding down mouse button.
  • Different monitor resolutions.
  • Effects of different themes (Linux, Windows), eg, the High Contrast theme on Windows.
  • Customizing Mac OS menu appearance by changing the desktop font and theme from the appropriate Appearance control panel (Mac OS 8/9) or Personal system preference (Mac OS X).
  • Customizing Linux menu appearance by changing the desktop/window manager theme and/or font.
  • Using multiple monitors. Or, in the case of Linux/unix, multiple virtual desktops.

Ad hoc

Ad hoc testing is covered by users in the Internet community, as well as casual use.

Regression

Due to time constraints, regression testing will encompass:

  • Verification of Resolved (Fixed ones get priority) bugs as they come in.
  • Periodic verification (eg, milestone deadlines) of Big Issues to make sure they're still fixed. This would go hand in hand with the usual acceptance testing that occurs during those periods.
  • Ad hoc testing with daily builds.