link Download 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
- Lots of recent activity so we need to carve out more time for review (Ghislain & Bender)
uGoMobi (Jasper de Groot) has been very active, very high quality work with great CSS attention to detail, we should prioritize review (need Mat to chip in here too for CSS)
link New members:
- Jasper, Codiqa guys - look for people to help us
link PhoneGap blinky transitions
- Scott's recent fix for blinking in PhoneGap seems to be pretty solid, though I've see a few reports that some issues remain. Since PG is a big deal, we should probably accelerate 1.1.1 for release in the next 2-3 weeks.
link Fixed jumping into place on transition w/scroll
- This fix seemed to help when I tested:
Another suggested fix:
I also figured that the major jump is caused when you've scrolled to the middle of a page and trigger a transition and figured that the jump is caused when JQM tries to scroll top and trigger the transition. So I explicitly set it in jQuery to auto scroll to top on every link click.
This fixes 99% of the issue and you no more see the page jumping (the 1% is just a minor flicker in the sticky header which I'm still trying to figure out).
- 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
- Still a problem and need more work, especially on Android. I asked Scott to give this another look on his way up Mt. Everest. There does seem to be issues in Android with fixed that can interfere with either content at the top/bottom of pages not being clickable or links in fixed not being clickable in specific scenarios. Did I mention Android is buggy?
- Pull by MauriceG re: persistent padding: https://github.com/jquery/jquery-mobile/pull/4260
link Button/form consistency
- test page: http://ugomobi.github.com/forms/
link Link styles
- Should we add styles to protect buttons from a: basic styles?
link 2.3 nav issues
- The back button doesn’t work in 2.x in some situations. The proposed fix is a revert back to the old timeout based prevention but doesn’t prevent the popstate triggered navigation like the previous version did.
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 Popup: prototype & API
- Prototype: http://jquerymobile.com/branches/popup-widget/docs/pages/popup/index.html
- Options: http://jquerymobile.com/branches/popup-widget/docs/pages/popup/options.html
- Methods: http://jquerymobile.com/branches/popup-widget/docs/pages/popup/methods.html
- Events: http://jquerymobile.com/branches/popup-widget/docs/pages/popup/events.html
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
- Just landed in master, but this page doesn't seem to be working
- Need to make sure the lists intro, data-attribute page covers this feature (Anne)
- The names of the config parameters (autodividers, autodividersSelector)
- Do we want to pass in the raw HTMLElement to the callback?
link 1.3 Features
link Fetchlink - Needs API design
- Rough idea: http://jquerymobile.com/branches/fetchlink/docs/pages/page-fetchlinks.html
- Tab/slideshow: http://jquerymobile.com/branches/fetchlink/docs/pages/fetchlinks/fetch-tabs.html
- Infinite list: http://jquerymobile.com/branches/fetchlink/docs/pages/fetchlinks/infinite-scroll.html
link Tabs - standalone widget or just a fetchlink demo?
link Themes: Multiple active states
- Support active state per swatch instead of a global active (Tyler - LOE?)
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
- Pull in autocomplete from UI?
- Pull in position from UI?
- Pull in progressbar from UI?
- Light calendar picker?
link 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/