1.next planning

This is not a final or prioritized list for 1.1. Instead this is just a discussion document to get us thinking about some of the key areas to focus on that we can refine into a roadmap.

Page transitions

• need a re-think to embrace the constraints we have - scrolling the docs can't be avoided, but we cn hide the jumpiness = introduce 1-2 new transitions that are smooth on all our platforms
• video sketch for animations (slow to illustrate the steps) - http://www.youtube.com/watch?v=di3-fz5TZKQ
• consider packing the new transitions with the switch from keyframe-based animations to transitions so we can package these with Opera, Firefox and IE10 support
• speed up page load/enhancement/transition time overall

Fixed headers

• Re-think whether we should use or dynamic re-positioning script or just use position:fixed since browser support is pretty solid. Some browsers that "snap" into place look like our dynamic re-position script anyway. Watch the video for results: http://bradfrostweb.com/blog/mobile/fixed-position/
• Sounds like there may be some bugs with 2.2 and even iOS5 with fixed - see comments

scrollOverflow

• Need to do more testing and debugging to see how smooth we can make this. I have concerns over the smoothness of scrolling in OS5 and how long it will take for other platforms to achieve acceptable performance to rely on this.
• Also think about whether we should leverage the same dual container model to allow a scroller polyfill to be hooked in

Touch Events & Scrolling

• Improve scrolling performance by tweak how we handle events (and maybe also force pre-rendering)
• Can we make mouse more reliable? Confusion about how to use this
• Look into touch event model for IE10

Dialog

• new markup so dialog is in a wrapper, overlay is a sibling, not a parent
• eliminate the scroll up/down when a dialog is opened/closed
• don't delete the parvenus page when a dialog is open, most times people go back
• consider having the dialog sit over the previous page

Link-based buttons & navbars

• support disabling? lots of people asking to to do this, even though technically disabling a link is odd, even if it looks like a button
• general confusion between link that looks like a button (buttonMarkup) and the button plugin

Tablet optimized layouts

• Review work already done by Sven - http://www.stokkers.mobi/valuables/multiview/page2.html
• Work out the key use cases we want to support in core, plan extension points
• Use media queries with a polyfill like respond.js to do the heavy lifting
• Figure out how to deal with hsitory and deep-linking in a rational way
• Create lots of small atomic tools we can assemble into larger demos:

Ajax include pattern (new plugin)

• a link on the page points to a page or fragment, at certain screen widths, this link is used to formulate an AJAX request that essentially works like an include.This way, at smaller screen sizes you can have a link to view the weather forecast but at desktop sizes, you can load the module in.
• control where the content goes: replace the link, append before/after
• decide the min width breakpoint to AJAX load the content
• encode what fragment to pull in, either through a data-attribute or force them to use an ID so we could do: foo.html#fragment

Popup/popover (new plugin)

• new widget to open content in a simple overlay
• consider leveraging this dialogs and custom selects

Navigation (new plugin)

• add a few simple responsive design navigation patterns to transform a horizontal nav bar into a menu, hide/show a search icon, etc.

Responsive layout grids

• create a few simple RWD layout patterns and focus on documenting how to write your own custom ones (this is all/mostly CSS)

History tools

• expose a simple way to let people include/exclude links or other JS-based actions in the history stack