Navigation Api

jQuery Mobile Navigation API

Current Goals:

• Separate out transitions into their own module
• Switch to js based transitions
• Make it possible to have non linkable history entries
• Add navigation hooks for widgets
  • click handler calls $( link.attr( "href" )[ link.attr( "data-rel" ) ]( "open" ); when handling an anchor that has data-rel="widgetname"
• Separate push state and hash change
• Simplify and review api
• Add support for multiple page containers
• Create separate auto enhancement module
• fall back to standard hash handling if you fail to find the internal widget to open() (comply with spec)
• implement linking to ids ( deep linking ) for scrolling to a position the same as the browsers do already
• Separate out click handler

Questions:

• If the initial hash contains the id of a widget should we open that widget?

  Answer(s):

  • @gabrielschulhof: IMO yes, because that means deep linking was allowed during the initial opening of the widget.