prefix "customScrollbars" element classnames with "webodf-"
Remove no longer needed "overflow: hidden" rule for the toolbar
prefix "selectionOverlay" element classname with "webodf-"
prefix "draggable" element classname with "webodf-"
prefix "annotationHighlight" element classname with "webodf-"
Merge pull request #460 from kossebau/namespaceMoreWOStuff

Namespace more of our stuff
Help pullbox backends by telling them the mimetype of the WSER call payload
Merge pull request #459 from kossebau/mimetypeForWSERPayload

Help pullbox backends by telling them the mimetype of the WSER call payload
Remove unused invite button
Merge pull request #453 from kossebau/removeUnusedInviteButton

Remove unused invite button code
define size of paragraphstyle dialog internally, not by general css rule on .dijitDialogPaneContent
Merge pull request #452 from kossebau/noGeneralHardcodedDojoDialogSize

define size of paragraphstyle dialog internally, not by general css rule on .dijitDialogPaneContent
Toggle hyperlink active state via classes rather than custom XML attrs

Toggling a custom attribute on a custom XML element doesn't properly
update the visual state on some browsers (e.g., WebKit on OSX). Using
CSS classes instead seems to be better handled in these browsers,
correctly updating the mouse cursor icon on the fly.
Clean up API dox
Normalize keyboard events involving modifiers

For keys that are also modifiers (e.g., Ctrl), different browsers +
platforms may report the modifier flag as leading or lagging the
keypress event. For example, pressing the ctrl key in FF on Linux will
report (ctrlKey:false)in the keydown event, while Chrome on Linux will
report (ctrlKey:true) in the keydown event. For these specific cases,
normalize the modifier flag so it is always the set to true.

Fixes issue #322.
Merge pull request #462 from peitschie/active-link-toggle

Toggle hyperlink active state via classes rather than custom XML attrs
First version of a new convenience class for dealing with ODF styling information.
The class parses the styling information and allows accessing it like e.g.
 fontWeight = style.getTextStyle("T1").text.fontWeight;
If T1 does not define, fontWeight is retrieved from the parent style and
eventually the document default and the implementation default.
This is achieved by setting the object prototype to the style parent.
some work
More complete implementation of style resolution.