jQuery Mobile Team Meeting – Jan 22 2015

• Ticket Triage:
  • 282 tickets (-3)
  • 26 pull requests (-10)

link 1.5.0

• 2 branches based on latest updates from ui
  • Ready to start on classes implementations again
• Classes
  • Scott doing his first review right now getting really close
• Button
  • CSS update (button, checkboxradio, controlgroup)
    • In ui-1-12 now
• RTL
  • organizing a call
    • Reaching out a few good responses so far
• Auto Init
  • New module details
    • enhancer branch (no update)
• data- attribute name space
  • backcompat
    • no update
• Perf bug
  • https://github.com/jquery/jquery-mobile/issues/1560
    • PR in progress
    • https://github.com/jquery/jquery-mobile/pull/7927
  • Should we add a way of removing a handler? We could track handlers via $.data( "mobile-events" ) like we do for swipe. Right now, we have to write code into callbacks to do nothing if they have become stale. What should the API be if we do want it? .animationComplete( callback, type, fallbackTime, remove )?
    • Agreed against adding an argument to .animationComplete, and use $.fn.removeAnimationComplete( callback ) instead
    • https://github.com/jquery/jquery-mobile/issues/7935
  • Testing the build
    • https://github.com/jquery/jquery-mobile/pull/7926#issuecomment-71067473
    • Should we? No :-)