Some areas that are still causing problems within Amaya 3.2
(July 3, 2000) from my viewpoint [Windows 95 and display limited
to 640x480 @ 256 color] are as follows (arranged editor issues first):

Geometry Manager
1] Checking for video size and positioning windows inside the frame
   requires more work.  Windows that open to right side (such as
   View Source) are off the right edge when small screen (eg 640x480)
   are used.  Other examples are 'alternate' view and 'structure'.
2] When a window is resized or moved and the geometry manager is 
   asked to save it, a restart of Amaya loses the 'new' size/position
   ie. the save has not been done. An example is:
   Views -- Show Source
            drag to a new position
            Special - Preferences - Save geometry
            selecting special loses display of source :-( oops !!
            saving and then restarting and doing Show Source will 
            exhibit that the new position hasn't been saved.

Color Selection
3] Many color-picker selected colors do not look like the ones
   displayed in the picker swatches. This is 256 mode related!!

Table Display
4] Table frames are thin lines which can be covered up by the
   cell contents. An example of this is 
   'http://www.cgocable.net/~jrussel/color16.htm'
5] Div element was used with attribute align="center" on a table
   but the table not drawn centered. An example of this is
   'http://www.cgocable.net/~jrussel/color16.htm'
6] Tables become confused if stacked more than two levels down.
   An example is 'http://www.bahnhof.se/~chimbis/tocb/links'
   where text is printed outside their associated box.
7] The above example also indicates an inconsistence. The document
   can be viewed on line but if a copy is taken off line, it requires
   an extension of HTML (or htm) to be viewed. If the name used is
   links. without an extension only the source is displayed.
8] Errors in table math that are editor detectable, should be
   flagged to user.

Other Display Problems
9]  After scrolling to bottom of document, scrolling up to top
    overscrolls on many docs.  Examples of this are 
    'http://www.cgocable.net/~jrussel/access.htm' and
    'http://www.cgocable.net/~jrussel/mathsci.htm'
    And scrolling down overscrolls on some documents such as
    'http://www.cgocable.net/~jrussel/home.htm'
10] Images are not floated correctly although this is part of
    HTML 4 specification.
11] Image elements placed directly after a header element closer
    does not align correctly with margin settings.
12] Horizontal rules have a hook on the left edge. Either the rule
    isn't being drawn to the correct thickness or first char isn't
    in correct proportion to rest of rule.

Screen Scroll Control
13] The scroll bars can't be pulled to the very bottom or right edge.
    No information is lost but this is untidy.

Compose Multi-key function
14] Creating a soft hyphen adds a &173; to the document which
    will not pass some validators.  Should use ­ instead.

Documentation
15] Standard shortcut nomenclature should be used in menus.
    For example Alt + P  instead of Alt p    and
    Ctrl + Enter  instead of Ctrl Return
    

Some enhancements that are desirable for a future release of Amaya are:

Internationalization
1] Offer parallel files in supported languages for all help files.
2] Allow language dialog selection to also chose help file language.

Geometry Manager
3] Automatically save user positioning/sizing state on exit.
   A bonus would be a Reset Window state to the original menu item
   in the Special - Preferences menu.
4] Documentation of location of geometry settings file would help
   in cases of user having to fix poorly positioned windows.

Keyboard Shortcuts
5] Either a menu function or an external utility should be provided
   to find the keystroke action number or logical name for
   nonstandard keyboards. 
6] The complete keyboard naming convention should be documented
   as well as the priorities for conflict resolution.
7] Keyboard associations are needed for the middle set
   of the keypad [i.e. arrows, home, page up, etc.]
   Appropriate settings should be set up and then documented 
   in the help pages.  Some settings may be:
   page up/down - move one screenful in appropriate direction
   alt-page up/down - move to beginning/end of screen display
   arrow key    - move one character/line in correct direction
   ctrl-arrow   - move one word 
   alt-arrow    - move one screenful in appropriate direction
   home         - move to beginning of line
   end          - move to end of line
   alt-home     - move to beginning of file
   alt-end      - move to end of file

Browser Issues
8]  Complete implementation of the HTML 4.0 specification.
    This includes floating image elements!
9]  Complete implementation of the CSS1 style functions.
10] Redisplay time should be optimized or image height default increased
    to prevent strobing on directory pages with images. A set of images
    causes a series of redisplay of pages. An example of this is
    http://www.neta.com/~cherry/mathml/  

Graphical User Interface
11] Retain a history of recent URLS in a scrollable URL address box.
12] A treed bookmarks structure should be built into the toolbar or menu
    system.  One should be able to edit all properties of this bookmark.
    This will add greatly to the BROWSER side of Amaya.
13] If a file is taking a long time to download or to render,
    there should be a flasher or gauge to reinforce the fact that
    activity is taking place and that nothing has 'hung-up' or crashed.
14] Moving over one of the hyperlink areas should indicate that 
    the zone is active! One can't assume that they will be of a
    different color than surrounding text or underlined. 
    One possible way of enabling this kind of feedback in a user
    preferred manner is by having a Special -- General
    (or its own subitem) dialog box with checkboxes
    (to allow multiple choices) for:
    a] hover type display (with optional color choice)
    b] show selected address in status line
    c] change cursor to hand or different icon
    Of course no checked off boxes allow action to be as it is now.
    This allows the user flexibility in choosing the feedback method.
    Perhaps a checkbox could also be included for underlined
    hyperlinks even though it is now the custom to use the default
    stylesheet for this.

Browser Capabilities
15] Framesets are currently not supported.  Since many web sites
    offer them as appropriate solutions for menuing, Amaya should
    offer basic browser capabilities to view as many sites as possible.
16] GIF transparency should be supported as sites often use it
    to provide margins and watermarks.  Is there some way of checking
    Amaya .gif rendering for this.
17] Animated GIFs are not supported even though they are a common
    format on the Internet.  Although other formats may be technically
    superior, democracy should rule in favor of supporting this format.

Documentation
18] On the Help menu item a selection for Contents or Index should be
    provided.  This selection would point at manual.html which is a
    good table of conents!
19] More work is needed in the help files to ease the new users into
    Amaya.  Documentation is detailed well for the advanced users but
    is awkward for people who are new to Amaya.
20] Documentation should include a page of features NOT included
    within Amaya that other browsers normally have. A brief mention
    of the implementation decision will help users understand why it
    isn't there. This could be either on the web site or as part of
    the delivered docs.