Permalink
Switch branches/tags
Commits on Oct 1, 2015
  1. Add MediaPlayer test page

    rigdern committed Oct 1, 2015
Commits on Sep 8, 2015
Commits on Sep 4, 2015
Commits on Sep 3, 2015
  1. Fix #1367: Can tab out of SplitView pane and close it

    When tabbing thru a SplitView pane that is open and the SplitView has
    openedDisplayMode:overlay, tabbing should carousel within the pane.
    
    In all other cases, tabbing at the boundaries of the pane should cause
    focus to exit the pane.
    rigdern committed Sep 3, 2015
Commits on Aug 28, 2015
Commits on Aug 17, 2015
  1. Fixes to publication process

    rigdern committed Aug 17, 2015
  2. 4.2.0

    rigdern committed Aug 17, 2015
  3. Fix #1176: Make ContentDialog's title a header

    ContentDialog's title is now marked as a header for consumption by screen
    readers.
    rigdern committed Aug 13, 2015
Commits on Aug 15, 2015
  1. Improve ContentDialog's response to the InputPane

    Fixes #1149 and #910
    
    When the input pane shows, the ContentDialog's response was to maintain
    its top/left position and to shrink its height as much as needed to avoid
    being occluded by the input pane. This behavior resulted in a bug where,
    if the dialog's top/left was close to the center of the screen, the dialog
    could become very short when it resized to get out of the way of the input
    pane (#1149).
    
    To fix this, the new way the ContentDialog responds to the input pane is:
      - If the dialog will not be occluded by the input pane, then the dialog
        maintains its current size and position.
      - If the dialog will be occluded by the input pane, the dialog lays
        itself out using its normal layout rules but it does so in the
        unoccluded portion of the window (visible document) rather than in the
        whole window.
    
    There was another bug (#910) where the ContentDialog would become
    horizontally off center if the window was resized while the input pane was
    showing. This is now fixed because the ContentDialog uses its normal
    layout rules even when the input pane is showing.
    
    Other changes:
      - Switiched from .focus() to .scrollIntoView() for keeping the focused
        element in view while resizing the dialog to get out of the input
        pane's way. The motivation for this change was that calling .focus()
        on document.activeElement no longer causes the element to scroll into
        view in Edge.
      - When the ContentDialog is shown, put focus on the root element of the
        dialog rather than on the first focusable element within the dialog's
        content area. The motivation for this change is that .scrollIntoView()
        is more aggressive about scrolling than .focus() was -- it scrolls the
        element to the top of its scroller even if that element was already in
        view. This results in a poor experience when showing the dialog and
        the first focusable element in the content area is a textfield -- the
        user will never have the chance to see the content at the top of the
        dialog because the dialog would immediately scroll it off screen.
        Order of events:
          - Dialog shows and puts focus on the first focusable element
            (assume it's a textfield) in the content area
          - Input pane shows
          - Dialog resizes
          - Dialog calls .scrollIntView() on the textfield to keep it in view
    	during the resize thus scrolling the dialog's topmost content off
    	the screen
    rigdern committed Aug 12, 2015
Commits on Aug 7, 2015
  1. Verify files have BOM during publish task

    This verification is designed to simulate part of the Windows App
    Certification Kit test.
    
    Protects us from regressing #1315 in the future.
    rigdern committed Aug 6, 2015
Commits on Aug 1, 2015
  1. Update URLs used in tests

    rigdern committed Aug 1, 2015
Commits on Jul 31, 2015
  1. Fix indentation

    rigdern committed Jul 31, 2015
  2. Automate release process

    You can now use a grunt task to:
      - Publish a release to GitHub
      - Publish to npm
      - Publish to bower
      - Publish to NuGet
    
    The command is:
      grunt publish
    
    This will print a message warning you about what is about to happen and
    showing you a checklist. Once you're sure you want to proceed, you run
    this command:
    
      grunt publish:force
    
    which actually publishes to all of the package managers.
    rigdern committed Jul 30, 2015
Commits on Jul 22, 2015
  1. Moved all getComputedStyle calls to _ElementUtilities._getComputedStyle

    Also added a jscs rule to warn us if we try to call getComputedStyle
    directly in the future.
    rigdern committed Jul 20, 2015
  2. Introduce _ElementUtilities._getComputedStyle helper

    Firefox's implementation of getComputedStyle returns null when called
    within an iframe that is display:none. This is a Firefox bug. Most of the
    WinJS code expects getComputedStyle to return an object whose keys map to
    strings.
    
    To work around this Firfeox bug, introduced a helper
    (_ElementUtilities._getComputedStyle). It always returns an object whose
    keys map to strings.
    
    Also fixed #1312 because it was breaking the unit test that this change
    was adding. Essentially, MessageEvent.source can be undefined in Chrome
    (when the iframe has already been removed from the DOM) so we have an
    extra if statement to protect against this case.
    rigdern committed Jul 18, 2015
Commits on Jul 20, 2015
  1. Fix #1307: Some pivot tests failing in Edge

    The problem was in the test code that generated pointer events. It was
    always using the MS-prefixed names of the pointer events but these no
    longer exist in Edge. The fix is to prefer the non-prefixed event names
    when they are available.
    rigdern committed Jul 20, 2015
Commits on Jul 18, 2015
  1. Update SplitView for high contrast

    Added an outline around the SplitView pane when it is opened in high
    contrast. It can't be done with a border or an outline because it can't
    take up any extra space and it needs to appear inside of the pane (rather
    than outside like an outline).
    rigdern committed Jul 10, 2015
Commits on Jul 15, 2015
  1. Merge pull request #1151 from KevinTCoughlin/fixes-1124-delete-css-or…

    …dering-tests
    
    Fixes 1124 - Remove CSSOrderingTests from test suite
    rigdern committed Jul 15, 2015
  2. Merge pull request #1257 from nobuoka/declaration-return-type

    Add return-type annotations on the winjs.d.ts file
    rigdern committed Jul 15, 2015
Commits on Jul 13, 2015
Commits on Jul 10, 2015
  1. 4.1.0

    rigdern committed Jul 10, 2015
  2. All build tasks should use package.json version number

    Tasks shouldn't have the version number hardcoded in them.
    rigdern committed Jul 10, 2015
  3. Import updated localized resjson files

    quc-Latn-GT is the new notation for qut-gt so qut-gt was deleted.
    rigdern committed Jul 9, 2015
  4. en-us resjson file: Remove BOM

    rigdern committed Jul 9, 2015
Commits on Jun 30, 2015
  1. Fix #1224: Hub doesn't leave room for App title

    In working on this fix, I found the Hub spacing didn't quite match the
    redlines in several places so I took the opportunity to fix those issues
    as well.
    rigdern committed Jun 25, 2015
Commits on Jun 26, 2015
Commits on Jun 17, 2015
Commits on Jun 12, 2015
  1. Make corrections to en-us resjson file

    - In the comment section, there should be an "=" sign after
      "{Locked" instead of a ":"
    - Many unicode characters don't match the symbols in the free text
      comments. They aren't needed so rather than trying to keep them in sync,
      we're removing the symbols in the free text comments.
    rigdern committed Jun 12, 2015
Commits on Jun 11, 2015
  1. 4.0.1

    rigdern committed Jun 11, 2015
Commits on Jun 5, 2015
  1. Fix #1202: Accent color sometimes not applied

    Some times none of the accent color rules work because they are generated
    with an accent color value of 'undefined'. This is due to a race condition
    in the accent color code: sometimes the accent color rules are generated
    before the accent color has been retrieved.
    
    The fix makes accent color retrieval synchronous. In addition to fixing
    this race condition, it also fixes an issue where the accent color could
    flash in. If it took a while to reach DOMContentLoaded, the user would
    initially see the page rendered without accent color and then after
    DOMContentLoaded, they'd see the page rendered with accent color. This is
    doesn't happen anymore beacuse color retrieval no longer waits on
    DOMContentLoaded.
    rigdern committed Jun 4, 2015