Add an example that renders a simple fractal

This works at resolutions where simplification is significantly reducing the number of points in the line.  At high resolutions, navigation becomes unresponsive.  Limiting draw instructions to a replay group's extent will fix this.
Keep track of max extent for replay
Determining coordinate relationship to extent
Testing segment intersection with extent

If needed, this function can be modified to take two additional coorinates that will be set to the intersection points.
Skip coordinates that don't affect the rendered extent

Segments that intersect the replay group's extent are drawn.  Any segment that represents a change in coordinate-extent relationship is drawn.  This maintains the left/right relationship (or cross product) between points in the rendered extent and every rendered segment.

Still left undone: clip the replay group's rendering to the max extent.
Clip to max extent
Function for applying a 2d transform to an extent
Add out-of-order shared Style and StyleMap test
Refactor KML style handling to handle shared Styles and StyleMaps
Be more tolerant of out-of-spec KML files
Read Icon hrefs as URIs
Explicit box model definition for box model dependent sizing

The zoom in/out tooltips are clipped when a css reset sets the
box-sizing to anything other than content-box. This breaks the
sizing of these tooltips, because they rely on content-box
sizing. This issue can e.g. be seen when using a bootstrap 3.x
bootstrap.css
Make renderSync always force a render
Don't use withFrozenRendering in ol.interaction.Interaction.rotateWithoutConstraints
Don't use withFrozenRendering in ol.interaction.Interaction.zoomWithoutConstraints
Don't use withFrozenRendering in ol.interaction.DragRotateAndZoom#handleDragEnd
Don't use withFrozenRendering in ol.interaction.Select#handleMapBrowserEvent
Remove ol.Map#withFrozenRendering
Remove unused ol.FeatureOverlay require
Merge pull request #1780 from fredj/unused-require

Remove unused ol.FeatureOverlay require