[00:19:13] New patchset: awjrichards; "Fix titles with formatting" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5294 [00:19:14] New patchset: awjrichards; "Change name of file to jquery.min.js remove the version reference" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5295 [00:19:15] New patchset: awjrichards; "Pass RequestContext" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5296 [00:19:15] New patchset: awjrichards; "Restore message lost in merges and refactorings" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5297 [00:19:16] New patchset: awjrichards; "Localisation updates from http://translatewiki.net." [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5298 [00:19:57] preilly: when merging from master -> remote branch, is it better to squash the merged commits into one or just push all the merged commits as individual commits? [00:52:57] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (contact-us-redesign); V: 1 C: 2; - https://gerrit.wikimedia.org/r/5298 [00:53:02] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (contact-us-redesign); V: 1 C: 2; - https://gerrit.wikimedia.org/r/5297 [00:53:06] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (contact-us-redesign); V: 1 C: 2; - https://gerrit.wikimedia.org/r/5296 [00:53:13] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (contact-us-redesign); V: 1 C: 2; - https://gerrit.wikimedia.org/r/5295 [00:53:17] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (contact-us-redesign); V: 1 C: 2; - https://gerrit.wikimedia.org/r/5294 [00:53:20] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5298 [00:53:21] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5297 [00:53:22] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5296 [00:53:23] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5295 [00:53:25] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5294 [10:07:23] * YuviPanda looks around [10:27:45] YuviPanda: are we ready to merge yet? [10:28:14] good spot on the ios typo [10:31:13] jdlrobson: heya [10:31:18] jdlrobson: I think so. [10:31:32] jdlrobson: want to look over the commits once more? [10:31:35] we're close to a hundred :) [10:31:59] https://github.com/yuvipanda/WikipediaMobile/tree/api-move yeh? [10:32:15] jdlrobson: or https://github.com/wikimedia/WikipediaMobile/pull/208 [10:32:16] sae thing [10:32:17] yeah [10:32:21] did you say ics had choppy fixed positioning still? [10:32:33] jdlrobson: it wasn't really 'choppy' [10:32:48] jdlrobson: essentially, *while* scrolling, the search bar moves down a pixel or so [10:32:52] and when you stop it goes back [10:33:04] mm i wonder why that is [10:33:18] it feels like the 'kinetic scrolling' algorithm is being applied to it as well [10:33:28] if I scroll faster, i see more movement [10:33:34] (more than a few pixels) [10:34:53] only suggestion so far is you might want to git rebase interactive and fixup https://github.com/yuvipanda/WikipediaMobile/commit/ceb8177d193811b65e9e408581fbc2527c772b0a [10:35:42] I'm guessing that's okay, not sure we should be 'hiding' mistakes behind squashes [10:37:00] same with https://github.com/yuvipanda/WikipediaMobile/commit/c7658c65824eea7d630dbfa511b63e8c2328d743 [10:37:23] well these mistakes are just sloppy and i don't think add anything to the commit log [10:37:32] apart from make it harder to follow [10:37:39] imo [10:37:57] but that aside i think we're good to merge [10:38:07] this is the 'history is sacred' vs 'that is pointless' bikeshed (of sorts) [10:38:31] jdlrobson: \o/ [10:38:37] jdlrobson: accept the pull req and merge it in? [10:38:58] wait let me do a rebase [10:39:07] k [10:39:13] ping me when it is time [10:39:58] jdlrobson: brion has made a few changes to master that're preventing a clean rebase :( [10:40:10] investigating [10:40:11] \o/ [10:40:18] gonna have lots of fun with those existing pull requests :D [10:43:12] heh [10:43:15] jdlrobson: rebased and pushed [10:46:34] sorry 1s just fixing a MFE bug [10:46:40] ok :) [10:48:32] k looking into it now [10:48:39] the bug effected the app as well [10:48:39] https://twitter.com/#!/Shaddez/status/192455772901347328 [10:49:21] my h1b got approved yesterday btw [10:49:23] \o/ [10:49:25] \o/ [10:49:50] jdlrobson: congratulations :) [10:50:07] still no physical visa... have to go to embassy for that. i'm not sure where that puts me in terms of eta but guess things are going to go really quickly now [10:50:25] right ICS testing first [10:50:52] that's an MFE bug? [10:51:02] mobile frontend [10:51:03] sorry [10:51:17] yeah, but was wondering how that'd be a MobileFrontend bug [10:51:24] unless you meant the 'two line looks weird' bit [10:52:27] well i think it might be due to common.css [10:52:35] it's present in the mobile site too [10:52:38] so when i click settings i lose my scroll position in an article - is that normal [10:52:57] right. no it isn't normal [10:53:05] that's because we're doing window.scrollTo [10:53:10] instead of $(content).scrollTop [10:53:13] we should start writing unit tests for these sorts of things [10:53:48] yeah [10:53:57] should be easier to do so now, than before (which depended too much on DOM) [10:54:34] also save page seems to be broken.. [10:54:38] yes it is [10:54:42] i've not started work on it [10:54:48] k as long as thats known [10:54:56] actually weirdly it saved [10:55:00] but didn't tell me it saved [10:55:37] so, half the code is there. but it doesn't take into account dynamic DOM loading, and so images in sections not expanded won't be saved [10:55:40] also did we decide what to do about MediaWiki:Common.css ? [10:55:44] no [10:56:07] jdlrobson: it's different for every language wiki, so I don't think we can get away with including a static version of it [10:56:18] doh [10:56:27] ok i'm gonna merge [10:56:28] so, yay to app breakages because of CSS changes from other people? [10:56:54] i'm wondering how to deal with MediaWiki:Common.css. They might easily conflict with app styles... [10:57:11] we might have to namespace classes/ids used in the app then... [10:57:12] just a thought... when i merge [10:57:16] irc is going to go crazy [10:57:21] hehe [10:57:43] just doing a bit more ios testing [10:57:45] (4.2) [10:57:52] ok [11:00:42] mm ios 4.2 isn't working at all [11:00:53] let me reboot xcode [11:01:23] seems fine on my sim? [11:01:24] ok [11:06:43] ahh i was running from wrong respository :D [11:06:50] so yeh ios doesn't have the scroll problem [11:06:51] :D [11:06:59] (when i load settings it keeps my place in the article) [11:07:09] jdlrobson: so, as I said - that is because we're using window.scroll [11:07:19] k as long as we know how to fix it :) [11:07:26] its looking awesome [11:07:30] ready for irc to go crazy? [11:07:35] indeed sir! [11:08:09] ! [11:08:30] mm [11:08:32] [WikipediaMobile] jdlrobson pushed 93 new commits to master: http://git.io/eORvZQ [11:08:32] [WikipediaMobile/master] Initial cut of pages being rendered via the API - YuviPanda [11:08:32] [WikipediaMobile/master] Get rid of the tree-conversion code - YuviPanda [11:08:32] [WikipediaMobile/master] Added MFE as a Submodule - YuviPanda [11:08:33] where's the madness? [11:08:35] ah there [11:08:41] heh [11:08:42] oh wait [11:08:45] not yet [11:08:49] it's jenkins that'll go mad [11:08:49] Project WikipediaMobile - Nightly builds build #348: SUCCESS in 9.2 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/348/ [11:08:50] * yuvipanda: Initial cut of pages being rendered via the API [11:08:50] * yuvipanda: Get rid of the tree-conversion code [11:08:51] * yuvipanda: Added MFE as a Submodule [11:08:51] * yuvipanda: Top level toggling works [11:08:52] * yuvipanda: Temperoarily hide extra header [11:08:52] * yuvipanda: Added Patch file needed to make MF work with app [11:08:53] * yuvipanda: Move back to local version of MF's application.js [11:08:53] * yuvipanda: Make only h2 collapsible [11:08:54] * yuvipanda: Drop the .m prefix [11:08:54] * yuvipanda: Don't depend on history for current URL [11:08:55] * yuvipanda: Spacing fixes [11:08:55] * yuvipanda: Refactor to make page's source more generic [11:08:56] * yuvipanda: Refactor page to be language independent [11:08:56] * yuvipanda: Redid Saved Pages to work with Page objects. Broken in iOS [11:08:57] * yuvipanda: Fixes to make RTL languages display as RTL [11:08:57] * yuvipanda: Make Language Links work via the API [11:08:58] * yuvipanda: Fixes to make loading read-in not painful [11:08:59] muahhaha [11:09:09] * yuvipanda: Added warning about code in comments [11:09:09] * yuvipanda: Fixed bash misunderstanding [11:09:10] * yuvipanda: Open attribution links under maps in external browser [11:09:10] * yuvipanda: Make sure that 'Show more results' is visible [11:09:11] * yuvipanda: ReadItLater issues fixed by changing modal presentation targets and eliminating previous ex nihilo method. Associated issues also fixed. Completing registration needs testing with a working RIL API key. [11:09:11] * yuvipanda: Added Rolken to AUTHORS [11:09:12] * yuvipanda: Support all orientations for RIL on iPad [11:09:12] * yuvipanda: Fix scrolling after orient change on iOS 4.x [11:09:13] * yuvipanda: Increasing keypress timeout to 300. Works better on iPhone3G [11:09:13] * yuvipanda: Fix for saved pages never persisting [11:09:14] * yuvipanda: Does not crash on 2.x -> 3.x app upgrade [11:09:14] * yuvipanda: Use noheadings in API call [11:09:15] * yuvipanda: Add elements to the DOM only on section expansion [11:09:15] * yuvipanda: Updated to latest commit on MF [11:09:16] * yuvipanda: More 'Proper' Section expansion implementation [11:09:16] * yuvipanda: Fixes to work with iScroll [11:09:17] * yuvipanda: Add hide buttons too to sections [11:09:18] * yuvipanda: No more zepto. [11:09:21] best log ever [11:09:24] more tings [11:09:29] * yuvipanda: Override scrollTo on android [11:09:29] * yuvipanda: Working badly hacked version of scrollTo for android [11:09:30] * yuvipanda: Removed all traces of doScrollHack [11:09:30] * yuvipanda: fixes for Ice Cream Sandwich android 4.* [11:09:31] * yuvipanda: remove unnecessary show/hide [11:09:31] * yuvipanda: Add detector classes to html element [11:09:32] * yuvipanda: Remove stray alert [11:09:32] * yuvipanda: Use jQuery to set classes instead of plain js [11:09:33] * yuvipanda: device specific fixes for android 2 [11:09:33] * yuvipanda: append missing semi colons [11:09:34] * yuvipanda: fixed ICS bug with content flashes [11:09:34] * yuvipanda: prevent horizontal scrolling in android ics [11:09:35] * yuvipanda: separate ios specific css interfering with android ics [11:09:35] * yuvipanda: only apply overflow-y to ios devices [11:09:36] * yuvipanda: Fix iOS 5.x scrolling [11:09:41] huzzah [11:09:44] all done [11:09:49] \o/ [11:10:03] now to go fix another scroll bug :) [11:10:07] so i'm keen to get https://github.com/wikimedia/WikipediaMobile/pull/210 merged - could you have a quick poke at it and my comments before doing that? [11:10:18] i expect lots of rebasing will now be required [11:10:29] jdlrobson: yes, and i'm not sure if I'd want to do it for 1.2 [11:10:40] why not? [11:10:49] since we have too much already? :) [11:10:56] yes :) [11:11:10] very sensible [11:11:16] i'm a sucker for new shiny things [11:11:18] i'd want this in 1.3, along with moving off geonames into the API [11:11:24] don't you mean shiny new bugs? [11:11:25] :D [11:11:43] nothing shiny about those! :PP [11:11:43] so I'm wondering how to deal with pull requests that we want to do 'later' [11:21:14] merge into a branch e.g. 1.3 ? [11:22:51] jdlrobson: but then that branch will have to be kept in sync with master [11:23:16] well lets use labels then.. [11:23:56] makes sense [11:23:58] done [11:24:11] annoyingly those don't show up in pull requests [11:24:13] just issues [11:24:28] we should respond to https://github.com/wikimedia/WikipediaMobile/issues/202 [11:25:25] was just looking at that [11:26:10] jdlrobson: also https://github.com/wikimedia/WikipediaMobile/pull/198 [11:26:10] ? [11:27:21] yeh what's your thoughts on that [11:27:36] well, we 'fixed' that on iOS [11:27:41] we did? [11:27:43] but not a fan of the approach taken here [11:27:51] jdlrobson: yeah, iOS no longer shows the navbar when on overlays [11:27:53] it just seems weird [11:28:00] yeh hiding the nav bar would make more sense [11:28:03] but you can't do that in android [11:28:10] yes [11:30:08] jdlrobson: the new code has setCurrentPage and setErrorPage, and I think it can be handled there. [11:30:19] haven't thought about that yet, currently figuring out how to do saved pages properly [11:30:27] k [11:30:30] jdlrobson: closing that pull request seems to be the way to go for me. [11:30:40] in terms of saved pages.. [11:30:50] why not just do one big additional ajax request for all of it [11:30:57] go for it then YuviPanda [11:31:07] jdlrobson: ahem, that's what we're doing now :) [11:31:14] jdlrobson: problem is images. [11:31:17] and where to save them [11:31:21] ah i see [11:31:25] well can base64 them... [11:31:28] so [11:31:31] that's what we're doing on iOS :) [11:31:34] :) [11:31:44] android doesn't support that on 2.x [11:31:45] oh wait [11:31:50] maybe we can get the API to do this for us [11:31:55] hmmm [11:31:56] :D [11:32:16] i'm not sure though [11:32:24] jdlrobson: thoughts on that idea? [11:32:45] jdlrobson: i'll note that the usual way of converting to base64 from canvas is what we're using on iOS. It seems to cause some perf problems [11:32:46] 2.x doesn't support base64? [11:32:51] jdlrobson: it does. [11:32:55] mm [11:32:58] it doesn't support converting images to base64 via canvas [11:33:13] i guess the question is are images essential offline [11:34:05] why not as a first pass forget about them and get offline working that aside [11:34:09] I'd say they are - it'd look broken otherwise? [11:34:21] plus we've been supporting that already, and you know how much people love having features taken away [11:34:26] ok [11:34:27] mm [11:34:56] though *I* am a fan of killing saved pages though :) [11:35:36] jdlrobson: we're including clicktracking to see how many people use that [11:35:58] well there seem to be 2 options - api base64s them on your behalf or we do it client side using canvas [11:36:23] alternatively we could look into the file api but i'm not sure if that works with phonegap [11:36:28] jdlrobson: client side using canvas is not doable on android 2.x [11:36:31] hmm [11:36:48] jdlrobson: so, on iOS we use the file API + canvas conversion [11:36:53] jdlrobson: so we save a single file. [11:37:05] so wait a minute android 2.x never had images saved offline? [11:37:15] jdlrobson: android has a java plugin that does the saving [11:37:26] while iOS is all js, uses canvas + file API [11:37:45] it's messy super-platform specific code [11:37:48] yeh [11:37:50] i hate that stuff [11:38:01] sure we can't take it away from 2.x ? [11:38:26] i'd want to take it away from all of them :) But not for this release - tfinc loves saved pages. [11:38:27] if they have an internet connection they can still get the images [11:38:51] i'm also worried about localStorage limits with images [11:39:14] jdlrobson: we're not using localStorage [11:39:28] we're using localStorage only for boolean/simple-string settings [11:39:35] jdlrobson: all our saved pages are done via files [11:39:40] ok.. sorry i've not really explored the offline code much as you can see [11:39:49] will have to explore [11:40:05] jdlrobson: i think having the API itself give us bas64 would be awesome [11:40:07] * YuviPanda pokes MaxSem [11:47:48] jdlrobson: https://code.google.com/p/android/issues/detail?id=7901 [11:49:58] eek "Still no support for jpeg (tested on icecream sandwich)" [11:50:02] so yeh canvas is out [11:50:12] jdlrobson: and no support for jpeg on iOS either. [11:50:19] jdlrobson: we're converting to PNG before saving on iOS right now [11:50:25] so eek [11:50:30] eek indeed [11:52:27] jdlrobson: I think getting base64 from the API would be awesome [11:52:47] sounds like it would take a lot of processing power [11:54:01] i'm guessing MaxSem would know [11:54:16] jdlrobson: also, the APi does not handle things in the File: domain currently [11:54:28] jdlrobson: this means that we need to now build our own Image handling code [11:54:33] i.e. what to do when someone taps an image [11:56:10] mm [11:56:18] filed as https://bugzilla.wikimedia.org/show_bug.cgi?id=36036 [11:56:31] I could just punt them to the browser for this release [11:56:45] but seems icky [11:59:46] New patchset: Jdlrobson; "simplify border rule into single line" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/5312 [11:59:46] New patchset: Jdlrobson; "prevent long search inputs forcing a new line" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/5313 [12:05:59] yuvi - can you not use an images intent? [12:08:55] jdlrobson: on android, yes [12:09:24] oooh, actually - you can't do that without saving it on file :) [12:13:37] Project WikipediaMobile - Nightly builds build #349: SUCCESS in 7.5 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/349/ [12:28:13] New patchset: Jdlrobson; "style errors better" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/5316 [12:29:30] New review: Jdlrobson; "A few outstanding problems" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) C: 0; - https://gerrit.wikimedia.org/r/5316 [12:40:18] who poked meeeee? [12:40:34] It was I, master! [12:41:16] MaxSem: thoughts on API that gives us base64 representations of files? Or better yet, an option to mobileview where it converts all images into data URIs so that it doesn't need additional requests [12:41:16] ? [12:41:46] mmm [12:42:03] are single requests so slow? [12:45:26] Project WiktionaryMobile - Nightly builds build #91: SUCCESS in 7.2 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/91/ [12:45:37] MaxSem: no [12:45:40] this is for our 'saved pages' feature [12:45:54] so we're just wondering how feasible this will be on the server side [12:46:12] at least, not easily [12:47:19] it would require either hooking up to parser or magic remapper of URLs back to FS paths or fetching of images via HTTP [12:47:36] that sounds ugly. [12:48:44] parser doesn't provide us with sizes of all thumbnails involved [12:48:53] just which images are used on page [12:49:30] MaxSem: or adding a data property to action=query & prop=imageinfo [12:49:37] that gives us the data as well? [12:49:37] so the answer is yes it's possible but not as a quick hack like action=mobileview which was created in one evening [12:49:41] hmm [12:50:01] MaxSem: i guess this would be just as messy (fetch over HTTP, base64, return) [12:50:41] there's such thing as remote repos e.g. Commons [12:51:00] for them everything's e ven more fun [12:51:21] yes, that 'idea' went downhill pretty fast :) [12:51:54] well, the idea actually makes sense but requires design and planning [12:52:26] New patchset: Jdlrobson; "use one button for toggling" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/5319 [12:52:27] yeah, and I'm not sure how much of a benefit it'll give us [12:52:29] ^ YuviPanda [12:52:36] \o/ [12:55:01] YuviPanda: any thoughts on references? [12:55:21] jdlrobson: so, if we load the references section into the DOM by default [12:55:32] I think the reference reveal code from MF should work unmodified (mostly) [12:55:54] i'm going to update the references code to take a parent element in the init [12:56:15] it currently does $( 'sup a' ).unbind('click').click( clickReference ) [12:56:23] should probably do $( 'sup a', parent ).unbind('click').click( clickReference ) [12:56:43] otherwise lots of needless rebindings [12:56:47] hmm, that should help with loading it on every section reveal [12:57:49] ill make the change and send to you for review [12:58:14] jdlrobson: okay! [13:14:32] New patchset: Jdlrobson; "allow initialisation function to target a specific element" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/5320 [13:17:43] brb [14:06:00] hi guys [14:06:33] is the mobile app setting an explicit user agent as of 1.0.3 for both the android and the ios version? [14:07:58] diederik: yes [14:08:26] thanks! [14:08:41] when was 1.0.3 released? [14:15:25] diederik: quite a while ago - almost two months. I could check the exact date if you want me to... [14:15:31] diederik: iOS was much more recent though [14:15:52] i am most interested in the release date of iOS [14:16:18] * YuviPanda hunts for exact date [14:16:26] thanks [14:16:32] roughly a week and a half ago, looking for exact date [14:16:52] diederik: ~Apr 5 [14:17:00] about two weeks ago [14:18:05] thanks! [14:18:22] diederik: :) [14:18:33] can you give me an example of such a user agent string? [14:19:15] diederik: essentially, we just prepend WikipediaMobile/ to the actual device's User agent [14:19:30] okay [14:19:35] so the user agent differs for each device/OS combo, but will be prefixed with WikipediaMobile/ [14:19:43] cool [14:19:50] again thanks :D [14:24:03] MaxSem: is your samsung jet handy? https://bugzilla.wikimedia.org/show_bug.cgi?id=30829 [14:24:56] MaxSem has a Jet? [14:25:32] jdlrobson, I lookd at it immediately after it was pushed [14:26:00] but what was the result [14:26:01] ? [14:26:32] with images disabled can you see the search button? [14:33:42] hmm, mobile-geo looks dead [14:34:18] memcached went offline? [14:39:31] hahaha $wgMemCachedTimeout = 500000; [14:41:45] dammit, bot funny [14:41:49] *not [14:42:00] it doesn't work anyway [14:47:12] jdlrobson, I can't check it until the Labs instance is fixed [14:47:17] k no worries [14:47:48] MaxSem i can put it on http://mobile-geo.wmflabs.org/w/index.php?title=Main_Page&mobileaction=toggle_view_mobile if that helps? [14:47:56] oh, after a reboot and 30 seconds' load it finally "works" [14:48:26] trying [14:49:33] jdlrobson, nope - still empty space clicking on which works [14:50:25] really? [14:50:30] why putting a simple button here is heretically unacceptable [14:50:55] well i noticed some browsers completely destroy any element that involves an element [14:51:03] there is a button there [14:51:14] element that involves an element? [14:51:26] lol sorry any element that involves an image [14:51:46] do any images show alt text? [14:51:50] no [14:51:57] waitasec... [14:51:57] yeh so some browsers if they encounter it just throws it away rather than showing the alt text [14:52:02] which is bad and the browsers fault imo [14:52:26] my android phone does that for example [14:59:10] meh, quite blurry: http://tinypic.com/view.php?pic=ddj8xy&s=5 [15:15:07] jdlrobson, is https://bugzilla.wikimedia.org/show_bug.cgi?id=34878 fixed? [15:15:16] * jdlrobson looks [15:15:25] well i wondered that myself [15:15:35] it's certainly not as important any more [15:15:43] the references code is only in the beta [15:16:01] and it doesn't actually remove the references section (although easily could...) [15:16:21] actually saying that... [15:16:26] let me check some thing [15:24:09] updated MaxSem [15:24:21] cool [15:27:32] YuviPanda: is this still relevant? https://bugzilla.wikimedia.org/show_bug.cgi?id=29862 [15:27:51]