The Mozilla
Organization
At A Glance
Feedback
Get Involved
Newsgroups
License Terms
Newsbot
Developer Docs
Roadmap
Projects
Ports
Module Owners
Hacking
Get the Source
Build It
Testing
Download
Bugzilla
Bug Writing
Tools
View Source
Tree Status
New Checkins
Submit A Bug
FAQ
Search

Feature Test Specification

Seamonkey (5.0)
Browser Copy & Paste/Clipboard Integration

 
Written by: <Eli Goldberg>


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



References:

UI and/or Functional Specifications: 

XPToolkit Clipboard

(A functional specification in plain English detailing what Copy/Paste behaviors will be supported doesn't presently exist.)

Mac OS 8.5 Technote: Part V (e.g. how the Macintosh Finder represents URLs in its Clipboard)


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

Will-Test Areas:

  • Copy and Paste within the Navigator browser, and from Navigator to other components of the Netscape client suite (e.g. Editor and Mail/News.)
  • Copy and Paste of rich media from Navigator to and from different applications, on different platforms. (e.g. Microsoft Office, PageMill)
  • Copy and Paste behavior for different media types (including pasting into containers that 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)

Major Issues:

  • XPFE hasn't committed to supporting Copy/Paste (or Drag/Drop) of images. Functionality has been present since Navigator 1.0 (Mac OS), and is (in my opinion) a user expectation from a web browser.


  1. Functional test cases
    1. Copying Styled Text (both from browser window, and from a GFX/Ender text widget)
      • Formatting/spacing conversion should result in "non-annoying" output (e.g. copying out of indented web pages into a text editor should result in text that 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 the open source community, given the importance of the functionality.
      • 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.?)
      • Determine whether JavaScript output can be copy and pasted appropriately. (For test case, adapt highlight-js-text.)
      • Determine whether HTML entities can be properly copied and pasted. (For test case, adapt the entity chart; beppe would know where it is.)

    2. Copying Styled Text with images
      • Images should not be included in clipboard, but the HTML version of the Clipboard content should include an IMG link to the image source. (relative links will not be converted to absolute links)

    3. Image Cut/Copy
      • ...of both native (e.g. GIF & JPEG) as well as non-native (e.g. XBM) 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.)

  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. (extremely low priority --- unlikely to be broken) Confirm Paste not viable option in unwriteable UI objects
      1. try pasting into a dialog box

    3. Overflow
      1. Copying/pasting extremely large text blocks (e.g. 1 MB)
      2. Copying/pasting extremely large (or atypical; e.g. XBM) images.
      3. Copying/pasting extremely complicated rich text (e.g. massively nested tables)

    4. User Interface stuff
      1. Determine whether copy/paste is properly grayed out when inapplicable (e.g. click into blank areas of page, such as within a table, and confirm that menu items are grayed out when nothing is selected)
      2. Determine whether contextual menu-invoked Copy/paste also works, especially for images (where it's the sole means to access the functionality.)
    5. Platform-specific stuff
      1. Win32: Confirm that valid documents can be pasted onto the application icon.

Explore for M12:

1. Need a tool on each platform to view the clipboard content --- specifically, content types exist in the Clipboard.
Windows: dobjview.exe (but doesn't show content)
Mac: output may be equivalent to drag (Dragpeeker --- Pinkerton), or try Scrapbook.
Linux: ???


2. Should copy/paste of linked text behave any differently from copy/paste of plain text? ('url ' in addition to 'text'?)

3. 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.)

4. "Copying styled text" includes several forms of text conversion (to styled text [Mac OS], to plain text), etc, depending on what formats the application we paste into can receive. Expand upon possible issues in this text conversion.



Copyright 1999 Netscape Communications Corporation
Copyright © 1998-2000 The Mozilla Organization.
Last modified November 5, 1999.