• Attending: John Bender, Todd Parker, Jasper de Groot, Maurice Gottlieb

link Todd

• 1.2 Beta Status - It’s taken a lot of time to work around some really frustrating browser bugs but as of today, all blocker issues with WP7 and Android have been addressed in the popup-simple branch. This branch also includes some code simplification of the history tracking since popup stacking isn’t supported. Please help us test today before we land in master for beta later today: http://jquerymobile.com/branches/popup-simple/index.html Here is a rundown of the worst bugs we’ve been wrestling with:
  • Visual z-index issues in Android 4.0 default browser (#4816 and #4874) - When fixed toolbars were used on a page, the use of any position:fixed elements cause havoc with rendering of stacked elements in Android. In these situations, the popup would visually appear under the overlay but was still clickable so this was a display bug. This issues were addressed by adding conditional logic that will toggle the toolbars from position:fixed to position:absolute when the popup is opened and closed. The drawback to this fix is fixed toolbars appear to hide when a popup is open, but this workaround is only applied to Android 4.0 and will only been seen if there are fixed toolbars and popups with an overlay theme.
  • Animating overlay opacity bug in Android 4.0 Chrome (#4915) - The CSS-based fade in/out transition on the themed overlay causes similar visual stacking bugs as fixed toolbars in Chrome. This was addressed by removing the fade behavior on the overlay. Testing revealed that not animating the opacity of the overlay made the popup display significantly faster so this change is now applied across the board. The overlay now pops into place without a transition and adding a transition isn’t offered as an option.
  • Wild scrolling in WP7.5 when closing a popup (#4784) - When closing a popup in WP7, the window would scroll to random locations. Turns out this was due to a bug in WP7’s history management that would not correctly remember the scroll position when we used the history and hashchange to close the popup. After spending over a week looking at possible solutions, the team has determined that this can not be worked around. To address this bug, we have excluded just WP7 from back button support with popups so these must be closed by clicking outside the popup or using a developer-supplied close button. We also had to handle the close button behavior to work without hashchange to work with this situation. The option to track history has been exposed as the “history” option now in the popup API: http://jquerymobile.com/branches/popup-simple/docs/pages/popup/options.html
  • Multiple button focus states in WP7 - Multiple buttons would get the focus state as popups were opened and closed. Also related to WP7’s buggy history implementation and fixed by excluding them from history.
• Targeting 1.2 beta the week of September 3, with a RC soon after
• Roadmap prioritization in progress, will have public details soon

link John Bender

• Re-factoring popup code, added history feature, unit tests
• Popup ready for testing
• Performance work on button markup, testing needed

link Jasper de Groot

• just tested popup-simple branch on Android 4.0.4. native browser + Chrome, issues:
  • native browser: go to popups page in the docs > go to one of the advanced examples pages > open and close a popup > click "back to popups" link .... the url doesn't change
  • https://github.com/jquery/jquery-mobile/issues/4898 (is the plan to disable scrolling?)
• fixed https://github.com/jquery/jquery-mobile/issues/4856
• fixed https://github.com/jquery/jquery-mobile/issues/4835
• fixed https://github.com/jquery/jquery-mobile/issues/4663 (we need to test on JB to see if John’s fix can be reverted: https://github.com/jquery/jquery-mobile/commit/b668b6006967354111f62caf96db37d63052bb52)
• Opera transitions: don’t work because Opera doesn’t suppport 3D-transforms at all
• created a branch on my forked repo with transitions for IE10 (unprefixed)

• Attending: John Bender, Todd Parker, Jasper de Groot, Maurice Gottlieb

link Todd

• 1.2 status - we’ve decided to re-work some of the popup history code to see if that will help with some of the WP7 (focus state, scroll jump when closing popups). Since this will require a fair amount of code re-factoring (and reduction), we’ve decided to release a beta version to make sure there are no regressions before moving on to RC status.
  • WP scrolling: https://github.com/jquery/jquery-mobile/issues/4784
• Updating master to use 1.8 today, been testing with core master for a while but good to use it daily. When 1.2 final hits, we should support 1.6.4-1.8.1
• Targeting 1.2 beta late next week at the earliest with a RC soon after
• Roadmap prioritization in progress, will have public details within a week or so

link Ghislain Seguin

• Joyent is discontinuing no.de, that’s where we host the backend service for the download builder. Their replacement (nodejitsu) is really cool but you can’t SSH to the VM which doesn’t work for our purpose: it’s needed to create the initial checkout and workspaces. Waiting on gnarf for the machine to be ready on jQuery hardware.
• Move master to jQuery core 1.8

link John Bender

• Base tag: ability to disable manipulation, waiting on feedback from the latest on that branch
• Closed 3 PRs
• popup work: re-factor history to simplify (https://github.com/jquery/jquery-mobile/commit/7a14e1588977)

link Jasper de Groot

• Started to look into some open issues and PRs for 1.2
• Triage a priority next week

• Attending: John Bender, Ghislain Seguin, Gabriel Schulhof, Jasper de Groot, Anne-Gaelle Colom

link Todd

• 1.2 status - hunting down last two WP7 critical issues (focus state, scroll jump when closing popups) and confirming that Android forms with on-screen keyboard is 100% ok on all versions, now targeting for RC next week
• If WP7 issues aren’t fixable due to hashchange bugs in their browser, we may need to exlcude back button support on this platform.
• Targeting 1.2 RC1 late this week
• Roadmap prioritization well underway, will have public details within two weeks or so

link John Bender

• 2 highs, 2 criticals fixed
• Basetag work continues
• Helping infra get setup on Vagrant

link Ghislain Seguin

• Builder issue fixed
• Need a node.js to replace no.de instance it's running on now

link Gabriel Schulhof

• Popup issues - #4784 “fixed” on branch fix-4784 - gonna investigate why there are no problems if the overlay stays visible (as Wilto was experiencing)
• Android 4.0 hangage - rapidly running out of ideas. We may have to use the fix currently on master, but confine it to Android 4.0 via UA checking (à la fixedToolbar) - everyone else attaches the handler to the screen (rather than allowing the event to bubble up to document and handling it there)
• Observation: responsive-carousel inside a listview + “swipeleft swiperight” event handler = swipe-to-reveal

link Jasper de Groot

• No Updates (device issues), joining back in tomorrow

link Anne-Gaelle Colom

• fixed a few issues on the api docs, need to add the event parameters to the existing widget pages
• Will be away for the next 2 meetings