flyout control metro2.0
Settings flyout metro refresh
Merge pull request #679 from caseyfaber/flyout-control

Flyout control design refresh
Merge pull request #692 from caseyfaber/settings

Back button and settings flyout design refresh
Fix #583: Unit test failure: Security_markSupported

There was a bug in the test. Chrome lowercases attributes set with
setAttribute while IE does not. The test was relying on setAttribute not
changing the casing of the attribute.

The fix was to change the test to use an all lowercase attribute. Other
than that, the attribute's name doesn't matter.
Fixes #693

Feature detect execUnsafeLocalFunction.
Set up build for Store Package.
Include _Telemetry module in Utilities.
Ignore .tscache folder in sublime project.
Fix #683: SplitView: Nested animations

SplitView's resize animation helper, transformWithTransition, needs to be
more strict when listening to onTransitionEnd. It needs verify that the
element and transition property match before completing the animation
promise.

Otherwise, the promise may complete prematurely due to animations on
descendants or animations on other properties.
Fix #683: SplitView: Position relative descendants

Currently, if you put an element with position: relative/absolute inside
of the SplitView's content, this element will end up being rendered on top
of the overlayed pane when it opens. For example, you can see this by
putting a SearchBox inside of the SplitView's content.

To avoid this, the SplitView's pane and content are each given a z-index
so that:
  1. They are each a stacking context so their descendants can't escape
     them.
  2. The pane element is always rendered on top of the content element.
Fix BackButton test bug.
With the Style changes for Backbutton, the BackButton no longer hides itself while disabled.
In IE "focus" and "blur" event listeners fire asynchronously. "focusin" and "focusout" fire synchronously. In other browsers "focus", "blur", and "focusout/focusin(where available)" all fire synchronously.
Because Firefox doesn't support "focusin" and "focusout" natively, our _ElementUtilities._addEventListener WinJS code today will fire synthetic "focusin" & "focusout".

Because we anchor these to the native focus and blur events, we fire our synthetic events asynchronously in IE and syncronously in every other browser. This change has us anchor our synthetic events to the native "focusin" and "focusout" where its supported (everywhere but firefox), otherwise "focus" and "blur".  The net effect is that we should get synchronous synthetic "focusin" and "focusout" events for every browser we support.
Merge branch 'master' into AmazingJaze/CascadingFlyout