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) https://github.com/jquery/jquery-mobile/issues/3249
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

Widget review

JS directory structure
remove jquery.mobile.* prefix
move things into sub-directories
move jquery.js out of js/ either to a vendor dir or as an npm dependency
Make all extensions proper extensions
table: reflow
table: column toggle
custom select
listview autodividers
Make sure everything that should be a widget is: listview filter (widget vs. object), page sections
Break out JS Objects
transition handler

UI/Mobile shared core

Widget factory compliance & cleanup

Check latest UI version (1.10.1 now)
Add widget method
Add destroy method
Add option method
Check enable method
Check disable method - use _setOption?
Works outside of a page
Works in isolation (ex: is it dependent on page lifecycle)
Remove visual options like corners, shadows
Change from ui-disabled to ui-state-disabled to leverage WF, remove our original disabled code
Use on / off
Find where we're binding to document
Touch events have no teardown (swipe, tap, etc.)
Navigate event teardown
Update unit tests: more granular methods, less integration tests
Review open issues per widget when re-factoring to see if we can fix as we go

Make AJAX Nav (Content container) a standalone widget

100% decouple nav to be optional so people can use mobile like UI - collection of widgets
Move all nav options from core to here

Mobile widget - add registry

Simplify the default theme as well as its CSS (taking lessons from the Android Design Guidelines and the KISS principle)
Reduce # of swatches?
Seeing as how more and more people are using their own designs as opposed to our themes - remove all theme-related styles from the structural styles (i.e. padding on .ui-panel-inner and .ui-content, margin and font size on .ui-title etc.)
Make it easier to change the width of the sidebar
Theme sub-team notes: March 19
Reduce markup decoration with JS, use more advanced CSS selectors https://github.com/jquery/jquery-mobile/issues/5173 - Demo of simpler button markup, no JS needed
Switch to SVG or font based icons, make it easier to use different icon size https://github.com/jquery/jquery-mobile/issues/5562
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? SASS vs. Compass. Syntax is fairly similar for things like variables and mixins so converting from one to the other wouldn't be hard for people - https://gist.github.com/chriseppstein/674726 (although, if ones design is so complex one needs to use a CSS pre-processor, the design probably isn't that good)
Make is easier to target elements that are wrapped (suffixed class/id) https://github.com/jquery/jquery-mobile/issues/3577
theme inheritance, use CSS instead of getInheritedTheme()? https://github.com/jquery/jquery-mobile/issues/5113

should it be possible to have navbar outside toolbar/content? if so, include it in content wrapper for panels
make it possible to use different iconpos and icon only https://github.com/jquery/jquery-mobile/issues/5374
move grid function to navbar widget?
trigger(“create”) should work: https://github.com/jquery/jquery-mobile/issues/4990 + https://github.com/jquery/jquery-mobile/issues/5141
add refresh and destroy methods
see what we want to do with feature request https://github.com/jquery/jquery-mobile/issues/5436 (don’t switch to multiple rows with 2 buttons if more than 5 buttons in navbar)
overflow issue https://github.com/jquery/jquery-mobile/issues/5566

Current nested listviews deprecated in 1.3
Alternative: Make list item collapsible if it contains a UL https://github.com/jquery/jquery-mobile/issues/5539