1.4 planning

Flexibility

• Use widgets like toolbars, popups, panels outside of a page
• Consider adding a query param option that could be set globally to communicate that it's an AJAX request (Build demos showing how to use the server to serve up a full page vs. just the contents)
• Revisit question of whether we should delete the contents of the original page contents (option)
• Use anchors and deep links simply - foo.com#bar
• Be able to update hash w/o manipulating history (pushstate only)
• Ability to pass hashes through (pushstate only)
• Easier ways to wire in back button support for widgets like panels
• Support AJAX loading in multi-page docs

Performance

• Add performance benchmarks so we have a clear baseline and avoid regressions

API/widget factory consistency

See https://github.com/jquery/jquery-mobile/wiki/Widget-Review

Design cleanup

• Reduce markup decoration with JS, use more advanced CSS selectors
• Switch to SVG or font based icons
• Re-design the default theme, reduce # of swatches?
• Make structural styles wrok as a minimal baseline for people who don't want to use TR
• Use media queries (rather than JS) to shield css rules to non-enhanced browsers to simplify enhancement
• Improve the C-grade styling
• Make it possible (and easy) to apply jQuery Mobile themes to jQuery UI widgets
• Re-consider using a CSS pre-processor?