This is a list of browser bugs found during testing of the library:

NetFront 3.4 Bugs:

* Displays legend element as inline and not as per other browsers.

  Rough fix through tweaking style sheet to use:

   legend { background-color: rgb(255,255,255);
     font-size: 80%; font-style: italic;
     padding: 3px; margin-left: 1em;
     position: absolute;
     display: block;
     width: auto;
     margin-top: -1.5em;
   }

  Clips first line of content, and haven't yet found workaround.

* input element ignores CSS properties for text-align,
  background-color, vertical-align. This effects text boxes,
  check boxes and radio buttons. The inability to change the
  color when the field is selected is a particular problem

* Doesn't show tooltips when hovering over elements with
  title attribute.

* Doesn't support > etc. within attribute values

  Work around is to test UA for this bug and fix up accordingly.

* Updating select element's options doesn't update displayed list
  although it works fine as far updating the DOM goes.

NetFront 3.3 has weaker support for the DOM and fails on
dates, range controls and repeating fieldsets. It also
has a clumsy default rendering for select elements.

Can ACCESS provide details on missing DOM features to enable
me to find work arounds?

Opera Mobile has different faults:

* doesn't give scripts access to non-standard values for
  type attribute on input element

  Work around is to use datatype attribute instead.

* CSS believes display width is much larger than device screen

* Can't navigate to links on positioned div when there is
  text immediately below on document body

* In fit to width mode, Opera ignores display:none and
  visibility:hidden when set from author's style sheet

Opera Mini is pretty cool but isn't really appropriate as
a platform for rich web applications where support for
client-side scripting is a critical component.

Opera 9 (desktop) doesn't give scripts access to non-standard
values for type and required attributes on input element. The
work around is to instead use datatype and needed for the attribute
names respectively.

Opera 9 and Safari recognize type="range" and render the
control as a slider. This is taken advantage of by the library.
Neither of these browsers provide a numeric indication of
the values available via the slider.

Opera 9's data picker doesn't allow you to type a date which
is more convenient if you aren't able to use mouse or other
pointer device.

Internet Explorer delays onchanged events until radio buttons
and checkboxes lose the focus, unlike other browsers. A work
around is to handle onclicked events. IE also paints the
background for fieldset elements above the border unlike any
other browsers.

Konqueror 3.5 doesn't support cloneNode(). This isn't a problem
except when exporting the data to XML.