Category: jQuery Mobile Team

Minutes from jQuery Mobile Team meetings

jQuery Mobile Team Meeting – May 10 2012

link Download builder

  • http://jquerymobile.com/download-builder/

  • https://github.com/jquery/jquery-mobile-builder

  • Open issues: none, 4 reported and closed

  • Include default theme + structure theme - create issue because we only include default, not structure

  • Plans for wider beta since we've run this by our alpha testers for the last 2 weeks

  • Need to test more internally:

  • Modularity questions: how much make we break things up for consumption:

    • Want a specific subset of widgets and transitions (yes)
    • Only want certain widgets, no nav model (yes)
    • Only want nav model/transitions, no widgets or CSS framework (yes)
    • Only want utilities like touch events, zoom fix, orientation (not yet?)
    • How to define mobile “core”

  • CREATE ISSUE: multiple button CSS

  • CREATE ISSUE: generate structure CSS in addition version with theme

link Code indentation

  • I am ready now to work on the docs code indentation to make it 2 spaces. Would it be ok to just update master and not cherry-pick into 1.1-stable?

  • As it will take several days, I'd rather target 1.2 and have it all completed for that, while if I cherry-pick, some pages of the stable version would get updated before others and we'd inconsistent code layout.

  • So is it ok to only update master for now? I could have a standard comment for it to easily track them if we then wanted to update stable before 1.2 is out? If we go for that, do you have a suggestion for what this comment should be? [docs indent]?

  • Decision: make changes in master only for 1.2, don’t cherry pick into 1.1-stable but we may have merge conflicts on whitespace. Wait until 1.2-beta (or RC), than tackle this.

link 1.1.1 Planning

link Pull requests

link New members:

  • Jasper, Codiqa guys - look for people to help us

link PhoneGap blinky transitions

###Fixed jumping into place on transition w/scroll

1
2
3
4
5
 
    $('a').click(function () {
 
      $('html, body, .ui-page').animate({ scrollTop: 0 }, 0);
 
    });
  • This works best either when data-transition is set to either none or fade. Hope this helps someone with this issue.

link Persistent toolbar with fixed

link Button/form consistency

link 2.3 nav issues

link The href monkeying issue

  • We’ve seen several issues coming in that are related to that. # on iOS
    • remove this

link 1.2 Features

link Read-only lists

  • New styling including removal smaller font-size and padding of ui-li-static for 1.2 #4347

*Changes to discuss

  • Modal overlay screen - default to none, only show if data-overlay-theme option is set to a swatch letter
  • Remove "Fade" as an option and just fade in overlay screen if one is specified, CSS override of keyframes if needed
  • Popup container - inherits the theme from the parent page by default, data-theme attr can be set to a swatch letter or to "none" to have the container have an invisible background (just won't write in the ui-content-a/b/c class)
  • Popup won't have any padding by default to let widgets like lists (menus), photos, etc. be edgeless. To add padding, recommend people add the "ui-content" class to the popup wrapper add the standard 15px of page padding or write custom styles as needed
  • Corner classes are a bit tricky with nested edgeless elements. Ex. if a inset list is inside a popup, will the corners look ok?
  • Popup transition. Use the same fallback mechanism as the dialogs >> create a utility that is used for both dialogs and popups. Factor out the mechanism (which is currently inline inside a function in navigation.js) into a public function: degradedTransition = $.mobile.maybeDegradeTransition( originalTransition ); It need not be public - but the little dance it does with looking up the transition in a hash of fallbacks is kind of important, and I don't want to copy/paste that code into popup.✓
  • Add an example of how to add a close button, like dialog, false by default = data-close-btn=”true”. Note that if we add this, we’ll also need a data-close-btn-text=”Close popup” option for accessibility and a11y. https://github.com/jquery/jquery-mobile/issues/4267#issuecomment-5492106
    • Q: Dialog doesn’t have an option currently to not write in the close button, add this feature there for consistency? Probably
  • The custom select should also be ported over to use popup as part of 1.2. Need to create a ticket. Any other widgets that could be ported over? - https://github.com/jquery/jquery-mobile/issues/4329

link Listview: autodividers

link 1.3 Features

link Themes: Multiple active states

  • Support active state per swatch instead of a global active (Tyler - LOE?)

link 1.future

Prioritize and start sequencing the next few releases for the remainder of the year

  • Tablet responsive layout patterns - YES!
  • Decoupling things to use standalone (touch events, vmouse, etc.)
  • Overflow regions - overthrow.js, be very defensive here to not break platforms
  • Performance optimizations to speed up rendering and interactions, enhancement - if you’re building a dynamic app, writing out the enhanced markup directly instead of starting with basic then enhancing via create makes more sense
  • Slider lag (look at UI?)
  • Pre-enhance markup
  • Carousel?
  • Pull in autocomplete from UI?
  • Pull in position from UI?
  • Pull in progressbar from UI?
  • Light calendar picker?

link Infrastructure

###Migration to Grunt (Bender)

  • Migration to Grunt in progress - JS and CSS only, not docs or zip because they aren’t public targets. Need to check with team on this.

link Sort out Test / TestSwarm issues

  • hopefully next week we’ll get this going

link Redirects for Branch Preview / Test to new server (per D. Heberden)

  • Looking into this.

link Plugin site requirements

  • Package JSON file for our plugins

link UI Integration

  • Test port of mobile TR framework onto a UI widget (TBD) as a POC - Scott/Mat
  • Download builder - status of UI’s tool?

link 3rd Party Widgets

  • Think about how to curate semi-official widgets that we recommend to offload some of the dev work. Bender wants to think about how to register and init widgets to make this easier.

link ThemeRoller - 3rd party tools

  • All sorts of web apps or software tools may want to integrate ThemeRoller functionality - how to make this as seamless as possible w/o hooking in too deeply?

  • Current idea: Support a lightweight round trip theme solution that lets a 3rd party tool have a button that would launch TR in a new window/iframe. This could either be a default TR theme (Create new theme) or it could support editing by pushing in a theme (via the import mechanism) so the theme would appear in TR, ready for modification. In TR, allow the Download button to be customized in appearance (Save to App X + icon) and the 3rd party tool would write a handler to manage the manipulation and saving of the TR output on their side. We'd just provide the hooks in and out so this would be a new API for developers to use TR without forking it and making a custom build.

  • Tyler needs to do more work on the versioning side of things to support this. The guys from Codiqa have volunteered to help with some of the engineering and to be the test case for this to help us work out the kinks. This would launch as an open platform and others tools can help participate in shaping this as we go.

  • Help test the new ThemeRoller versioning: http://jquerymobile.com/themeroller-test/

jQuery Mobile Team Meeting – May 03 2012

link Download builder

http://jquerymobile.com/download-builder/ https://github.com/jquery/jquery-mobile-builder

  • Open issues: none, 4 reported and closed
  • Include default theme + structure theme - create issue because we only include default, not structure
  • Plans for wider beta since we've run this by our alpha testers for the last 2 weeks
  • Need to test more internally:
  • Modularity questions: how much make we break things up for consumption:
    • Want a specific subset of widgets and transitions (yes)
    • Only want certain widgets, no nav model (yes)
    • Only want nav model/transitions, no widgets or CSS framework (yes)
    • Only want utilities like touch events, zoom fix, orientation (not yet?)
    • How to define mobile “core”

link ThemeRoller - 3rd party tools

  • All sorts of web apps or software tools may want to integrate ThemeRoller functionality - how to make this as seamless as possible w/o hooking in too deeply?
  • Current idea: Support a lightweight round trip theme solution that lets a 3rd party tool have a button that would launch TR in a new window/iframe. This could either be a default TR theme (Create new theme) or it could support editing by pushing in a theme (via the import mechanism) so the theme would appear in TR, ready for modification. In TR, allow the Download button to be customized in appearance (Save to App X + icon) and the 3rd party tool would write a handler to manage the manipulation and saving of the TR output on their side. We'd just provide the hooks in and out so this would be a new API for developers to use TR without forking it and making a custom build.
  • Tyler needs to do more work on the versioning side of things to support this. The guys from Codiqa have volunteered to help with some of the engineering and to be the test case for this to help us work out the kinks. This would launch as an open platform and others tools can help participate in shaping this as we go.

link 1.1.1 Planning

link Pull requests

link PhoneGap blinky transitions

link Fixed jumping into place on transition w/scroll

link Persistent toolbar with fixed

link Button/form consistency

link 2.3 nav issues

link The href monkeying issue

  • We’ve seen several issues coming in that are related to that. # on iOS
    • remove this

link 1.2 Features

link Read-only lists

  • New styling including removal smaller font-size and padding of ui-li-static for 1.2 #4347
  • Changes to discuss
    • Modal overlay screen - default to none, only show if data-overlay-theme option is set to a swatch letter
    • Remove "Fade" as an option and just fade in overlay screen if one is specified, CSS override of keyframes if needed
    • Popup container - inherits the theme from the parent page by default, data-theme attr can be set to a swatch letter or to "none" to have the container have an invisible background (just won't write in the ui-content-a/b/c class)
    • Popup won't have any padding by default to let widgets like lists (menus), photos, etc. be edgeless. To add padding, recommend people add the "ui-content" class to the popup wrapper add the standard 15px of page padding or write custom styles as needed
    • Corner classes are a bit tricky with nested edgeless elements. Ex. if a inset list is inside a popup, will the corners look ok?
    • Popup transition. Use the same fallback mechanism as the dialogs >> create a utility that is used for both dialogs and popups. Factor out the mechanism (which is currently inline inside a function in navigation.js) into a public function: degradedTransition = $.mobile.maybeDegradeTransition( originalTransition ); It need not be public - but the little dance it does with looking up the transition in a hash of fallbacks is kind of important, and I don't want to copy/paste that code into popup.✓
    • Add an example of how to add a close button, like dialog, false by default = data-close-btn=”true”. Note that if we add this, we’ll also need a data-close-btn-text=”Close popup” option for accessibility and a11y. https://github.com/jquery/jquery-mobile/issues/4267#issuecomment-5492106
      • Q: Dialog doesn’t have an option currently to not write in the close button, add this feature there for consistency? Probably
    • The custom select should also be ported over to use popup as part of 1.2. Need to create a ticket. Any other widgets that could be ported over?

link Listview: autodividers

link 1.3 Features

link Themes: Multiple active states

  • Support active state per swatch instead of a global active (Tyler - LOE?)

link 1.future

  • Prioritize and start sequencing the next few releases for the remainder of the year
  • Tablet responsive layout patterns - YES!
  • Overflow regions - overthrow.js, be very defensive here to not break platforms
  • Carousel?
  • Pull in autocomplete from UI?
  • Pull in spinner from UI?
  • Pull in progressbar from UI?
  • Light calendar picker?

link Infrastructure

###Migration to Grunt (Bender)

  • Migration to Grunt in progress
  • Sort out Test / TestSwarm issues
  • Redirects for Branch Preview / Test to new server (per D. Heberden)

link Plugin site requirements

  • Package JSON file for our plugins

link UI Integration

  • Test port of mobile TR framework onto a UI widget (TBD) as a POC - Scott/Mat
  • Download builder - status of UI’s tool?

jQuery Mobile Team Meeting – Jul 07 2011

##BETA 2 ITEMS

###All beta 2 issues here:

###Transition improvements - See “Transitions” branch

###Remove ajax-loaded pages after hide.

  • Commit for branch here: https://github.com/jquery/jquery-mobile/commit/2265330677ca4ce1b3808112a7c5952cd555ca5e
  • adds an option to the page plugin:
  • ajaxDomCaching: false (default)
  • will remove a page from the DOM when it is transitioned out, this will leverage the native browser’s cache to store pages
  • if set to true, it will leave pages in the DOM as now
  • we’d recommend leaving this off, but it can be turned on per-page via data-ajax-dom-caching=”true” on the page container
  • need unit tests before pushing

###Add a data-prefetch attr to any anchor element and jQM will load it

  • branch: https://github.com/jquery/jquery-mobile/commits/prefetch
  • basically a markup shortcut for $.mobile.loadPage
  • new data-prefetch attribute, which can be applied to any anchor element in the page and trigger a pre-fetch request of that anchor's href url
  • a great way to transition away from multi-page docs
  • need unit tests before pushing

###Auto-init branch

###pushState

###Decoupled widgets

###XSS with XHR level2 cross domain request

##QUESTIONS

##PULLS

jQuery Mobile Team Meeting – Jun 30 2011

##Areas of focus right now:

###Cross-platform page transitions (Ghislain)

###PushState implementation: In the works (Scott)

Our approach: this sits on top of the current hash system and when hashchanges come through, if pushstate is supported, it replaces the hash with a better url but will fall back to tracking haschchange in the browsers that don’t support pushstate.

It’s working quite well so far in Firefox 5, Chrome, Safari, and Opera latest. We need to do more testing on mobile devices.

Unfortunately iOS gets pushstate wrong (support is true, but it only lets you set pushstate based on a user action, like in a click callback) which doesn't work for us, since we set hash based on all sorts of conditions, including programmatically with $.mobile.changePage. If we strictly used history.pushState when it is supported, iOS would really break because the URL just never update. Instead, we use replaceState to react to hash changes which ensures that iOS is excluded from this feature until it’s properly supported. So iOS still gets hash urls, despite its claimed pushState support (this isn't fixed in iOS5 either).

Some URLs will always be hash-based such as dialogs and nested lists which lines up well with how hashes traditionally work anyway. When it's a dialog or a nested list page url, we’re only adding the relavant part to the hash.

We’ll need to do a lot of work on our unit tests to fork it to either look at the URL or hash because this feature won’t be supported in many places for the near term.

###XSS fix (Ghislain has a fix, jaubourg to review)

###IE/WP7 - gradients and rounded corners = trouble

Should we just drop all -filter rules and go with flat color for IE? Even with these in not, IE and WP7 don’t show gradients (need some hacks for it to work), Mango bleeds out corners if combined with a -filter gradient. IE10 will support standard CSS gradients. I’d rather add support for Opera gradients because it works and has greater reach.

##Beta 1 - blog post

###Beta 1: Issues with vclick for handling links

In Beta 1, we switched to using our custom vclick events in Beta 1 for handling Ajax links to improve responsiveness and because this change really helped to hide the URL bar consistently on the iPhone and Android phones. The vclick feature is a custom synthetic event that normalizes events by listening for touch and click events. It works at the document level and looks for duplicate events on the same target and will go with the one that bubbles up first and cancels the duplicate event.

Even though we did quite a bit of testing before landing this for Beta 1, we began to hear feedback that this change was causing some significant issues out in the wild including:

  • Multiple click events causing navigation and form element issue – In certain situations, when tapping an element, tap/click events seem to fire twice on links and is due to edge cases where the target of the touch event and mouse event don’t match due to how the browsers calculate tolerances for these events. This is most pronounced on Android 2.1 but affects most WebKit-based browsers when you tap near the edge of an element.

  • Click handlers in custom scripts didn’t “work” anymore – if a script binds only to click events on the document, the vclick feature could interfere because the touch events may supercede these click events so it won’t appear to trigger.

  • Disabling vclick globally didn’t work – To compound the issue, we had recommended using a new $.mobile.useFastClick option to disable the vclick feature globally but there was an issue with this option in Beta 1 that prevented this from working as designed.

###Our solution: Roll back from vclick to click globally

Based on a lot of detailed testing and analysis, we’ve decided to roll back to using standard click events on links instead of vclick because it’s the only reliable way to support all our target browsers. If you test on the latest builds with this change integrated, things should work reliably again. There are two important things to note in this change:

  • URL bar hiding isn’t quite as slick as in Beta 1, but link handling is obviously much more important. The good news is that there is still a significant improvement from Alpha 4.1: although URL bar may appear briefly it overlays the page instead of pushing down content and causing a re-draw blink. We methodically tried every technique we could to keep the URL bar hidden but there is unfortunately a Safari bug (even in the latest Beta 2 of iOS 5)

  • The useFastClick option is now removed in the latest code because we’re not using vclick globally anymore on links and don’t recommend doing this going forward. We hardly knew ye…

##Beta 2 - Planning and prioritization

jQuery Mobile Team Meeting – Jun 23 2011

##Beta 1 - Identify any key issues or regressions

###vclick issue

###Blackberry 5

link Beta 2 - Planning and prioritization

jQuery Mobile Team Meeting – Jun 07 2011

##Navigation re-write status update

##Blockers for beta 1 - for discussion

https://github.com/jquery/jquery-mobile/issues?sort=created&direction=desc&state=open&page=1&milestone=5

###ChangePage() and Navigation paths refactor

###Double vclick - not an issue?

###Fixed? iOS scroll position history broken in A4

###AJAX requests broken due to incorrect host name

###Ajax in Chrome & Android

###Radiobuttons can't be selected once they are selected, then de-selected

###Radiobutton onchange event issues

###Change page CSS error

###Ajax off fixes

With Ajax off, we need to tweak all plugins that rely on Ajax. This needs to be done anyway because this feature cna always be turned off globally but we have some dependent plugins:

jQuery Mobile Team Meeting – May 24 2011

##Navigation re-write status update

##Targeting Ajax navigation and animated page transitions (Scott) Currently in jQuery Mobile, if a browser supports media queries or is Internet Explorer, we enhance the page to the full experience, including Ajax-based navigation for animated page transitions. The issue we’re seeing now is that there are browsers that support all the advanced enhancements but don’t properly track hash changes as history stack events so the back button is essentially broken on both Blackberry 5 and Symbian. Opera Mini also has issues with the Ajax navigation system because of the way it’s proxy-based rendering works.

###Suggested action:

jQuery Mobile Team Meeting – May 17 2011

##Navigation re-write status update

##Targeting Ajax navigation and animated page transitions (Scott) Currently in jQuery Mobile, if a browser supports media queries or is Internet Explorer, we enhance the page to the full experience, including Ajax-based navigation for animated page transitions. The issue we’re seeing now is that there are browsers that support all the advanced enhancements but don’t properly track hash changes as history stack events so the back button is essentially broken on both Blackberry 5 and Symbian. Opera Mini also has issues with the Ajax navigation system because of the way it’s proxy-based rendering works.

###Suggested action:

link Restore user zooming capability

  • Right now, all our demos and docs have this meta tag:

<meta name="viewport" content="width=device-width, minimum-scale=1, maximum-scale=1">

The issue is that the minimum-scale=1, maximum-scale=1"portion completely disables the pinch- or double-tap-to-zoom feature which isn’t very “webby” so we’re going to change our meta tag to set a better example of how to code a page in jQuery Mobile. The meta tag is part of the user’s page content so this isn’t a change to the library per-se, but our demos are used as a template for many users so this is important to evangelize.

  • The proposed meta tag we’ll use will look like this:

<meta name="viewport" content="width=device-width, initial-scale=”1”">

On iOS, there is a bug that will incorrectly scale the page when you change orientation which is the reason why we originally used the current meta tag configuration, but we don’t think it’s worth disabling the user’s zoom feature to workaround an iOS bug that may be fixed in the near future. A bug was submitted to Apple by Filament Group, and there’s a description here: http://filamentgroup.com/examples/iosScaleBug/

JavaScript can be used to manipulate this tag dynamically but this approach is far from fool-proof and causes some performance issue so we want to start with the simplest option (leaving the browser feature untouched) and think about alternatives to improve this for 1.0. Jeremy Keith has a great article on this topic: http://adactio.com/journal/4470/

Ticket for this change here: https://github.com/jquery/jquery-mobile/issues/1645

Fix provided here: https://github.com/jquery/jquery-mobile/commit/8ba4c27300da72f5792c98a6aeb53e2f2fd4b02c

and here: https://github.com/jquery/jquery-mobile/commit/04cb9c185040994265ffbd3e40a9ab2cb3ab1dbb

##Remove dynamically injected viewport meta tag

This was deprecated in alpha 4 due to Windows Phone 7’s lack of support for dynamically injected viewport elements. In the end, we think this should be in the page to start anyway, so we’re recommending that users of jQuery Mobile write the meta viewport tag into the head of their page (with content=”width=device-width, initial-scale=1”).

Fix here: https://github.com/jquery/jquery-mobile/commit/adf3808e842677feb23e9d1102c7203ab82a42a3

##Git repo size

The jQuery Mobile repo's large and it may be due to obsolete branches.

##Transition encapsulation and packaging (current state: fuzzy idea)

  • (From Steve) Currently we have jquery.mobile.transition.js package (for css3 transitions) and jquery.mobile.navigation.js acting as a transition “god object” (as it were). Possibly better: navigation triggers at the appropriate junctures, and transitions, as a self-sustained independent package, listens and acts, or not. Acid test: navigation would know nothing about transitions.

###Probably good: Audit, eliminate setTimeout() wherever possible

  • Expecting that some of these can be engineered with $.deferred instead.
  • Currently we have 15 setTimeout() calls in Master.
    • 2 in core.js
    • 2 in event.js
    • 2 in footer.js
    • 3 in select.js
    • 1 in textinput.js
    • 1 in hashchange.js
    • 3 in navigation.js
    • 1 in vmouse.js

jQuery Mobile Team Meeting – May 10 2011

###Datepicker fixes

Outcome: Looks good, but we need tests.

###Navigation Extensibility:

  • https://github.com/jquery/jquery-mobile/wiki/Refactor:-navigation.js-A4.1-extensibility
  • A solid philosophy suggestion for hooks:
    • Events trigger, or call methods, always.
    • Conditional pre-hook the events (@ top)
    • Post hook methods (@ bottom)
  • Currently some of our hooks are at the same juncture. These are effectively the same hook.
    • Example: beforehide and beforeshow are separated by 2-lines, and pagehide and pageshow are separated by 2-lines
  • URL hooks (upon get especially) are probably critical things to add.
  • Not documented in the wiki yet: authoritative user gestures like swipeleft or swiperight; ability to override any pre-specified transitions at that juncture.
  • Not really a hook, but listed on that wiki page: allowing re-loading the same page including transition for apps that munge the same target container over and over.

###Pull: Input/selects with dots in with ID

###Opera Mini: ajax and scrolling issues

  • The problem: Opera Mini prior to V6 times-out after 2.5 seconds. See Issue 1276. https://github.com/jquery/jquery-mobile/issues/1276
  • One notion is the progressive enhancement crutch is expensive for Opera Mini because we do a lot of expensive DOM insertions and manipulations that, in the end, never render anyway. A link is never a button or a bar when rendered in Opera Mini; it stays a simple link. Therefore maybe we should option-out of expensive markup, especially DOM insertions, transitions, and some setTimeout() kluges in some key situations like Opera Mini.
  • Another notion: drop Opera Mini which is expensive in terms of the wider mission for jQuery Mobile.

###Targeting Ajax navigation and animated page transitions

Currently in jQuery Mobile, if a browser supports media queries or is Internet Explorer, we enhance the page to the full experience, including Ajax-based navigation for animated page transitions. The issue we’re seeing now is that there are browsers that support all the advanced enhancements but don’t properly track hash changes as history stack events so the back button is essentially broken on both Blackberry 5 and Symbian. Opera Mini also has issues with the Ajax navigation system because of the way it’s proxy-based rendering works.

Due to these limitations, we’re currently exploring how to better target Ajax navigation only to a subset of capable browsers because the animated page transitions that Ajax enables seems like a “nice-to-have” enhancement that we should layer on only if confident we won't negatively impact the user experience. We don’t believe that using user agent detection is a sustainable way to make this divide so we’re investigating feature-based detection to allow us to only opt only fully capable browsers into the Ajax navigation system.

jQuery Mobile Team Meeting – May 03 2011

##New volunteer: Alex Kessinger, developer at Mixed Media Labs and their jQM/native hybrid PicPlz app, and speaker at last jQuery Conf. Can’t be on the call but will check in after.

###Navigation re-write status update and planning

  • URL handling:

    • in-progress, test written, code changes this week by Kin

  • Extensibility hooks: need to document on wiki page

    • Steven Black will start a wiki page with suggesitons

  • Caching: a simple "don't cache" flag per page

    • A new data-cache attribute on the page div to tell framework to re-load it if shown again, default is “true” (re-use the page) but you can set data-cache="false" to tell the framework to re-load ever time it’s viewed
    • $( "[data-role='page'][data-cache='false']" ).live( "pagehide", function(){ $(this).remove(); });
    • Issue: https://github.com/jquery/jquery-mobile/issues/1554

  • Memory management: how to keep the DOM from getting too big?

    • A new global configuration option to set the max number of pages to keep in the DOM at once. Once that max is hit, we run a a document-wide $("selector").remove() at the appropriate juncture in every changePage invocation (post Ajax success) that finds all pages that are data-cache="false" or oldest in the stack and delete them. We’ll need to check for alreadyLocalPage = ("[data-url='...']:not([data-cache='false']")
    • Default to a sensible number like 15-20 pages but this can be overridden to any number more than 2 (to allow for transitions) or turned off completely
    • Issue: https://github.com/jquery/jquery-mobile/issues/1555

  • Focus: can we handle this better?

    • we need to have focus brought to the top of the current page on transition for accessibility and keyboard/focus-based navigation
    • Scott Jehl will create a wiki page with suggestions

  • Transitions: how to smooth out, eliminate blinking

    • Kin will tackle this after URLs

https://github.com/jquery/jquery-mobile/wiki/Refactor:-navigation-paths

https://github.com/jquery/jquery-mobile/wiki/Refactor:-navigation.js-A4.1-structure

https://github.com/jquery/jquery-mobile/wiki/Refactor:-Transition-dependencies

https://github.com/jquery/jquery-mobile/wiki/Refactor:-changepage

###Radiobuttons can't be selected once they are selected, then de-selected

###Opera Mini Page ScrollTo issues - blank & cut off pages

###Blackberry 5 support - A or C grade TBD based on performance.

###Checkbox array support

##PULL REQUESTS

###listview.filter / data-filter performance optimization

###Decoupling Navbar State from Button "active" State

###Images with full URL broken in FF

###Theme inheritance in dialogs

###Update functional tests: bind click event to objects

###Dynamically insert thumbnail item at 0-index position doesn't update all style after listview refresh

###Several patches - Faster data filter / control what is filtered + Load dialog content from other base URL

###Patch for issue #1024 (Duplicate pages created in DOM)