[00:12:30] New patchset: preilly; "Fixes: * Bug 36213 - [CSRF] Special:MobileOptions/DisableImages needs token ** https://bugzilla.wikimedia.org/show_bug.cgi?id=36213 * Bug 36194 - Image enable/disable requires page reload to work after tapping link in beta ** https://bugzilla.wikimedi" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/5771 [00:12:45] awjr: can you look at ^^ [00:13:50] New review: preilly; "Added the following to the mobile view api ?action=mobileview&page=mobiletoken&override=1&format=xml" [mediawiki/extensions/MobileFrontend] (master); V: 0 C: -2; - https://gerrit.wikimedia.org/r/5771 [02:44:25] https://en.wikipedia.org/w/index.php?diff=489081184&oldid=489080938 [03:42:03] thanks Joan [03:48:27] New review: Catrope; "Has a broken API parameter and some minor issues with the JS changes, but looks good otherwise." [mediawiki/extensions/MobileFrontend] (master); V: 0 C: -1; - https://gerrit.wikimedia.org/r/5771 [08:22:51] * tfinc yawns [08:23:33] jdlrobson: check your pm [08:23:54] tfinc: go to sleep [08:24:01] YuviPanda: its only 1:23 [08:24:16] and since when do you take my role of telling *you* guys to sleep [08:24:19] ;) [08:24:37] :D Wah, I've been up for 4 hours and it is only 2 [08:24:39] not bad. [08:26:56] YuviPanda: how is our iOS feedback looking? [08:27:33] tfinc: not great [08:27:37] tfinc: still bad [08:27:42] what are people reporting? [08:28:13] tfinc: most of them seem to be 'the old app was good, why did you update, this sucks and is slow!' [08:29:04] scrolling on iOS 5.1 and 'slowness' are the only 'specific' issues reported, other than general 'it sucks' comments [08:29:43] 'BOTTOM LINE IS THEY TOOK MY FAVORITE APP AND DESTORYED IT' is copy pasting from one, which seems to be the general consensus there [08:30:24] so the ui comments i can understand but the slowness worries me. where are they reporting it? [08:31:08] general laginess. Again, nothing specific [08:32:00] I'm guessing most of it is 1. Initial load time 2. no 'instant' feedback on touching menus. [08:32:39] what can we do for the latter? [08:32:47] https://bugzilla.wikimedia.org/show_bug.cgi?id=35778 [08:32:47] that would make the app on both android and iOS better [08:32:59] right, so i've a branch called 'faster-clicking' [08:33:07] it *does* have more instant feeback [08:33:12] except that it breaks scrolling [08:33:53] i've been fighting with saved pages again, hopefully should have them fixed today. Saved pages and scrolling are taking an disproportionate amount of time to get right :( [08:34:25] so once I've this figured out, I'll be able to go see why that breaks scrolling and fix that. I'm pretty sure we'll ship a fastclick implementation for 1.2/3.2 [08:34:31] k [08:35:35] YuviPanda: can you respond to Maarten subject: " Android Wikipedia Mobile app v1.1.1 (background of saved page)" [08:35:50] i did, and got a response back. should respond to the response [08:36:00] YuviPanda tfinc - out of interest would it not make sense to allow downloading of the old app but mark it as not undergoing further development ? It might reduce the comment noise to useful ones if people who **loved** the old one can still download it [08:36:22] some people in general don't like change :) [08:36:32] jdlrobson: i pitched that as an option a couple of weeks ago [08:36:40] YuviPanda didn't like it much ;) [08:36:59] * aude waves [08:37:00] YuviPanda: whats your thought a couple of weeks later [08:37:02] hey aude [08:37:25] * aude says yes, keep the old app for iOS :) [08:37:35] tfinc: so, of late I've contemplated abandoning PhoneGap, and just maintaining separate iOS and Android native apps. [08:37:57] YuviPanda: whats causing you want to do that? [08:38:06] it would be a drastic and costly shift [08:38:11] now that program and scholarships are done, i have time to help with maps stuff [08:38:16] aude: nice [08:38:32] aude: we've been waiting on ops to get our new hardware in [08:38:44] * jdlrobson doesn't like native apps full stop and looks forward to a world where people just use the web [08:38:47] YuviPanda: and one that were not setup to handle [08:38:47] tfinc: we have labs project to work with now and it's good [08:38:55] aude: sweet [08:38:58] figure out what configuration works well [08:39:09] tfinc: indeed. I've not fully thought it out. [08:39:48] so YuviPanda I'm just suggesting we make the old app available under some different name and eventually make the iOS app a lot better so people switch over [08:40:18] jdlrobson: what about a simple "lite" version with no maps [08:40:26] * aude cant believe i'm saying that! [08:40:38] i think just for reading articles :) [08:40:44] maps aren't complicating anything [08:40:49] that's fine by me but the larger question is if we poured the same amount of time we poured into phonegap into the native iOS (or android) versions, we might have a better app? [08:40:50] oh, okay [08:40:50] there is no need to remove them [08:41:05] no I think we should push the app as far as possible - but from the sound of it people liked the old ios app for whatever reason and moving to our phone gap app was too drastic a change for them [08:41:07] it is also very much possible that I just need to put in more work :) [08:41:11] though, on older phones, the new app is incompatible [08:41:26] jdlrobson: true, we never ran into this issue with Androdi market, which had no 'old app' [08:41:30] exactly [08:41:36] and in the android market the feedback is more useful [08:41:42] aude: it supports the same exact phones as our previous app on ios [08:41:49] like why doesn't it do X why doesn't it do Y [08:41:51] tfinc: i don't think so [08:42:00] or i haven't updated my app in a long time [08:42:22] jdlrobson: indeed. Plus we're at a good 4.5 after 8k ratings, with iOS much lower. [08:42:29] * aude has a really old iphone but it's not broken and i don't want to pay for a new one [08:42:30] actually i take it back. we likely ran on 3.x [08:42:39] but honestly the distribution of those phones is tiny these days [08:42:39] tfinc: it did :) [08:42:47] that is almost negligible [08:42:54] grrrr [08:43:16] we make the same trade offs on the desktop [08:43:21] exactly. So my recommendation is we revert to the old app on itunes store and provide another download - even calling it something different e.g. WikipediaPlus making it clear it's a new app that's in development that will be more functional and one would hope we'd get better more useful reviews for that [08:43:34] if viewership is below our base % then its not officially supproted [08:43:48] tfinc: :( [08:44:11] jdlrobson: so, essentially, we revert 'official' wikipedia app to native one, and then rename phonegap one to something else marked 'unstable'? [08:44:46] when i drop my phone in the toilet, then i get a new one ;) [08:44:51] thats always been the case. endlessly trying to support every version means we don't reach anyone else. causing to fail our community and donors. we can't do that. and besides. iOS users upgrade faster then any other platform [08:45:00] Considering that'll actually improve our ratings, I'll do a +0 on that [08:45:01] jdlrobson: ^ [08:45:03] kind of... only i wouldn't call it official and in the description I'd say development on this has ceased and we are working on a new app (linking to it) [08:45:22] so encourage people to move to the new app [08:45:37] eventually when downloads get low enough we remove it from itunes store altogether [08:46:23] jdlrobson: what are your thoughts on page curl mockup for attribution ? [08:46:28] although we'd have to think about such a move carefully to avoid confusing people [08:46:59] jdlrobson: yes, 'auto updating' them to an older app might not be the greatest idea [08:47:08] yeh [08:47:20] * jdlrobson doesn't have an iphone so is not familiar with the update process [08:47:57] sounds tricky [08:48:03] tfinc: i really like it - my main worry is how the transition works. If people see a page curl I'd expect a fancy animation which is something I haven't looked into. I'm not sure how achievable it is on older devices [08:48:12] jdlrobson: i'm not enamored by it. using a page curl to trigger another browser to open is bizarre [08:48:18] YuviPanda: if we added a link in the description to the old app would people find it [08:48:29] people would, i'm not sure how apple will like it [08:48:34] a page curl should show a smaller set of text . here we'd be opening the browser and taking them to view history [08:49:11] so tfinc I was imagining it would give the illusion of looking on the back of the page [08:49:28] jdlrobson: right but that means were doing something pretty fancy here [08:49:45] but now I think more... maybe that would make more sense for an edit function [08:49:45] which as you said compatibility wise would be tought [08:49:47] tough* [08:50:06] i'm don't think the page curl is going to work [08:50:09] * tfinc wonders what else we could do [08:50:13] * YuviPanda likes a simple link :) [08:50:13] worse case scenario tfinc we could just not show the page curl and show a button for legacy browsers [08:50:29] YuviPanda: the link is simple. too bad its hideous looking [08:50:30] tfinc, are you sure you wanna se all our faces? :P [08:50:36] MaxSem: bring them on! [08:50:37] :D [08:50:41] well tfinc we'll have a new nav sometime soon - http://jonrobson.me.uk/wikipedia/experiments/nav/ :) [08:50:54] tfinc: can't it be made non-hideos? [08:50:57] we could put it in the menu on the left [08:50:58] hideous [08:51:08] jdlrobson: i need something before the nav bar or pete will (rightfully so) keep hounding us [08:51:16] (in the mean time placing it under the wikipedia icon menu) [08:51:22] yeah [08:51:26] i suggested that a while back [08:51:30] next to home and random [08:51:43] as people familiar with the W icon opening a menu will still click it on the new nav and get the same stuff [08:51:48] jdlrobson: that works for mobile web. but what about the app [08:51:54] the app is the main problem [08:52:12] actually.. and now I think about it linSmith wanted to keep page functions together [08:52:18] which would mean it would actually be in the sub menu [08:52:33] (e.g. button on right of screen) [08:52:42] we've transitioned those W options into the native menus [08:52:51] so we have to have something from the apps [08:53:18] if we give YuviPanda something pretty shiny then we could sneak it into the native menu [08:53:22] but I'm sure he'll revert it [08:53:23] ;) [08:53:37] * YuviPanda sneaks 'hand me a pony' into native menu [08:53:38] well in the app the search button doesn't do much right? - could we not replace that with the more icon which when clicked gives just the history icon [08:54:24] * tfinc raises YuviPanda to a rainbow unicorn [08:54:41] New review: MaxSem; "I've made core's action=tokens extendable in https://gerrit.wikimedia.org/r/5781" [mediawiki/extensions/MobileFrontend] (master) C: 0; - https://gerrit.wikimedia.org/r/5771 [08:54:48] jdlrobson: so, currently building from master the app has *no* footer. I'm adding a variant of the footer, so I'll add a link to history there. We'll kill it when we have something better. [08:54:49] tfinc: ^ [08:55:11] another suggestion (I know it's awful) but for the app couldn't we just tuck contributors into the more menu.. [08:55:12] YuviPanda: jdlrobson i'm likely going to fall asleep soon. can you guys keep the conversation going and find something else that will work [08:55:28] jdlrobson: that's what tfinc meant by the 'native' menu :) [08:55:33] ah sorry [08:55:38] but yeh that seems to be the way to go [08:55:48] jdlrobson: so, the app currently has no footer. [08:55:53] as it does feel like it's going to end up in a more menu of some description [08:56:09] does the app need a footer? [08:56:29] are you talking about the "Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of use for details. [08:56:29] Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. [08:56:29] Contact us" text ? [08:56:31] jdlrobson: so, it doesn't. we can put 'contact', 'privacy', 'about', 'disclaimers', 'terms of use' in settings [08:56:32] yes [08:56:38] so, what I suggest is [08:56:50] that we can just have 'Content available under CC BY-SA 3.0' as a footer [08:56:53] and link history out of there [08:56:59] yes agreed [08:57:17] * YuviPanda goes to do that [08:57:25] -> Content available under CC BY-SA 3.0 - view authors [08:57:31] something like that [08:57:35] I wouldn't use the word history [08:57:36] yup [08:57:46] authors/contributors/ [08:57:58] Content available under CC BY-SA 3.0 (Contributors) [08:57:58] so in the mobile app I'll stick it in the W icon [08:58:03] if tfinc is fine with that [08:58:05] or view contributors. [08:58:23] * jdlrobson thinks [08:58:27] jdlrobson: i'm confused. I was suggesting putting this on the end of the page content (footer) [08:58:37] where that uglyish text is right now [08:58:46] sorry I meant mobile site [08:58:48] !! [08:58:53] ah [08:58:54] ok [08:59:09] why not have 'view contributors' next to the cc link in the site as well/ [08:59:11] ? [08:59:44] brion has checked in some wp7 code, I wonder what else it breaks :) [09:00:26] this sounds nicer -> Content provided by these people and available under CC BY-SA 3.0 [09:00:45] jdlrobson: re: your comment on the menu.js code. Our menu code is currently way too spread out and messed up. Should spend a cycle 'settling tech debt', but unsure when. Hopefully right after 1.2 [09:00:47] jdlrobson: agreed [09:01:07] I guess we'd need to check any copy text with phil [09:01:17] well, we can always add and change later [09:01:31] YuviPanda: agreed - the menu.js was a landmine field to walk through :) [09:01:43] especially since android code is different :) [09:02:05] brion likes overriding globals. but then again, it was essentially 'stick to the current code's style'. [09:02:18] jdlrobson: i'd reccomend checking out a commit that was 4-5 months back and looking around :) [09:02:20] I'll update the ticket suggesting the footer with text 'Content provided by these people and available under CC BY-SA 3.0' [09:02:26] ok [09:02:34] i'll take a break from saved pages and implement this. [10:08:04] So lucb1e my plan was to make a few tweaks to this url - http://bit.ly/JoIoZ8 - and you comment if they fix the scrolling [10:08:18] okay [10:08:41] i'm assuming in the current form the scrolling problem is present? [10:08:52] * lucb1e tries [10:08:57] yes [10:09:15] and there is a php error on top btw, but you'll probably see that too [10:09:57] yeh I just saw that shouldn't matter for our needs [10:10:02] okay [10:10:07] ok so I'm going to make a quick change [10:10:31] can you refresh now and tell me if the problem is still present? [10:11:02] it's still present [10:11:26] can you refresh now [10:11:32] is it still present? (toggling should break) [10:12:59] hm it's incedibly slow now, testing if my phone is doing something in the background... [10:13:13] as in the scrolling is even slower? [10:13:29] or as in loading? [10:13:34] sometimes the page is very slow to load :( [10:13:41] no I mean it lags, not less scrolling distance per click [10:14:07] Ok let me know when you've checked any background apps are not running [10:14:09] it's only on the wiki page, as soon as I switch to another website it doesn't lag anymore [10:14:23] ok [10:14:39] can you try now ... is it any better? [10:15:26] yes, no lag and normal scrolling distance! No toggling either btw [10:15:37] ok [10:15:43] try now [10:15:46] toggling should return [10:16:04] hopefully lag will not... [10:16:26] yes, and the scrolling issue is not present. The scrolling distance is normal (and there is no lag)! [10:16:38] ok it looks like its related to the search bizarrely [10:16:44] can you refresh one more time [10:16:46] that should confirm it [10:17:28] no scrolling bug anymore :) [10:17:30] and then I'll try and find a more specific reason :) [10:17:32] and toggling [10:17:35] ok [10:17:41] so now the scrolling bug is back yes? [10:17:45] (just updated) [10:18:02] yes [10:18:11] I think I know the problem... [10:18:37] refresh now.. [10:18:40] btw when I open something, then close it again, it says "ShowHideShow", the buttontext gets appended instead of replaced [10:19:08] scrolling problem appears again [10:19:20] ok.. so it wasn't what I thought :) [10:19:42] can you refresh now [10:19:47] well I don't know what you are trying, but it feels like we're getting close now :P [10:20:09] yup we are [10:20:11] scrolling problem appears again [10:20:27] how about now? [10:20:48] scrolling problem appears again [10:21:07] still? mm that's very strange [10:21:38] reloaded again after you said "still?", and yes it still appears [10:22:03] try reloading now [10:22:08] I'm just double checking it is search related [10:22:15] this could well be a memory problem [10:23:02] scrolling problem is present [10:23:13] ok... just to check are you on the beta or the normal version [10:23:28] the beta has images for arrows, the normal version has buttons with 'show' text [10:23:36] I think you have the normal version so this is most strange [10:23:52] where should I see that? [10:24:03] I'm just reloading whereever it redirects to after that bit.ly link [10:24:59] oh wait just read where I can see that (missed it) [10:25:13] yes the normal version, I have toggle buttons [10:25:20] ok great [10:25:34] if you refresh now is the problem still there - just checking this is not caching related [10:25:55] was thinking about caching too, but this worked before... Anyway, reloading and trying now... [10:26:10] the problem is not there now [10:26:15] it works normal [10:26:19] right it was caching related.. this makes more sense now [10:26:49] refresh now - if the scrolling problem is still not there I think I've worked out the problem :) [10:27:21] the problem is not there now! [10:27:42] and if you refresh now is it still there? [10:27:49] *still not there [10:28:09] indeed, still not there [10:28:29] and now if you refresh it is back :) [10:28:52] indeed! [10:29:02] awesome.. we have a fix :) [10:29:06] yay :D [10:29:07] thanks so much [10:29:18] especially you, you did all the work :P [10:29:19] * jdlrobson does a dance [10:30:17] hmm how fast does stuff get updated on the live wikipedia website? [10:30:33] we do a deployment every Monday [10:30:38] sometimes more often [10:30:47] that's Monday afternoon PST [10:31:11] okay, and after that it's until everyones cache has refreshed by itself or do you make sure it expires? Just wondering [10:31:24] so Tuesday AM next week at the latest the problem should disappear... although saying that we also have a new design mOnday [10:31:28] have you seen the beta? [10:31:42] if not -> http://bit.ly/Jnjabh [10:31:47] I don't think I've seen it [10:31:50] you might want to check that works in your Nokia as well :) [10:32:28] actually, it lags hugely [10:32:36] eek [10:32:42] we should look into that as well [10:32:46] if you have the time? [10:33:03] hmm I think I can make the time [10:33:17] right does the lag disappear now? [10:33:28] it's possibly related to the last problem [10:33:35] if I drop out at some point, I'll either reappear within about half an hour or contact you via email again (or just check if you're here some other time) [10:33:37] * lucb1e checks [10:33:39] ok no worries [10:33:48] hopefully this will be quicker now we know what caused the last one [10:34:16] no lag and no scrolling issue now :) [10:34:24] ok yeh so it's search again.. let me see [10:34:26] and the toggle buttons still "ShowHideShowHide" [10:35:15] how about now? [10:35:35] (hm when I visit the page on my pc there aren't even buttons lol) [10:35:48] scrolling is fine and no lag [10:35:52] yep the new design has no icons [10:35:56] no buttons [10:36:00] icons instead on the far right [10:36:01] well it does on my phone :P [10:36:55] how about now.. does the lag return? [10:37:34] no lag [10:37:42] (and no scrolling issue) [10:37:57] oh and no buttons now [10:38:07] but the lag returns now? [10:38:08] looks neat :) [10:38:15] sounds like caching problems [10:38:16] nah there is no lag [10:38:28] if you refresh now there should be lag...? [10:38:37] oh, /me refreshes [10:38:52] no, there isn't any problem now [10:39:27] does search work you as well? [10:39:50] If you search for San you should get several results (although they might be slow to appear) [10:40:48] search results should look a bit like this - http://www.mediawiki.org/wiki/File:Mobile_min_A.png [10:40:49] hm when I mouseover the search the whole page goes blank and it lags hugely, the only thing visible is my cursor (which changed to a pointer/hand), the php error on top and an icon that was to the left of the search [10:41:21] attempting to click the now invisible searchbar, it does focus. Let's try searching... [10:41:36] it sounds like a host of caching problems :-S [10:41:42] this server is not brilliant [10:42:16] lag disappeared as soon as I selected the bar, typing something results appear rather quick and I can click them [10:42:41] ok but there is lag when you scroll the page? [10:42:54] no [10:43:00] ok great [10:43:04] so I think we're okay then [10:43:49] so when I mouseover it, it lags for some reason, when I focus the field the lag disappears, when I mouseout the field the lag disappears (or blur by moving the mouse out works too) [10:44:14] how very strange [10:44:25] it's workable, but not sure if everyone will get what's happening, especially since the search bar disappears (though the cursor is still a hand/pointer) [10:45:15] ok as long as it's workable [10:45:21] the search sounds like it needs a bit more tweaking though [10:45:45] might be good if it didn't do anything on mouseover [10:47:46] does the issue happen now if you refresh? [10:47:52] on a mouseover [10:48:33] yes [10:49:05] and only when I mouseover the search box, the wikimedia logo on the left or search icon on the right is no problem [10:50:14] hm one thing changed though, the page doesn't disappear anymore as I mouseover the searchbox [10:50:22] yeh that's what I changed [10:50:23] :) [10:50:30] if you refresh now.. same problem? [10:50:52] yes [10:51:39] most bizarre [10:52:53] if you create a debug output div below the search, I can tell which ones appear before it lags (and it lags so much that every mousemovement takes seconds, plenty of time to read "action $i executed" [10:53:24] and it's only mouse mouse movement over search? [10:53:27] so just put those messages all over the js and try :P Or that's how I'd try this [10:53:38] hm I don't have a tab button or touchscreen [10:53:45] there is no other way to reach it [10:53:51] if that's what you meant [10:54:17] so to be clear you are saying that when you move your cursor over the search box lag appears? [10:54:23] but it's only when you go over the search? [10:56:58] I'm not sure what you exactly mean (the diff between 'search box' and 'search'), but this is the area that makes the problem occur: http://g2f.nl/0mr78bi [10:57:34] (printscreened on pc, the problem only occurs on my phone of course) [10:57:59] thanks that helps a lot [10:58:05] and if you refresh now is the problem still present? [10:58:17] also the text "Type your search here" disappears onmouseover [10:58:19] * lucb1e tries [10:58:42] problem is still there [10:58:53] you sure this time that it's not caching related? [10:59:02] and now? [10:59:15] it shouldn't be caching related.. i'm updating cache as i make the fixes [10:59:26] oh I meant browser cache [10:59:31] not sure how caching works on the server's side [10:59:39] problem is gone! [10:59:40] I'm forcing you to download new js each time so don't worry :) [10:59:44] *trying search itself* [10:59:56] search will be broken now :) [11:00:11] indeed [11:00:29] mm [11:00:32] so that's very weird [11:01:40] ok try now [11:01:42] is the problem still gone [11:01:45] search should work this time [11:02:39] problem reappears [11:02:51] eek [11:03:05] and search broke [11:03:35] hm as soon as something is inputted in the search, there is no problem anymore when I mouseover [11:03:49] how about now? [11:03:51] emptying the box makes the problem appear again [11:03:55] oh! Maybe I know what this is! [11:04:03] I just saw an autocomplete flash by [11:04:25] yeh I think I know the problem [11:04:27] takes ages for that to load when the box is empty (so it matches * and shows all my thousands of previous searches) [11:04:28] if you refresh it should be okay? [11:04:33] let's try [11:06:40] the moment I mouseover the page disappears like I described before, but search works [11:07:08] mouseout'ing the box, the page does not reappear [11:07:11] Yes the page should disappear.. I think maybe it's just not rendering nicely in your browser [11:07:55] you might want to make it disappear onclick/onfocus instead of onmouseover, every time someone scrolls past it now... [11:08:42] the weird thing is it should disappear only on a click.. I'm not sure why your browser is triggering the event [11:09:02] oh, that'd explain why so many websites have this [11:09:07] if you refresh now the problem is still gone yes? [11:09:08] well, many, far from all [11:09:15] * lucb1e tries [11:09:49] lag issue reappears [11:09:55] ohh no! [11:10:37] ok so what is happening here is that your browser as you hover over the search is repeatedly firing blur and focus events [11:11:03] this is most annoying [11:11:21] trying with an own page with only a

lipsum

on the middle of the page, it never fires the event except when I click the div [11:11:24] if you look now the problem goes away? [11:12:04] yes, works perfectly now [11:12:43] ok [11:12:46] only onclick the page disappears and when I type the search is working (although slowly) [11:12:51] i'll have to think about this a bit more but I have a few ideas [11:13:04] yep that's the correct behaviour [11:13:08] it will be quicker on a faster device [11:13:16] the problem is you are seeing an empty search screen [11:13:22] (the page is underneath) [11:13:27] possibly a problem with our design [11:14:37] yeah the device isn't too fast, but most things go alright with enough patience :P [11:15:04] great [11:15:11] well I'll get some fixes out sometime today and update the ticket [11:15:25] I really appreciate you taking the time to help me troubleshoot this - so much harder without a real device! [11:17:53] yes I can imagine how hard and annoying it must be to debug [11:18:09] and well, doing this also improves reading wikipedia from my phone for me, you're spending all this time on it ;) [11:18:27] is it possible to see how many users have a symbian s60v3 device or even this E75? [11:19:09] We have tables somewhere.. [11:19:11] I'm trying to find [11:21:04] http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm [11:21:56] I guess the information is somewhere in there! [11:23:36] haha, well it's not findable with ctrl+f when searching 'e75' or 'symbian', let's see what my browser useragent is and if I can find anything with that :P [11:24:26] still neat to see that detailed data, statcounter's global stats are good for an overview but this is really an in-depth look [11:25:31] hm nokia is in there [11:25:45] can you check something for me if you still have your nokia handy? [11:25:53] I can [11:26:06] http://bit.ly/JoIoZ8 [11:26:14] is scrolling lag present there? [11:26:48] no scrolling lag, but there is the scrolling distance per click-problem [11:27:32] scrolling distance per click? [11:28:27] the original problem I reported on bugzilla [11:28:35] ahh that's what i meant [11:28:38] so every time I click it only moves half the distance it should [11:28:39] ok that's not a good solution then :) [11:28:40] okay [11:29:41] hmm, that sortof half-sounds like the iOS 5.1 scrolling problem [11:32:06] lucb1e: have thought of a different fix [11:32:08] can you refresh now? [11:32:11] it should go away [11:32:17] if so I'll push the fix and close the bug [11:33:32] argg actually that's no good either! [11:33:38] scrolling works good now [11:36:44] ok looking into the beta now [11:42:48] 1 last test lucb1e is the mouseover lag present in http://bit.ly/Jnjabh [11:44:00] no lag, search works, page disappears onclick, no scrolling dist/click. Perfect :) [11:44:29] awesome [11:44:32] will push the fixes [11:44:43]