1. 11 Nov, 2013 5 commits
  2. 09 Nov, 2013 1 commit
  3. 07 Nov, 2013 3 commits
  4. 10 Oct, 2013 5 commits
  5. 09 Oct, 2013 2 commits
    • Andy's avatar
      Added support for non-tab LI elements · d7bc2d7b
      Andy authored
      Potential fix for issue #33.  Created a 'baseItemSelector' that only
      selected items with have a child with the 'data-toggle' attribute set
      to "tab" and used that when referencing tabs.
      d7bc2d7b
    • Andy's avatar
      Made compatible with both bootstrap 2.3.2 and 3.0.0 · c868bc54
      Andy authored
      Attached to both the legacy 'shown' event and new 'shown.bs.tab'.
      Since only one or the other should exist. There should be no conflict.
      c868bc54
  6. 12 Aug, 2013 1 commit
  7. 11 Aug, 2013 1 commit
  8. 02 Aug, 2013 8 commits
  9. 10 Jul, 2013 3 commits
  10. 17 Jun, 2013 4 commits
  11. 10 Jun, 2013 1 commit
  12. 23 May, 2013 1 commit
  13. 28 Apr, 2013 3 commits
  14. 14 Apr, 2013 1 commit
    • Dave Shoreman's avatar
      Only look for direct children · c1ec6b52
      Dave Shoreman authored
      By only checking for ```<ul>```s that are a direct child of the root wizard element (and only tabs that are part of that navigation) we're able to nest a second tab group within the main ```#rootwizard``` div.
      
      This may or may not fix nested wizards, I haven't tested that. However it *does* fix [the scenario](https://github.com/VinceG/twitter-bootstrap-wizard/issues/11#issuecomment-16353032) I commented about in issue #11.
      
      Like I mentioned in my comment on that issue I'm not entirely sure how closely related a "wizard" is to a "vanilla" bootstrap tab group (at least when it comes to nesting them), but this could well do the trick.
      c1ec6b52
  15. 01 Apr, 2013 1 commit