Catch and log unhandled exceptions in async tests
Remove and ignore files created by tests
Add clarification comment on how the meta element behaves (and test)
Don't stop parsing an ODF unless the container state becomes invalid

An error is not necessarily fatal unless the handler sets the state to
invalid as a result of the missing data. In addition, when the state
is set to invalid, log the component that failed to load and (if
defined) the error that has occurred.
Handle documents with no office:settings element

Settings.xml and office:settings are both optional according to the
ODF specifications. WebODF must be able to handle loading and saving
files with or without this setting.
Ensure all ODF elements are recreated when setting a new root element
Merge pull request #466 from peitschie/optional-settings

Handle documents with no office:settings element
Noting agreed coding rules for types
Merge pull request #420 from kossebau/codingPolicy

Noting agreed coding rules for types
Allow the event trap to receive focus in read-only mode

A disabled element is not able to become the document's activeElement.
The better way of setting the event trap to non-editable is through
the readOnly flag. This still allows focus to be passed to the trap.

During a mouse down event, the event trap should be disabled however
to ensure it doesn't capture the window selection.
Re-enable the event trap if a context menu is displayed

A contextmenu event is fired instead of a mouseup event, therefore
both these events need to be listened for to ensure the event trap
becomes re-enabled.