[00:00:13] RoanKattouw: mucho gracias [00:00:35] RoanKattouw: umm... where? [00:00:56] RoanKattouw: any ideas on fixing it? [00:01:11] Read scrollback, I said quite a bit about it during lunch [00:01:24] I'm too tired to explain it again :( [00:01:45] Holy crap I just discovered I've already worked 20 hours this week [00:02:02] k [00:02:04] right on [00:02:36] RoanKattouw: thank you so much for your hard work and long hours you put in this week [00:02:46] Good night guys; I don't know when I'll be around to deploy stuff, I'll send an e-mail with my availability in the morning [00:02:59] good night RoanKattouw [00:04:12] does anyone in this room speak arabic? [00:10:23] I was planning on learning it [00:10:38] katie does [00:11:25] she doesn't stop by at this room lately [00:12:05] i wanted someone who knows arabic to look at the link dialogue text/icon organization [00:12:20] but i sent email to casey if he can find someone to verify [00:17:02] pdhanda: I have a new respect for you from the last few days [00:17:12] I've been customising bugzilla for Wikimedia Australia to track tech tasks [00:35:11] haha [00:35:29] i check in the custom templates if you want a starting point [00:35:42] checked in even [00:35:57] mediawiki/trunk/tools/bugzilla-3.4.4 [00:54:42] pdhanda: ooh, thanks [00:54:59] np [00:55:22] goodnight Roan! [00:55:50] I think he's well and truly off in dreamland [00:56:12] yay [00:56:25] do you think he's dreaming of code commits?? [00:56:26] it's just about 2 RST [00:56:27] tee hee [00:56:31] I think he's dreaming of IE bugs. [00:56:58] I know I would be [16:26:56] adam_miller: Great work on the link dialogs :) [16:27:39] A few days ago I noticed that you could open the link dialog, click outside the textboxes then click Insert, and it'd insert something like [[Page title or URL]], i.e. it'd treat the tooltip as the filled-out text. Does that still happen? [16:28:09] RoanKattouw: thank you sir. it does, and I can fix that next [16:28:18] Awesome [16:28:41] i debated for a second if that was OK as our non dialog toolbar buttons insert default text if nothing is highlighted [16:28:54] My availability is not what I would like it to be these days, I'm busy reading bedtime stories and teaching my 3yo sister about the Enter button :) [16:29:02] Aah [16:29:13] I guess that /kinda/ makes sense [16:29:24] yeah, those were my thoughts too [16:29:38] it's not exactly the right text for placeholder [16:29:45] Also, IIRC the existence check got triggered on "Page title or URL" (coming up with "Page does not exist" of course) [16:30:15] k i'll look into that as well [16:35:54] hi adam_miller and RoanKattouw [16:35:59] hi hannes-_- [16:36:02] hey nkomura [16:36:14] Morning [16:36:28] i just attached the screenshot to the RTL link dialogue bug [16:36:40] i don't see the fix on arabic prototype [16:36:58] I just discovered something very interesting: apparently the government lets me keep my student support until I've actually hit the income limit [16:37:14] *RoanKattouw gains $2000 and 5-6 months of free public transport [16:37:17] RoanKattouw: that's nice [16:37:49] And they even recommend I re-request it for 2011 so I can do another half year ^^ [16:38:09] From reading their website it's almost as if they /want/ you to abuse the system and take their money [16:38:17] nkomura: did my comment make sense though? You were requesting the position of the link status icon stay the same from LTR to RTL, which we currently don't do [16:38:26] just reading it now [16:38:51] *RoanKattouw does a pre-dinner software update on prototype for good measure [16:39:39] adam_miller: yeah your comment makes sense [16:39:57] ok, i'm adding the flipped external link icon now [16:40:04] thanks [16:45:56] Software update done on prototype, I'm off to dinner [17:55:08] hi everyone [17:56:09] hannes-_- [17:56:17] tell me something hannes-_- [17:56:22] why the -_-? [17:56:53] why not hannes=D? [17:57:35] "=" is not allowed [17:58:08] that s all I can do for you, adam [17:58:23] now you just look suspicious [17:58:36] i'll take it though [17:58:48] good [17:58:53] adam_miller: how are you feeling today? i forgot to ask earlier? [17:59:04] $1,000,000.00 [17:59:13] good! [17:59:19] actually, maybe more like $750,000.00 [17:59:40] still some lingering sick-feelings, but much better [18:00:55] at least you are better than yesterday, that's good [18:05:19] how do I get thes donate box on test.wiki? [18:06:04] hannes^^: that's is experimental banner [18:06:08] i suppose [18:06:29] looks strange though I see it on paru s screenshot only [18:06:51] I would like to see it on a prototype,... is it nowhere visible currently? [18:11:21] i suppose you are talking about that bright red donate button on test.wp.org? [18:12:15] why does IRC not let me spell lunch properly? [18:13:37] adam_miller_lunc: we'll have a discussion on the toolbar at 2pm your time [18:13:55] i didn't see your confirmation to my invite [18:14:07] 11am for you/ 20pm for me, right? [18:15:39] right [18:26:36] hi RoanKattouw [18:26:40] how's it going? [18:26:56] I'm good [18:27:09] Pretty much recovered from my crazy sleeping schedule :) [18:27:12] did we merge my fixes I made yesterday before I left? [18:27:18] RoanKattouw: good to hear [18:28:21] TrevorParscal: I merged stuff at 3:50 PM, any fixes after that have not been merged [18:28:27] I left a fixme comment on CR, did you see that? [18:28:55] looking through email still [18:30:18] I like the notion of you putting out fires while babysitting... [18:30:58] There's two sources of fire there [18:31:02] Although I know it's a figurative expression, I like to think that you are babysitting little pyromaniac children who are going around starting fires [18:31:10] and you are going around and extinguishing them [18:31:26] probably with regular expressions, but possibly also with a fire extinguisher [18:31:37] hehehe [18:31:52] So I'm babysitting 3 children over here, for how many do our servers count? [18:31:53] s/fire/ashes/gi [18:32:18] 5 servers == 1 well behaved child [18:32:34] 100 servers == cadence [18:32:36] Let's hope I don't make the mistake of using s/fire/fire plus burning extinguisher/gi [18:32:47] ha ha [18:32:54] "Made in Brittan" [18:38:31] http://www.mediawiki.org/wiki/Special:Code/MediaWiki/61961#c5619 [18:40:02] I don't understand: if you remove the

completely, how will the next step magically convert them to newlines when they're already gone? [18:40:54] because in IE,

is actually

\n [18:41:09] replace( /\r?\n/g, "" ) [18:41:26] hmm [18:41:32] it seriously works [18:41:39] but indeed, i may be mistaken why [18:42:02] IE uses empty Ps for *newly inserted* lines [18:42:15] So try blanking the article and inserting "Foo\n\nBar\n\nBaz" by hand [18:42:19] hmmm [18:42:22] And check out the diff [18:42:25] yeah, i see this now [18:42:58] aka, lots of consecutive empty lines (more than 1 full empty line) turn into 1 [18:43:09] Yes [18:43:10] \n\n\n [18:43:13] becomes \n\n [18:43:14] hmm [18:43:21] as does \n\n\n\n\n\\n\n\n\n\n [18:43:31]

Foo

Bar

-->

Foo

Bar

, presumably [18:43:34] ok, so this can either be conditional for IE [18:43:45] hm [18:43:54] Why do you need to kill empty

s anyway? [18:44:33] messing with it now [18:46:25] if I don't, we end up with extra lines where we don't want them [18:46:39] but that's likely a side-effect of something else [18:46:44] messing with it now [18:46:46] still [19:03:26] when I use the search-and-replace feature to replace "\n" by "\n* ", it recognizes new lines alright, but it writes "\n" in the text instead of adding new lines. Bug? Feature? Missing regexp knowledge on my end? [19:03:50] guillom: The replace by part doesn't support any sort of syntax except $1 [19:04:07] Or $0 in your use case I guess [19:04:11] ok [19:04:31] well, I did it the old way (search/replace in my text editor) :) [19:05:01] brianmc, she's not here but someone here can answer your question, I'm sure [19:05:04] probably TrevorParscal [19:05:07] RoanKattouw: is the wikieditor intended to support IE7 in RTL? [19:05:15] Ah, thanks. [19:05:24] no [19:05:25] it's not [19:05:28] not at this time [19:05:30] layout issues [19:05:46] something we can probably fix given more hands on deck or time [19:06:02] en.wikinews has switched on Vector for all, have any other langs/projects? And, of those that have, I'd be very interested to know what percentage of registered users have forced prefs to a non-Vector skin [19:06:30] brianmc: srwikinews very recently [19:06:36] ok I was figuring there was a good reason it wasn't showing up at all [19:06:49] Nice to see the wikinews langs turning it on [19:06:51] i know on en.wikpedia there's about 200k (near half logged in users) [19:07:02] Yes, that's in the beta [19:07:50] I truly dread the vote on enwp to make the switch permanent [19:08:21] And I agree totally with Brion; the little star that spins for watchlisting a page is really cute [19:09:43] i like it too [19:09:47] :) [19:09:54] of course, i'm biased [19:10:07] lemmie guess, you coded it [19:11:11] and designed it [19:11:22] adam_miller: actually coded most of it [19:11:42] ah. brb... need to stick some chicken in the oven [19:11:46] we worked together on it to be certain [19:12:06] *cary wants to create a spinning star [19:22:21] \o/ spinning gfx ftw [19:24:38] TrevorParscal: My little 3yo sister is just like you were *sigh* it's 8:20 and she's completly awake; I just convinced her to go back to her room so she can play there instead of keep me from working [19:26:37] ha ha [19:26:40] One thing I've noticed with some of the stuff we do on enwn is it would be really useful if the drop-down menu could easily be customised - even to the extent of having sub-menus [19:26:54] RoanKattouw: I think it's VERY important that we get this line handling thing solved before we deploy [19:26:57] hello javascript. [19:27:22] TrevorParscal: Yeah so what's the Firefox problem you're poking at? [19:27:27] The IE6 The -> [19:28:21] RoanKattouw: well I have it working as of what's in trunk, but consecutive empty

tags need to be preserved [19:28:27] I'm in a design meeting [19:28:36] do you think you could look at handling that as an edge case? [19:29:03] OK just tell me how to reproduce or give me sample HTML [19:29:11] aka, 1 empty

should go away, but 2 should become 1, 3 should be come 2, etc... [19:31:14] just add new lines, some with a character on them, others without, and watch the diff [19:31:21] it's pretty easy to repoduce [19:33:00] the existing stuff in trunk works great, except that multiple blank lines turn into 1 [19:33:36] and you could take out the \s* in those expressions [19:33:46] i overlooked that it's actually a problem to have them there [19:34:05] because

is a line with a space, that's good to keep... [19:34:14] that was a mistake on my part for sure [19:35:52] OK so the \s* needs to go from the

expression and from the

expression [19:36:27] And empty

collapsing needs to die on IE at least [19:38:02] TrevorParscal: Sorry if I'm being dense but in which context are empty

s causing problems in Firefox? Does Firefox just not treat them as a line or something? [19:39:01] RoanKattouw: yes [19:39:20] in FF and other browsers, they don't put empty Ps in there to begin with [19:51:32] OK so in FF and only in FF I need to collapse one

of each sequence [19:53:14] RoanKattouw: is it safe to start messing with the hilight code? b/c it continues to get more broken for templates and I'm gonna start fixing it... [19:53:29] or attempting to [19:58:27] nimish_g: Please don't mess with trunk just yet, we wanna deploy first [19:58:37] Also, I've got some highlight fixes planned for after we deply [19:59:21] ok ::awaits IT crowd lunch in a few min:: [20:00:35] On a Thursday? [20:01:06] today's staff lunch [20:01:08] with the board [20:01:11] tomorrow* [20:01:17] so IT crowd is today [20:03:09] Ah yes [20:09:04] how's things going there? [20:10:22] I just put the kids to bed *again* :( [20:10:37] hahaha [20:10:48] We're supposed to be deploying soon - but I want to get this multi-consecutive p thing sorted [20:10:59] it could end up causing some strange diffs in IE [20:11:03] Yeah I'm committing your fix now [20:11:16] Completely untested and no idea why I was doing it, but you said to do it :) [20:11:34] http://www.mediawiki.org/wiki/Special:Code/MediaWiki/61989 [20:24:41] *RoanKattouw installs Opera [20:24:48] We seem to have a few Opera-specific bugs [20:25:13] RoanKattouw: i will test that throughoughly before we deploy [20:25:42] OK [20:25:51] I'll poke at the Opera bugs in the meantime [20:26:22] Got to do with selection.getRangeAt( 0 ) throwing errors, selection object seems to be incomplete when the selection is empty [20:39:23] YO RoanKattouw, TrevorParscal, any of my issues holding you up from deploying? i need to run out for about 45 min [20:39:49] Lemme go down the bug list real quick [20:40:57] adam_miller: You can close bug 22354, that's about inserting "Page title or URL" [20:41:25] adam_miller: bug 22376 is kinda vague and is probably a keydown vs. keypress issue [20:42:56] nkomura: Could you try to reproduce https://bugzilla.wikimedia.org/show_bug.cgi?id=22374 again and give me the line number of the error? I updated the software twice today and the line number no longer makes sense [20:43:15] sure [20:43:42] adam_miller: I assigned bug 22311 to you but it's not critical I guess [20:43:42] *nkomura actually has a window machine in the office... shhh [20:44:50] nkomura: could you also provide some more information on bug 22376, and a screenshot? Is it the placeholder text that is showing up in the link text? I'm not sure where to begin fixing it [20:45:16] adam_miller: And there's bug 22352 [20:45:16] k [20:45:26] *nkomura booting the machine [20:46:18] ughh opera [20:50:32] Ugh, turns out that whenever the cursor is on an empty line in Opera, it gives me startNode=endNode=body, startOffset=endOffset=1 [20:50:42] Regardless of which empty line the cursor is on [20:50:57] At least Firefox gives me valid start/end offsets here [20:52:33] RoanKattouw: 22374 is fixed [20:52:44] nkomura: Cool, thanks [20:53:05] one question i have is i thought the cursor is below the inserted header [20:53:14] but it goes above right now [20:53:41] That would be a case of https://bugzilla.wikimedia.org/show_bug.cgi?id=22379 [20:53:48] I'm gonna turn my attention to that one now [20:55:57] great [20:56:09] *nkomura goes to bug 22376 [21:03:07] RoanKattouw: 22352 appears fixed so I closed it as worksforme [21:03:28] OK thanks [21:03:32] *TrevorParscal is catching up [21:03:34] RoanKattouw: status? [21:03:41] I'm testing your fixes [21:03:52] I'm poking at Opera still [21:04:14] i need to run out, i'll look closer at the tabbing thing when I get back. [21:04:26] After that I intend to move on to the cursor positioning issue on insert in non-IE browsers. Currently it's always put at the start of the inserted text rather than at the end or selecting some text or whatever the previous behavior for that case was [21:04:28] that cool RoanKattouw? It doesn't seem like something we'd need to rush to include [21:04:37] Yeah that's cool [21:04:42] k be back soon [21:06:36] RoanKattouw: things are looking good [21:06:53] I'm going to try some more rigorous testing, but I think we are pretty much there [21:07:28] OK, lemme know when you feel comfortable deploying [21:14:25] mdale: you coming in tomorow? [21:14:29] staff lunch [21:14:33] we need to know about food [21:19:03] FOOD [21:19:12] GLORIOUS FOOD [21:22:44] RoanKattouw: see commit [21:22:58] brb [21:23:05] TrevorParscal: D'oh [21:25:12] :) [21:27:48] OK so this issue with Opera misbehaving when the cursor is on an empty line is partially unfixable [21:28:20] Thing is there's no way at all to determine the cursor position in that case because the W3C Range object is bogus and Opera doesn't support IE-style ranges on contenteditable [21:28:44] So I'm reworking it to not change the highlight state if for some reason beforeSelection() can't reliably determine which header we're in [21:28:59] That'll fix the bug for regular arrow key movement at least [21:30:10] TrevorParscal: hopefully [21:30:31] mdale: they will have lunch for you [21:30:36] if you don't come, I will eat it [21:30:37] I feel better now then I did last night [21:30:40] om nom nom [21:30:48] i'm back [21:30:48] good to know it won't go to waste ;) [21:31:10] TrevorParscal: Yeah I don't know why we bother with counting people, you're our trash can ;) [21:32:22] ha ha ha [21:32:36] I eat up yum yum food [21:32:44] you not eat, I eat for you [21:32:57] OM NOM NOM [21:39:09] are we ready to deploy yet? [21:41:42] *RoanKattouw passes the buck to Trevor [21:41:57] I think we can [21:42:02] I'm working on minor Opera issues, but I think we're mostly OK [21:42:33] The things I've been pushing things back on have to do with dirty diffs or unpredictable new line behavior [21:42:38] which has all been sorted now [21:43:41] I'm in favor of deploying to a small wiki, and playing with it for a day [21:43:54] the pushing out further tomorow [21:44:00] wait [21:44:04] not on Friday [21:44:11] we might push out to a couple more wikis [21:44:25] and on Monday we can push out to all - or something simila [21:44:28] *similar [21:44:30] thoughts? [21:45:42] let's deploy to usability wiki now, unless there is a blocker [21:45:48] i'm not aware of any [21:46:05] what is the opera issue you guys are talking about? [21:49:36] There's two [21:49:55] One is that when the cursor is on an empty line, Opera refuses to tell us where it is, breaking TOC highlightig [21:50:21] I'm committing a fix now that'll try to compensate for that best it can by not changing the highlighted section when the cursor goes off the radar like taht [21:50:36] The other issue is that moving the cursor in Opera doesn't wokr :( [21:51:02] wow [21:51:06] that's serious [21:51:22] Yeah [21:51:29] Hm for some reason moving the selection does work ... [21:51:58] *RoanKattouw wonders what Opera usage is at these days [21:52:40] i am looking that up right now [21:54:25] production is slow.. [21:56:54] opera distribution is a little above 2% [21:57:19] and Opera 9.6-10 combined is 0.3% [21:57:42] let's do single installation [21:57:46] OK [21:57:50] and if all goes well [21:57:55] we proceed globally [22:00:57] RoanKattouw: cam you get us pushed out to Usability only? [22:01:03] usability.wikimedia.org [22:01:04] Yes, hold on [22:01:08] take your time [22:01:16] I just committed that Opera 'fix' [22:02:04] shall we test it to make sure it didn't break something else? ;) [22:02:31] RoanKattouw: i can test if you want to update test.wikipedia.org [22:02:42] Yeah [22:02:53] I was gonna do it that way anyway: first update test, then switch on usability [22:02:55] so test, then usability [22:02:58] I'll give you a heads-up when test is updated [22:03:02] thanks! [22:10:27] OK test should be updated now [22:11:02] on it [22:13:43] TrevorParscal: Undo acts weird, not breaking, but weird :) [22:13:53] Esp. sequential undos [22:14:23] we can refine it [22:18:12] Looks good to me [22:19:41] hey guys [22:19:57] the cursor after header insertion still is at above the header [22:20:23] i'm ok proceeding as is if we can fix it later [22:21:03] otherwise it looks good to me [22:21:11] i'm going to have a quick test with opera [22:21:13] brb [22:21:31] nkomura: Yes, I didn't tackle that issue yet [22:22:25] i'm so sad that opera is faster than firefox 3 [22:25:55] cursor jumps a little wonky when i jump around sections in NTOC [22:26:17] but since we are not paying importance on Opera [22:26:23] we can proceed [22:26:29] to usability.wikimedia.org [22:26:33] OK [22:26:35] On it [22:29:02] Done [22:29:24] cool [22:29:31] *nkomura goes to check [22:30:16] so with opera heading level 4 and 5 are acting up funny [22:30:32] *RoanKattouw tries [22:31:15] Funny how? [22:31:38] they seem fine for me [22:31:48] it inserts above the last header inserted [22:32:08] That's the same as the cursor placement issue you reported before [22:32:22] no [22:32:23] After inserting, the cursor ends up before the inserted text except after in all browsers except IE [22:32:31] because this case, the cursor is below the header [22:32:33] So when you insert something again, guess where it's gonna go [22:32:36] Really? [22:32:41] really [22:32:53] i put the numbering to the header so that i can track [22:33:02] Doesn't happen for me [22:33:09] with opera? [22:33:24] Opera 10.10 [22:33:43] so there's no TOC if there's no headings in the text...if you create a heading, should we make it appear? [22:33:55] nimish_g: What do you mean? [22:34:17] Which TOC are you talking about? The navigable TOC beside the edit box is always there, headings or not [22:34:48] TOC is working great for me on Safari 4 [22:34:58] Good [22:35:04] though i'm still getting the cursor-disappearing issue when i ctrl-Z [22:35:21] I couldn't get it to appear...let me make sure it's not something silly I'm doing [22:35:54] howief: Yeah me too [22:36:22] TrevorParscal: Ctrl+Z in Firefox and apparently also in Safari causes the cursor to disappear and the next Ctrl+Z to do weird things. Suggest context.$iframe[0].contentWindow.focus(); [22:36:49] hmm [22:37:53] working good for me on FF3 [22:38:11] i haven't tried the ctl-z, but in general [22:38:46] hmmm i get the same behavior in chrome [22:38:51] undo is a strange thing to visualize in your head... [22:39:21] I get the edit warning after undo [22:39:29] do we think that the undo we've implimented is worse than the not so great browser provided one? [22:39:56] I think it's more predictable than the browser one actually [22:41:11] nimish_g: EW on udno --> can't reproduce [22:41:16] i've actually never pused the browser provided undo [22:41:29] played [22:42:23] I'm using ff3.5, I just press ctrl+z [22:42:43] hmm [22:42:44] it seems like we are not at the right part of the stack sometimes [22:43:05] i'm using ff 3.6 and it seems like the browser undo is a little more predictable [22:43:07] the stack needs to be updated less often [22:43:31] and we need to always save state upon undo - since it's possible to add something and then undo before a state save [22:44:02] also, there's the whole cursor moving to the begning issue, which we know of but never fixed [22:44:17] we can either fix this up, or comment it out for now [22:44:40] I say we disable it on the live site [22:44:41] I'm in favor of commenting out and making a more robust undo system later [22:45:00] Yeah, it's close, but it needs some obvious improvements [22:45:11] RoanKattouw: it's pretty simple to comment out [22:45:18] TrevorParscal: can i show you a strange heading behavior with opera on my computer? [22:45:30] sure - do you want me to come over? [22:45:30] OK will comment out in the branch [22:48:37] the opera bug she's seeing is that opera always puts headings at the begining [22:48:52] it has to do with loosing focus when you click on the heading drop down [22:48:59] and thus loosing cursor position [22:49:02] Which version of Opera? Doesn't happen for me [22:49:07] (Opera 10.10) [22:49:11] it's the most recent one [22:49:13] the cursor is restored after the operation [22:49:14] lemme look [22:49:20] but it was wrong durring the operation [22:49:20] i just downloaded it [22:49:32] help -> about? [22:49:47] 10.10 on Windows 7 [22:57:12] got unresponsive script error while working on NTOC [22:57:20] the doc is longer than 32kb tho [22:57:29] I blame people who live in Washington state, in general [22:57:55] why? [22:57:56] I disabled undo on test&usabilitywiki, please test [23:01:17] i can still undo with FF3 [23:01:26] nkomura: i'm just joking [23:01:30] i did shift+refreshh [23:01:33] refesh [23:02:40] Yeah that's in-browser functionality probably :) [23:02:53] Sorry about that, can't really test whether Trevor's undo code is disabled [23:03:09] Lemme just confirm that the wierd cursor jump thing doesn't happen any more [23:03:17] Yup looks good [23:03:22] yeah [23:03:38] you disabled both saving the states and also restoring them right? [23:03:58] cursor looks good [23:04:01] no need for the performance hit of saving the states on delayedBind:realChange [23:04:05] howief: can you test again? [23:04:18] you need to reload [23:04:33] we should make it so if you click on anything it closes the heading drop down... [23:04:35] should be easy [23:04:42] document.click() or some such [23:04:51] ok testing now [23:05:37] argh [23:05:41] i shouldn't have spoken so soon [23:06:07] cursor moving bug is fixed in opera! [23:06:18] Yay [23:06:21] TrevorParscal: you are ninja! [23:06:22] nimishf was right - the browser ctrl-z behavior within the editing window is even worse [23:06:54] howief: hence why we were hoping to improve on it [23:07:05] some browsers do have better behavior than others [23:07:17] soon we will have consistent and improved behavior [23:07:35] RoanKattouw are you going to bed now? (shouldn't you?) [23:08:02] I should go to bed soon, yes [23:08:10] Do you guys wanna deploy site-wide? [23:08:49] If so, I'd like to do that sooner rather than later [23:09:55] yes [23:09:56] do it [23:10:01] and if all hell breaks loose [23:10:05] you will be asleep [23:10:16] dreaming of bug reports [23:10:48] Yeah [23:28:24] *nkomura got back from the mtng [23:28:42] hi naoko [23:28:54] so we are live? [23:28:57] Not yet [23:29:06] hi werdna [23:37:01] Here we go *crosses fingeres* [23:38:07] crossing my fingers [23:39:44] i'm seeing the old toolbar... [23:39:51] going to check my preferences [23:39:52] Bleh messages messed up [23:40:04] woops [23:40:45] preferences are enabled for the enhanced toolbar [23:42:37] RoanKattouw: I won't screw you up if i commit new code now, right? [23:42:47] No, go ahead [23:44:02] let me know when i should check back again [23:45:30] production got really slow [23:47:38] OK we seem to be live now [23:47:46] wheeee [23:48:43] NG!!! [23:48:53] the toolbar text is all screwed up [23:49:18] <wikeditor-somestuff> ? [23:49:40] something like that [23:49:48] How do I see the new stuff? [23:49:54] some are overlapping [23:50:03] Hold on [23:50:22] OK try now [23:50:30] this time it's good [23:50:35] Thought so [23:50:38] maybe a glitch in updates [23:50:39] What's new? :) [23:50:41] phew.... [23:50:42] werdna: Through the regular opt in system [23:50:50] I don't see anything different [23:50:53] nkomura: Yeah, it was caching an old JS file [23:51:15] mpw o [23:51:27] werdna: We use a content-editable iframe now instead of a textarea. Improved NTOC, improved toolbar dialogs [23:51:50] now i'm seeing a block of gray area in the bottom half of the text edit area [23:52:45] refreshing is not helping [23:52:50] Oh and the TOC is busted, that's my fault [23:52:57] I don't get the grey box though [23:53:17] the right alignment is pushed out [23:56:35] OK it all works for me now [23:56:45] TOC works and I don't see a grey box [23:56:46] i think it is related to busted NTOC [23:56:48] *nkomura goes to look [23:57:30] NTOC is at the bottom now... [23:57:42] Huh> [23:57:57] Works fine for me [23:58:02] it may be still updating [23:58:09] let me refresh a few more times [23:58:11] Nope it's done [23:58:15] Try Shift+Refresh too [23:58:36] Oh please make sure you don't have AMW enabled [23:58:55] no love [23:59:07] wikis are all broken for me; i blame you [23:59:26] Although that doesn't seem to matter for me [23:59:28] guillom: Broken how? [23:59:33] which ones are you trying guillom? [23:59:41] won't load [23:59:48] well, fr.wp, en.wp, fr.wv [23:59:59] commons