Known bugs
----------

- example_2 (or is it XmHTML itself, can't figure this one out clearly) chokes
  on progressive image load on a HTML document with frames in it (07/17/97).

- scrolling a document with a large form in it doesn't always work correctly
  (try the fully expanded search page at Hotbot). You can restore the screen
  by hitting the PageUp or PageDown keys.

- framesets nested more than two levels deep are not always displayed correct.
  (See examples/test-pages/frame5.html)

- frames are not always placed at the border of their parent HTML widget;
  this goes away by resizing the parent HTML widget a bit.

- frames are not resizeable.

- scrolling text downwards example_2.c is run with the -root option does not
  erase the text at the bottom line properly.

- a very strange and funny bug: placing the word March as the first word
  in a <dt> doesn't get it's spacing correct. IMHO, this has something to
  do with a bug in the adobe roman font at pointsize 14: the width of a 
  capital M is incorrect?
  The workaround is to use a default font size other than 14.

- when in <pre></pre>, using a different font messes up the text alignment.

- <div align=whatever> around a <pre></pre> block doesn't work.

- The stuff for auto-sizing (XmNresizeWidth & XmNresizeHeight) is far from
  being optimal. When setting text in a widget, Layout() is called at least
  twice: once for the text, and again by Resize() when the widget is resized.
  The current check on pref_height does not work since Resize() resets it to 0.
  (which is required if one wants to be able to resize the widget).

  Partially Fixed, 01/10/97; kdh
  Almost fixed on 04/27/97, kdh.
