[09:01:35] Hi! [09:01:59] <_markelog> hey [09:02:07] hey! [09:02:22] I have a FirefoxOS feature that I need to wrap up today (mid review) so ping me if there is any discussion re: the data-as-expando patch [09:02:46] ok, i pushed it off to the 2.2 version [09:02:49] Rad [09:02:58] I need to rebase [09:03:01] freebase [09:03:03] present [09:03:04] * rwaldron shrugs [09:03:04] rwaldron: ¯\_(ツ)_/¯ [09:03:54] i think we have the tickets down pretty low right now, which is good [09:04:25] I see new browsers in TestSwarm :) [09:04:34] that's not good! [09:04:38] :) [09:04:47] IE11 & Safari 7.0 still missing, though [09:04:48] ;) [09:05:08] Chrome 31 Ajax fail [09:05:19] the chrome 31 fail on ajax is due to that known chrome bug [09:05:24] yeah, right [09:05:29] which is annoying [09:05:33] it's fixed already [09:05:35] AFAIK [09:05:46] NOT IN CHROME 31! :) [09:05:53] but BrowserStack doesn't update its browsers [09:05:56] not? [09:05:57] :( [09:06:27] the latest released version is 31 right now [09:06:39] canary is 33 [09:07:00] yeah, I know, but they tend to backport more critical bugs [09:07:38] for some reason they didn't fix this for a while, it was reported long ago [09:08:42] i was gonna verify it was fixed on canary but i can't even get the tests to start on mylocalhost [09:09:39] works fine on my Canary [09:09:46] and fails on stable [09:09:56] well good i guess [09:10:03] dunno why my canary is barfing [09:10:04] we should mark it as an expected failure specifically for Chrome 31 [09:10:07] seems to be bothered by localhost [09:10:12] dunno about 32 [09:10:19] to not get these errors all the time [09:10:29] yes [09:11:05] hullo hullo [09:11:09] hey gibson042 [09:12:05] okay, all 1.11/2.1 tix are currently assigned [09:12:45] timmywil has 4, i have 3, m_gol and gibson042 have 1 each [09:13:15] everybody okay with their assignments [09:13:16] ? [09:13:17] I'd like to get all the tests to pass on iOS7 and include it in TestSwarm then [09:13:23] but probably not before the 3rd beta ;) [09:13:39] well the sooner the better [09:14:28] lets look at pulls [09:15:01] it's not bad, we're failing only 2 tests on iOS7 [09:15:12] and those are prob safari bugs [09:15:28] i know we had a couple of tickets reporting bugs [09:16:02] so https://github.com/jquery/jquery/pull/1459 [09:16:21] not sure about the background on this one [09:16:37] but it needs some explanation and tests if it should stay [09:16:42] and i wouldn't do it as a prefilter [09:16:53] should we kick this to jaubourg for review? [09:17:09] <_markelog> i think the guy should rebase this [09:17:18] <_markelog> it has a lot of needless noise [09:17:30] well that too but i was more worried about the why at this point [09:17:39] he did it off the release tag which is wrong [09:17:44] jaubourg suggested a prefilter approach here: http://bugs.jquery.com/ticket/13240#comment:11 [09:17:49] yes [09:18:18] right but i think that was assuming we wouldn't land anything? lemme read that [09:18:26] <_markelog> activeX also supports other non-standtart methods [09:18:51] <_markelog> so i don't we should make a path request a special case [09:19:20] <_markelog> *patch request [09:21:15] this patch tries to do activex on all browsers? [09:21:43] it seems so :) [09:21:56] DaveMethvin: no, it's in an `if ( window.ActiveXObject )` block [09:22:21] but is definitely not a form in which we'd solve this problem [09:22:34] which means it wont run in ie11 ... is that good or bad? :) [09:23:10] for now, markelog's comment is fine, let's see if they come back to do that [09:23:30] IE11 has native PATCH support, the fix is for IE8 [09:23:54] yeah i just didn't know when that occurred...ie9 was okay then? [09:23:57] I added more links in a comment [09:24:29] <_markelog> i would actually do it in reverse if it is one of methods that supported in IE xhr - use xhr if - not use activeX, if it available [09:24:33] feature testing this stuff is tricky since there's no direct feature test [09:24:53] <_markelog> we don't need to feature test it [09:25:06] <_markelog> ie xhr has support for handful of http methods [09:25:23] <_markelog> they use - is an edge case [09:25:25] also supports local files [09:26:00] https://github.com/jquery/jquery/pull/1458 looked good [09:26:35] <_markelog> :-) [09:26:41] yup [09:26:46] thanks for that _markelog [09:27:01] I was trying out shrinkwrap as well but it's pretty broken now [09:27:14] <_markelog> hm, broken? [09:27:35] yeah i saw your comments on twitter m_gol [09:27:47] btw https://github.com/jquery/jquery/pull/1457 looks good too [09:27:50] yeah, not stable (as in: running it twice doesn't produce the same output), if you don't clean it up it still triggers additional requests, sometimes it mishandles GitHub handles etc. [09:28:25] that's not good [09:28:30] I'd love to use it if it worked as it should because just locking versions in package.json doesn't protect us from grunt task dependencies breaking in patch releases [09:28:45] well we [09:29:01] re never completely protected if we use any "global"tools [09:30:01] https://github.com/jquery/jquery/pull/1455 imma just gonna fix that and give a shout out to tcort [09:30:35] DaveMethvin: would you be open to using this in our setup? https://npmjs.org/package/grunt-check-dependencies [09:31:00] I can create a pull request for testing if I have at least a yellow light ;) [09:31:23] it would be worth having i think ... i worry about npm install when i switch between branches [09:31:35] I was looking at other solutions [09:31:36] we've been close enough that usually it doesn't matter [09:31:44] but one day i will be bitten i know [09:32:09] there is https://npmjs.org/package/grunt-check-modules [09:32:14] but it just runs `npm ls` [09:32:17] and that's not enough [09:32:24] _markelog do you want to look at that activex patch? [09:32:30] it doesn't e.g. catch not matching depenencies [09:32:36] <_markelog> i already did [09:32:38] ok, I'll just prepare a PR and we'll see :) [09:32:57] i meant, potentially write a fix if this guy can't [09:33:07] <_markelog> if we want to fix it, what damage could we afford? [09:33:38] you mean, like when we use it at the wrong time? [09:33:39] <_markelog> do we want in beta-3? [09:33:54] <_markelog> i meant size diff [09:34:08] oh, i'm not sure [09:34:39] i don't have a good feel for how big it would be [09:34:49] <_markelog> okay, i will try to make a fix on this week [09:34:57] <_markelog> we can go from there i suppose [09:35:00] there would seem to be some trickiness to get it only applied where needed [09:35:29] <_markelog> it might be, but it looks pretty simple right now [09:35:37] if we could get it into beta3 that would be good, otherwise i'd push to 1.12 [09:35:49] since i'm hoping we don't have a beta4 [09:35:53] :) [09:36:02] <_markelog> maybe test would uncover something, it's IE so you never know Ж-) [09:36:18] <_markelog> yeah all right [09:36:31] lol yeah [09:36:59] _markelog were you going to land https://github.com/jquery/jquery/pull/1449 [09:37:26] <_markelog> i would wait until 2.2, it's pretty big change if you think about it [09:37:53] oh thta's right [09:38:01] i forgot to mark these [09:39:01] I'll mark this one test as an expected failure in Chrome 31 [09:39:42] yeah that is fine [09:42:05] can we just give up on https://github.com/jquery/jquery/pull/1421 ? [09:42:34] i like small code but this is just a pain [09:43:17] we have a lot of commits like that... [09:43:24] speaking from experience, this guy spend a lot of time to do this [09:43:47] -18 seems pretty nice [09:44:13] DaveMethvin: what are your concerns? [09:44:40] I don't see a compelling reason *not* to land it [09:44:53] m_gol: -19 :-) [09:45:20] and it's stale mostly because we didn't respond to the latest comment of the guy [09:45:22] is it stale now? [09:45:23] oh [09:45:31] okay, well who wants to land this? [09:45:56] I'll do it [09:46:15] done [09:47:23] what do you guys think about https://github.com/jquery/jquery/pull/1429 [09:47:24] I can land https://github.com/jquery/jquery/pull/1436 [09:47:32] timmywil & markelog seemed to agree on it [09:47:39] coo [09:47:42] cool even [09:48:43] i really am not a fan of having Callbacks exposed at all but i'm also not sure about the utility of .forget() [09:49:04] i'm do not actually, i'm neither [09:49:39] it's only a line but i'd rather people don't use it :) [09:49:46] well, the fact is it is exposed ;) [09:50:20] we've had exactly one request for this feature in all the time it's been exposed [09:50:29] so that doesn't sound like a big number to me [09:50:34] yeah, right [09:51:22] I don't get the example under http://bugs.jquery.com/ticket/14542 [09:51:58] well i think it would be the case of "somethng happened and i don't want to do anything anymore" [09:52:37] i can see the use case but am not sure that Callbacks were the right solution in the first place [09:53:22] when I've looked at using them either they were too complex for my use case or not flexible enough [09:54:17] let's just push this off to 1.12/2.2 [09:54:19] I haven't actually used them directly, I prefer to just use promises [09:54:58] okay, any other stuff we shoudl discuss for beta3? [09:55:10] should be doable by thursday i think [09:55:23] although timmywil has several tickets and i'm not sure where he is on those [09:55:59] alrighty then, let's call it a meeting [09:56:03] thanks guys!