1.4 planning

General

Support using widgets like toolbars, popups, panels outside of a page
Support AJAX loading in multi-page docs
Support anchors both inside a page (#bar) and across pages (foo.com#bar)
Revisit question of whether we should delete the contents of the original page contents (option)
Support anchors and deep links to content like 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
Show how to use the server to serve up a full page vs. just the contents - how to use headers to decide what type of request it is or consider adding a query param option that could be set globally to communicate that it's an AJAX request

Add performance benchmarks so we have a clear baseline and avoid regressions
Work with core on what modules we might want sliced off as modules, maybe ship with a custom build of core that is lighter
Less markup generation/decoration for enhancement

Widget factory review for conformance. See https://github.com/jquery/jquery-mobile/wiki/Widget-Review
Ideally, have a common core with UI that is just the minimal amount of code needed to bootstrap a widget from either library; move the nav/autoinit config, key handling, etc. out into separate modules.
Use a class config mechanism to allow UI and Mobile to map to different theme frameworks
Make it possible (and easy) to apply jQuery Mobile themes to jQuery UI widgets

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 work 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
Re-consider using a CSS pre-processor?
Make is easier to target elements that are wrapped (prefixed class/id)