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 plans > Copy & Paste/Clipboard Integration

Feature Test Specification

Seamonkey (6.0): Browser Copy & Paste/Clipboard Integration

Originally written by: <Eli Goldberg>
Currently maintained by: <Terri Preston>
History
Date Change Description Revision Updated By
<4/19/99> Skeleton test plan 0.5 Eli
<8/11/99> First Draft, for review .9 Eli
<9/1/99> Actual Test Plan 1.0 Eli
<3/17/00> Maintenance update 1.1 Eli
<7/28/00> Maintenance update 1.2 Eli
<8/21/00> Maintenance update 1.3 Blake
<12/26/00> Maintenance update 1.4 Terri

References:

UI and/or Functional Specifications:

  • Mac OS 8.5 Technote:Part V - (e.g. how the Macintosh Finder represents URLs in its Clipboard)
  • XPToolkit Clipboard - A functional specification in plain English detailing which Copy/Paste behaviorswill be supported if they don't presently exist, as well as how they should function.
  • Windows Transfer Operations Guidelines - Guidelines for how transfer operations (e.g. move, copy, paste) should function on Windows.

In Seamonkey, users will be able to copy and paste rich and plain content, including text and stylized (HTML) text. Seamonkey represents this content internally using the XIF format (undocumented).

Will-Test Areas:

  • Copy and Paste within the Navigator browser, and from Navigator to othercomponents of the Netscape client suite (e.g. Editor and Mail/News.)
  • Copy and Paste behavior for different media types (including pasting into containersthat do not support the media types in question, e.g. plain-text editor)

Won't Test Areas:

  • Copy and Paste from other components (e.g. Ender and Mail/News)
  • Copy and Paste of rich text from Navigator to other applications. (not expectedto be supported)

Major Issues:

  • Copy/Paste (or Drag/Drop) of images will not be supported in the initial Seamonkeyrelease. Functionality has been present since Navigator 1.0 (Mac OS), and may bea user expectation from a web browser. (bug #21747)
  • XUL textfields still don't have context menus to aid in clipboard operations.
  1. Functional test cases
    1. Copying Styled Text (from browser window)
      • Formatting/spacing conversion should result in "non-annoying" output(e.g. copying out of indented web pages into a text editor should result in textthat isn't oddly formatted.) This is potentially a very complicated testing area (tables, line breaks, paragraphs,CSS formatted text, etc), and Akkana is open to formally inviting testing from theopen source community, given the importance of the functionality.
      • Determine whether JavaScript output can be copy and pasted appropriately.
    2. Copying/cutting plain text
      • Determine whether HTML entities can be properly copied and pasted.
      • Determine whether text can be copied and pasted from an Ender Lite widget (e.g.form or application text fields)
    3. Copying Styled Text with images
      • Images should not be included in clipboard, but the HTML version of the Clipboardcontent should include an IMG link to the image source. (relative links will notbe converted to absolute links)
      • Images should be ignored entirely when pasted as plain text --- no ALT tags.
    4. Copying Text from dialog boxes
      1. Text should be copyable and pasteable from text fields within dialogs, includingthrough all platform-specific means of text copy/paste.
  2. Negative/Stress/Boundary
    1. Confirm Copy/Cut not viable option in non-selectable UI objects
      1. within chrome
      2. widgets within web pages (e.g. buttons, scroll bars, etc)
    2. Overflow
      1. Copying/pasting extremely large text blocks (e.g. 1 MB)
      2. Copying/pasting extremely complicated rich text (e.g. massively nested tables)
    3. User Interface stuff
      1. Determine whether copy/paste is properly grayed out when inapplicable (e.g. clickinto blank areas of page, such as within a table, and confirm that menu items aregrayed out when nothing is selected)
      2. Determine whether contextual menu-invoked Copy/paste also works.
    4. Platform-specific stuff
      1. Win32: Confirm that valid documents can be pasted onto the applicationicon. (OS level operation, no test case written.)
  3. Test cases for future versions
    1. Functional
      1. Image Cut/Copy
        • ... of both native (e.g. GIF & JPEG) as well as non-native (when implmented) image formats. (should be irrelevant; at least, on Mac, converted to PICT before going to Clipboard.)
        • Pasting image into text editor should degrade into URL. (or, at least, we should be providing content in the clipboard in order to allow applications to determine the url; e.g. 'url ' file type on Mac OS.)
        • Confirm as formality that well-behaved applications accept our paste output, and degrade it appropriately. (e.g. pasting an image into a plain-text editor such as BBEdit.?)
    2. Stress
      1. Copying/pasting extremely large (or atypical; e.g. non-native, when implemented)images.

For future exploration:

  1. Should copy/paste of linked text behave any differently from copy/paste of plain text? ('url ' in addition to 'text'?)
  2. Clipboard should contain all of the proper text types upon a copy. What are they? (Guessing Mac: HTML, Rich Text, Plain Text. Windows & UNIX? must find out.)