[11:02:13] hey all [11:02:36] <_nickel> hey! [11:02:46] whew. thought this was still moderated. [11:02:49] hiya [11:02:51] hey [11:02:58] hey guys [11:03:22] so scottjehl won't be here so think this is us [11:03:49] since you all have been cranking, maybe you can do a quick summary of the big items [11:03:52] pushstate [11:04:14] <_nickel> toddparker: whats been pushed to the link kinblas has works [11:04:19] <_nickel> save for the chrome issue [11:04:31] <_nickel> I'm working on a fix for that now [11:04:46] <_nickel> the tests are all passing for whats pushed [11:04:52] <_nickel> and we run two test suites for nav [11:04:59] <_nickel> one with push state [11:05:00] <_nickel> and one without [11:05:07] _nickel: what is the chrome issue (sorry for being out of sync) ? [11:05:31] <_nickel> gseguin: forward history is pruned when (push|replace)State is called with a hash in the url [11:05:36] awesome work on the tests _nickel [11:05:42] <_nickel> we submitted the bug yesterday [11:05:50] to chrome? [11:05:53] <_nickel> yes [11:05:57] perfect [11:06:03] http://code.google.com/p/chromium/issues/detail?id=94125 [11:06:08] <_nickel> kinblas: deserver like 99% of the credit [11:06:11] <_nickel> *deserves [11:06:19] eh ... not really [11:06:30] <_nickel> I was really struggling to get the test case boiled down and he helped me out [11:06:37] you both get 110% of the credit [11:06:40] problem solved [11:06:40] <_nickel> :D [11:06:50] * _nickel thanks kinblas heartily [11:06:52] we're running a slight credit deficit [11:06:57] <_nickel> lol [11:07:00] * _nickel go USA! [11:07:05] _nickel: as always ... no problemo [11:07:06] the next administration will tackle that important issue [11:07:14] * _nickel is not sure why he emoted that [11:07:30] patriotic fervor? [11:07:34] heh [11:07:46] so you guys have a workaround in mind for the chrome issue? [11:07:51] <_nickel> yah [11:08:09] just wondering if it's better to land this soon with that as a known issue and work on a fix after [11:08:11] <_nickel> instead of doing a replace state with the hash and triggering hachchange handling [11:08:19] that may give people more time to uncover bugger issues [11:08:21] <_nickel> we'll do the changepage directly [11:08:28] <_nickel> toddparker: I think we can land whats there now [11:08:31] i see [11:08:34] <_nickel> since we have the tests I can monkey under the covers [11:08:45] cool, so we're in agreement that this can go today? [11:08:49] yeah, sure [11:09:02] <_nickel> I'm fine with it if you guys have had a chance to test it [11:09:12] can you reference that chrome bug in the commit and issue tracker if you haven't already [11:09:17] * _nickel braces for bug impact [11:09:24] <_nickel> hmm [11:09:25] so i can do more testing today if needed [11:09:34] the cool thing is it can be ripped out my just removing the plugin [11:09:38] <_nickel> toddparker: ah! you mean add an issue [11:09:40] <_nickel> yesir [11:09:42] i like that, yeah [11:09:50] * kinblas notes he can't type today [11:09:57] <_nickel> toddparker: kinblas: should I stash my work and add a config option? [11:10:11] <_nickel> so people don't have to do the build if they don't want to [11:10:16] <_nickel> or if they don't care? [11:10:16] config for turning push-state on/off? [11:10:19] <_nickel> yah [11:10:27] I think we need a config yes [11:10:47] without it, we're assuming everyone wants this behavior that is different across devices [11:10:49] <_nickel> $.mobile.pushState ? [11:10:59] i think a config option is a good idea [11:11:04] sounds good [11:11:05] $.mobile.enablePushState [11:11:10] <_nickel> kinblas: better [11:11:13] kinblas: +1 [11:11:19] is that "truthy" [11:11:24] <_nickel> :D [11:11:26] love that word. [11:11:45] <_nickel> ok I'll stash my chrome fix and put that in [11:11:46] where'd that come from? [11:11:48] so you want to drop the option in, then push this to master [11:12:00] we need to add this to the docs too [11:12:10] _nickel: by stash you mean, you'll push the config, and then get back to it right? [11:12:14] <_nickel> kinblas: yes [11:12:17] <_nickel> git stash [11:12:26] not 'stache? [11:12:31] lol [11:12:40] : { [11:12:46] <_nickel> toddparker: http://chokeonwords.com/wordpress/wp-content/gallery/mustache/1.gif [11:12:55] woah [11:13:06] i wish you could render images inline here, like campfire [11:13:19] anyhoo, that sounds great [11:13:38] when you add this to the options docs page, try to write it up with enough detail taht I coudl use it as a start for the blog post [11:13:59] <_nickel> toddparker: will do [11:14:02] specifically, explain how it works and where it might cause issues [11:14:04] super [11:14:06] <_nickel> toddparker: should I do that before or after merge? [11:14:16] so kinblas - transitions? [11:14:24] * kinblas cries [11:14:36] * _nickel pats kinblas on the back. [11:14:38] _nickel - are you askign if you shoudl add to docs before of after landing? [11:14:51] <_nickel> toddparker: yah you can ignore that I'll sort it out [11:14:53] So I've spent the last couple of days trying to figure out why we flash sooooo much on the Xoom and on HTC incredible it just doesn't work right [11:14:55] * gseguin feels sorry for having handed that out to kinblas [11:15:06] heh [11:15:08] it works great everywhere else though [11:15:20] the puzzling thing is I've got it to the point where there is no flashing [11:15:21] kinblas is a trooper. he like going to the depths [11:15:25] on Xoom [11:15:37] but incredible is flasy? [11:15:37] if I extract out the page markup and transition manually sans JQM [11:15:44] ah [11:15:47] odd [11:15:55] yeah that's the frustrating part [11:15:58] could the scrolling cause that? [11:16:03] so I'm trying to figure out what other stuff we're doing [11:16:12] @toddparker: yeah I already commented that stuff out [11:16:16] and it still flashes [11:16:44] I also see some page sizing wierdness, i need to talk to Scott about some page height code he added in June [11:17:00] anyways, the CSS we have that actually moves stuff seems solid [11:17:11] as the manual triggering proves [11:17:22] ... the Xoom is actually hardware accerlerated [11:17:50] so I'm still tweaking things ... [11:18:18] * kinblas is done [11:18:24] talking that is [11:18:44] * kinblas tries to avoid the long awkward IRC pauses [11:19:05] I'll go then [11:19:16] Not much to report [11:19:44] Fixed listview padding issues [11:19:54] saw, that thanks gseguin [11:20:00] landed a few requests and commented on others [11:20:17] so kinblas - how many android devices are HW acceleerated? [11:20:19] doing more of the same today [11:20:47] @toddparker: I'm not sure, I'm assuming the Galaxy Tab is too [11:20:51] but I don't have one [11:21:07] kinblas: we have one here [11:21:33] let me know if I can help testing [11:21:49] gseguin: ok I'll shoot you an URL on dev [11:22:04] we have a tab [11:22:09] ok [11:22:24] does anyone need me to do testing today? [11:22:27] ok, my tree currently has stuff commented out while I track down the cause of the flash [11:22:36] ok [11:22:42] @toddparker: I'm not sure where we landed regarding testing last week. [11:22:48] i'd like to test boradly on what we think will go into master [11:22:53] @toddparker: I landed my fixes for ipad/ios [11:23:12] part of those fixes made things bad for the Incredible [11:23:18] * kinblas pulls out his matrix [11:23:20] so you're just tracking down this blinking in honeycomb? [11:23:48] yeah as well as for my Incredible which is 2.1 [11:24:15] http://webpro.host.adobe.com/people/jblas/research/page-transitions/results-01.html [11:25:08] if you look at that page, you really need to pay attention to the jqm and jqm2 columns ... the jqm2 column was the transitions branch with some ipad/ios tweaks ... which represents the current transitions head [11:25:40] i have a 2.1 device i can test on too [11:26:11] @toddparker: I feel like I'm starting to lose my objectivity with this stuff ... questioning if we really need to switch from keyframe to transitions [11:26:13] wait - droid x or incredible [11:26:16] says incredible is 2.2 [11:26:49] whoops yeah I guess I meant 2.2 [11:26:51] i think switching opens us up to broader compatibility [11:27:07] in your experience, is is less smooth than KF [11:27:15] it looked similar to me [11:27:22] @toddparker: I guess in context on the devices I have, I'm not seeing much win, but more platforms support transitions versus keyframes [11:27:23] but i want to re-test [11:27:28] right [11:27:46] @toddparker: to me they look equivalent in all but basic tests [11:27:49] it's also a standard (W3C) vs.a proprietary thing [11:27:58] true [11:28:10] ok ... I'll keep plugging along [11:28:11] but we mainly did it to add FF and Opera [11:28:16] and prolly IE eventually [11:28:20] for 10 [11:28:27] they are going to support transitions [11:28:37] that's why it's not a sexy change [11:28:40] @toddparker: anyways if you want to play with the *CURRENT* transitions code [11:28:43] nothing much better now [11:28:47] then you can use my jqm3 url off that page [11:29:03] ok [11:29:08] i'll prolly do this tomorrow am [11:29:17] I updated the jqm3 and jqm2 trees so they are in sync with the code in transitions branch, but I'm now tweaking jqm2 for debugging [11:29:44] fyi, that page has the short urls for the typing challenged [11:30:08] thanks ;) [11:30:30] * gseguin felt like that was directed at him :) [11:31:50] heh, no todd razzes me about my urls all the time :-) [11:32:24] :-: [11:32:30] :-) [11:33:49] @toddparker: so when you asked about honeycomb were you asking out of concern? [11:33:50] have you ever typed those suckers in? [11:33:57] <_nickel> :-: <- nosering ? [11:34:00] @toddparker: all day my friend [11:34:20] oh, seemed like maybe the blink was a honeycomb issue [11:34:37] _nickel: fat-fingered [11:35:02] so gseguin, thanks for bug fixing [11:35:11] no problem [11:35:32] if you see issues that look serious and you want to tackle for B3, just tag and go [11:35:35] that damn padding on iOS5 though, no luck there [11:35:40] same with everyone esle [11:35:50] feel free to prioritize these [11:35:51] <_nickel> toddparker: kinblas: gseguin: I have one quick question before we finish - just throwing my hat in [11:35:58] gseguin - no worries [11:36:01] sort fo an edge case [11:36:06] k, _nickel [11:36:07] and I don't hace an iPhone with iOS 5 so it's difficult to test [11:36:18] *have [11:36:25] yeah [11:37:06] * kinblas waits for _nickel's question [11:37:25] <_nickel> enablePushState = action [11:37:36] <_nickel> pushStateEnabled = boolean [11:37:42] <_nickel> discuss [11:37:44] <_nickel> :P [11:37:50] +1 [11:38:10] errr [11:38:13] <_nickel> NITPICKING [11:38:18] what is more consistent [11:38:19] +1 [11:38:21] <_nickel> toddparker: this is what happens when you get engineers together [11:38:23] _nickel: not nitpicking ... it follows the other configs [11:38:37] but are those 2 options? [11:38:42] <_nickel> toddparker: hashListeningEnabled [11:38:50] <_nickel> so its consistent [11:38:51] oh, i see [11:38:53] my bad for suggesting enable* [11:38:53] gotcha [11:38:55] +1 [11:38:57] <_nickel> cool [11:39:01] it's unanimous [11:39:18] sweet [11:39:37] oh, so who was going to look at finalizing the hook scott sketched out? [11:39:53] that is less important than these other items, jsut wondering [11:40:19] scott is going to look at the iOS5 enhancements for toolbars and transitions with overflow/fixed [11:40:38] i never got the blog out last week, but will this week [11:40:50] is that going to land in B3? [11:40:50] @toddparker: You talking about the json hook? [11:40:50] be great ot have pushstate in there so i'll til tomorrow [11:40:58] yeah [11:41:03] cool [11:41:15] well, the more limited idea i think [11:41:30] go with the lightest hand, but i want to get something in there [11:41:51] if you all need to discuss specifics, we cna get scott on irc tomorrow [11:41:56] to hash it out [11:42:05] @toddparker: by limited .. are you referring to the json hook ... or to pushstate? [11:42:08] i think you guys might have grander ideas? [11:42:16] json hook [11:42:27] I can help look, I think gseguin needs to look also to keep Jive in the loop [11:42:33] k [11:42:45] alright, think that's all the big stuff [11:42:58] <_nickel> toddparker: GREAT SUCCES! [11:43:04] we should try to get B3 out in the next week to 10 days max [11:43:16] 'cause we only have a few weeks to do bug fixes for 1.0 [11:43:32] when do you foresee 1.0 out? [11:43:34] if 1.0 doesn't hit by the end of Sept., my head rolls [11:43:41] ok [11:43:45] think that needs to be a hard date [11:43:47] it *MUST* ship in september [11:43:56] :-) [11:43:58] we fix as much as we can before then [11:44:00] agreed [11:44:18] i think a few weeks of you guys focusing on bug fixes and we'll be pretty tight [11:44:34] the jQ conf is Oct 3rd and it will be out by then [11:44:40] i'll get boo'd off [11:48:16] Anything else to discuss? [11:49:28] not from me [11:51:13] I guess we're done then [11:51:19] see you guys on -dev [12:12:04] mode #jquery-meeting +m