YUI3 button click event is acting like a submit type instead of a button type
===

I am using `ASP.NET MVC 3` with the `Yahoo API version 3`.  I am trying to get my `YUI3 button` to redirect to another page when I click on it, this button is my cancel button.  The cancel button is a plain button type, but it is being treated like a submit button.  It is not redirecting to the correct page, but acting like a submit button and it kicks off my page validation like what the submit button would do.

I thought that it might be with my HTML but I did validate it.  It validated 100% correct.  So I then stripped down the whole page to a bare minimum but the cancel button is still working like a submit button.  Here is my HTML markup:

    @{
        Layout = null;
    }
    
    <!DOCTYPE html>
    
    <html>
         <head>
              <title>Create2</title>
         </head>
         
         <body class="yui3-skin-sam">
    
              <h1>Test submit</h1>
    
              @using (Html.BeginForm())
              {
                   <button id="SaveButton" type="submit">Save</button>
                   <button id="CancelButton" type="button">Cancel</button>
              }
    
              <script src="http://yui.yahooapis.com/3.6.0pr4/build/yui/yui-min.js"></script>
              <script>
                   YUI().use('button', function (Y) {
                        var saveButton = new Y.Button({
                             srcNode: '#SaveButton'
                        }).render();
    
                        var cancelButton = new Y.Button({
                             srcNode: '#CancelButton',
                             on: {
                                  'click': function (e) {
                                       Y.config.win.location = '/Administration/Department/List';
                                  }
                             }
                        }).render();
                   });
              </script>
    
         </body>
    </html>

I'm not sure what I am doing wrong here?  Is this maybe a bug in their API?  I am testing on IE8 and on the latest version of FireFox.