[09:00:57] howdy DaveMethvin addyosmani_ timmywil [09:01:09] ohai! [09:01:15] yay meeting [09:01:29] ohai guys [09:01:41] Hi [09:02:07] hey dere [09:02:16] I'm interested in finding out if there's been much progress on the Trac front from last week :) [09:02:23] when you get around to it of course! [09:02:27] he sindresorhus! [09:02:30] hey* [09:02:35] why is my sound always muting!!!! very annoying [09:02:45] i miss all my alarms [09:03:00] ok let me start the agenda [09:05:14] DaveMethvin harsh! [09:05:23] you sunk my battleship [09:05:55] the grunt stuff? [09:05:58] that was from last week [09:05:59] yeah [09:06:03] it's still there [09:06:11] I put that in there for this week [09:06:11] ok [09:06:15] just like... 3mins ago [09:06:26] oh then it needs to be moved up ... just a sec [09:06:36] I just wanted to report my progress is all :) [09:06:46] ta da [09:06:59] woo! [09:07:06] ok, lessee here [09:07:20] does anyone have bugs they wanted to get into 1.7.2? [09:07:34] i'd still like to get an rc out tomorrow if there isn't anything holding us up [09:07:57] i was tryna go thru trac over the weekend but it wasn't cooperating [09:08:12] so, did anyone follow that PR thread? [09:08:23] the ie6 one? [09:08:40] https://github.com/jquery/jquery/pull/699 [09:08:41] ★ Pull request on jquery by amonat (23h, 6m ago): Remove obsolete test code. Fixes #11435 [09:08:51] I haven't had a chance to actually run through these [09:09:04] tickets I am assigned to page spit out $USER instead of timmywil [09:09:20] odd [09:09:40] * DaveMethvin shakes fist ... "TRAC!" [09:10:12] yeah i wanted to look at pr699 rwaldron, he may be right [09:10:27] that would deuglify .data a bit [09:10:53] plus that was the hack we put in where snover had a comment "this is for 1.5.1 ONLY!" :) [09:11:02] and it's still there [09:11:47] just a sec [09:14:52] sorry, back [09:15:21] ok, anyone else with stuff for 1.7.2 then? [09:16:27] i'll plan on rolling out the rc tomorrow afternoon if there are no objections then [09:16:42] if trac holds up i'll try to make a pass through tonight and see if we've missed anything [09:17:25] I'll go ahead and knock out docs#10870 today [09:17:27] [#10870] (assigned bug) - http://jqbug.com/10870 [09:17:56] great, thanks timmywil [09:18:41] i just added an item for unit test failures [09:19:03] i played with some of these and they seem to be the issue with timing being off when firefox doesn't have focus [09:19:23] i bumped up a lot of timeouts and got it to behave better locally [09:19:32] but it's still acting strange when Jenkins runs it [09:19:51] Anybody with expertise on this? [09:21:52] looking for a link to the last run to show you [09:23:39] http://swarm.jquery.org/job/957/ [09:23:48] that was last run [09:24:03] i have to look at the 3.6 fails, but the effects fails on ff10 are the ones i was talking about [09:24:52] blah [09:24:53] http://viewvc.svn.mozilla.org/vc/libs/product-details/json/firefox_versions.json?view=co [09:24:58] was hoping it would be gone [09:25:31] unfortunatley i think it will be around a year or more [09:25:50] as soon as corporate america adopts it, we are talking about a multi-year death cycle [09:25:53] haven't looked into it. So the timers do not get cleared when out of focus? [09:26:08] the timers aren't precise [09:26:16] so 100ms can be 1 second [09:26:34] sob [09:26:36] and a few of our tests are like, "animation stopped about halfway thru" [09:26:43] right [09:26:44] which is kinda risky anyway [09:26:59] so i had to switch 100/200ms to 1000/2000ms [09:26:59] yea, but is there another way to test that? [09:27:08] probably not [09:27:21] i can try pushing up the timeouts even more [09:27:50] well, we could have a step function that calls stop when it reaches a certain value I suppose [09:27:57] but ugh [09:28:07] but there are a LOT of animation tests that use settimeout delays [09:28:13] yes there are [09:28:28] i started to change more of them and then wondered whether it was a good idea [09:28:37] well, this is test suite problem, not a library problem [09:28:49] agreed, i just don't like jenky hollerin at me [09:29:05] plus i am starting to treat him like the boy who cried wolf [09:29:12] heh, yea [09:29:19] every once in a while he's right [09:29:32] it might be the case for this 3.6 problem, i dunno [09:31:30] Sorry, I'm a abit confused.... [09:31:43] the failures in that PR thread - are those related? [09:31:53] or is this in addition? [09:32:06] these are ff10 failures [09:32:16] related to their treatment of timeouts when not in focus [09:32:17] ok gotcha [09:32:19] at least i think it is [09:32:27] I'll see if we can find a solution for those unit test issues, but i agree that it's not a library issue [09:32:30] seems reasonable [09:32:38] that's what I thought, but I wasn't sure if there was a connection between these and those [09:32:46] it doesn't seem so... [09:32:52] i don't think so either [09:32:59] that's where I was confused [09:33:04] i mentioned the PR thread [09:33:10] i would just be a lot happier if jenky would say SUCCESS [09:33:16] and then the conversation jumped into this [09:33:30] sorry for the unne. confusion! [09:33:40] no confusion is ever unnecessary [09:33:43] :) [09:34:02] Soooo, how bout that 1.8? [09:35:22] i have some stuff started to refactor and identify dependencies, once 1.7.2 is out I'll get back to that [09:35:54] i think a lot of this will be "behind the scenes" and not have to involve api changes beyond what we've already identified [09:36:12] looking forward to it [09:36:25] rwaldron: i'm looking forward to seeing the grunt stuff [09:36:28] I wish I could see the 1.8 ticket list [09:36:31] it's sassy [09:36:43] DaveMethvin after the meeting, I will push up my progress [09:37:12] I haven't had time to destroy sizzle yet, but I will [09:37:19] i just finished doing the "sizzle-jquery.js into sizzle.js into selector.js" dance [09:37:44] any other issues to discuss? [09:38:30] well then, go forth and code! [09:38:34] WAIT [09:38:38] 1.8 all tickets: [09:38:39] http://bugs.jquery.com/query?milestone=1.8&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&report=206&order=priority [09:38:45] there wasn't a report for it [09:38:47] now there is [09:38:49] have fun [09:38:50] <3 [09:38:57] thanks rwaldron! [09:39:12] now all we need is a bug tracker that can show the report! [09:39:25] only took 25 seconds. [09:39:34] ahahaha [09:39:56] i can hardly wait to see timmywil fix :not(:has(:has(*))) :) [09:40:14] the key is to separate the :has from the :has:not [09:40:16] FUUUUUU [09:40:18] lol [09:40:40] :has or :has:not, that is the question [09:41:01] :is() .... :is(:not)! [09:41:09] sounds like me arguing as a kid [09:41:23] there is no :try! [09:41:47] words of wisdom from yoda [09:42:28] DaveMethvin: fyi, I just tested ie9 and got the same stop fails in effects out of focus [09:43:07] also, my browserstack seems to be unhappy testing ie6 [09:43:12] hmm, that's odd [09:43:14] but I don't think that's a jquery issue [09:43:35] maybe the ie9 was in focus, that is scary to think about [09:43:57] we need consistent unit tests! [09:44:29] hmm, maybe we could use the new visibility api and only bump up the timeouts if the browser was out of focus [09:45:37] in any case it might be a good idea to have a unitTestDelay variable rather than hard-wire all these 100ms everywhere [09:45:53] then make the other delay be a multiple [09:46:01] a few of the unit tests do define the delay as a variable [09:46:37] we can check if an animation is in progress [09:46:55] that doesn't really fix it [09:47:00] nvm [09:47:41] i think this is akin to a crazy guy trying to figure out if he is crazy [09:48:07] we aren't really sure which parts of the environment are trustworthy [09:48:42] "Delay 100ms? Sure, or something like that, maybe 1200ms, that's pretty close" [09:48:58] not exactly consistent [09:50:24] i was tryna think if i've seen the problem in other browsers, you said you just saw it in ie9 but i don't think i've ever seen it in chrome [09:50:38] and i test out of focus with it all the time [09:51:20] just ie9 and FF for me so far [09:54:26] ok, i gotta run for a few minutes, but should be in #jquery-dev most of the afternoon [09:54:30] thanks guys!