[00:01:23] brion: did u see may's comments about some of the abuse filter messages referring to desktop interface element locations which won't be present on app? https://trello.com/c/PKaAEAUT/28-5-as-a-mobile-app-editor-i-want-to-be-notified-if-my-edit-was-caught-by-an-abuse-filter-so-that-i-can-make-the-appropriate-chang [00:03:49] bleauuughhhhghghgh [00:03:53] that's going to be fun to deal with [00:04:06] jdlrobson: yeah, looks like diff-thank in MobileWebClickTracking is the only way to do it. [00:04:29] brion: yah. sounds like rather than creating work-around with web-view or attributed string, we need clean versions of these messages... [00:04:34] jdlrobson: but that doesn't really give you a comparison with desktop [00:05:08] as the numbers in the Echo logs are for both desktop and mobile [00:05:25] you could be clever and subtract one from the other [00:05:38] but I don't see a clean way to do it [00:06:41] brion: should i just show the terse "info" part of the abuse filter response for now until we get the verbose warning stuff sorted out? [00:07:16] yeah let's start there [00:07:50] jdlrobson: You could also add eventSource info to the Thanks Echo logging [00:08:32] brion: so based on may's findings and pesky html, should i create card for "clean no-html abuse filter warnings"? is that even something we could expect to be ready in time? [00:09:08] mhurd: i would not expect that to be ready in time but we should consider how to make it gradually available [00:09:18] there'd be a lot of rules to update in a lot of languages to improve their warnings [00:09:31] that's community work; we have to see if we have to provide them tools to do it [00:09:46] brion: ah [00:10:54] jdlrobson: Looks like it should be setting the eventSource as 'mobilediff' if you haven't already figured that out [00:12:04] andrew g. is gone, who can i ask about abuse filter consequences? [00:14:18] violetto: i don't know :( [00:14:45] violetto: how did you get that link to show the actual message? [00:15:19] i click on one of them and sometimes when you scroll down, you'll find a button that says preview filter message [00:15:30] violetto: ah! thanks! [00:16:22] mhurd: np! [00:27:44] rmoen: Why does VE parse thumbnails into figure elements (and then reproduce the Vector skin styles to make it look the same as Vector). This makes it a pain to make them look right in skins besides Vector. [00:30:53] Seems like it would be much easier to just parse them the same as normal and let the existing skin styles apply themselves. [00:48:52] (03PS1) 10Cmcmahon: Merge "Story 1620 (part 2): Promote LeftNav Signup A/B test to Stable" [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110113 [00:51:18] (03PS1) 10JGonera: Make search input font size consistent [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110114 [00:51:35] brion: god these are a nightmare... some of the abuse filter messages have sooooo many links, and there are a hundreds of messages... ahhh [00:53:29] (03CR) 10Cmcmahon: [C: 04-1] "I think this is a reasonable approach, but the test fails because no BetaPage is defined:" [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109436 (owner: 10Jdlrobson) [00:56:39] (03PS1) 10JGonera: Hygiene: Remove #mw-mf-page-left from menu link [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110116 [00:58:07] (03CR) 10Cmcmahon: "gah, left comment on the wrong branch, meant to say this for https://gerrit.wikimedia.org/r/#/c/109011/" [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109436 (owner: 10Jdlrobson) [00:58:50] (03CR) 10Cmcmahon: [C: 04-1] "I think this is a reasonable approach, but the test fails because no BetaPage is defined:" [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109011 (owner: 10Jdlrobson) [00:59:39] jdlrobson: did you not check in a page file? https://gerrit.wikimedia.org/r/#/c/109011/ [01:06:16] kaldari: I know there was a reason for the thumbs to be a figure. you could probably get a better answer from mooeypoo ( moriel ) [01:06:34] kaldari: ^ though i cannot remember right now [01:07:59] rmoen: any idea where the VE folks are anyway? Haven't seen them at the office and they all seem to have been away from IRC for a while [01:23:48] (03PS1) 10Jdlrobson: QA: Add browser tests for story 1610 [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110117 [01:23:50] (03PS1) 10Jdlrobson: Story 1610: Promote already logged in message to stable [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110118 [01:24:51] (03CR) 10Jdlrobson: [C: 032] Hygiene: Remove #mw-mf-page-left from menu link [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110116 (owner: 10JGonera) [01:25:15] (03Abandoned) 10Jdlrobson: Merge "Story 1620 (part 2): Promote LeftNav Signup A/B test to Stable" [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110113 (owner: 10Cmcmahon) [01:25:27] (03Merged) 10jenkins-bot: Hygiene: Remove #mw-mf-page-left from menu link [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110116 (owner: 10JGonera) [01:26:29] (03CR) 10Jdlrobson: [C: 032] Make search input font size consistent [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110114 (owner: 10JGonera) [01:27:04] (03Merged) 10jenkins-bot: Make search input font size consistent [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110114 (owner: 10JGonera) [01:28:20] (03CR) 10Jdlrobson: [C: 032] QA: Add a short pause for notification to disappear [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110068 (owner: 10Cmcmahon) [01:28:54] (03Merged) 10jenkins-bot: QA: Add a short pause for notification to disappear [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110068 (owner: 10Cmcmahon) [01:31:00] (03CR) 10Jdlrobson: [WIP] Allow users to adjust the font size (033 comments) [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/108300 (owner: 10Theopolisme) [01:33:16] (03Abandoned) 10Jdlrobson: Optimise external link SVGs [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/107740 (owner: 10Jdlrobson) [01:35:35] (03CR) 10Theopolisme: Use DISPLAYTITLE when rendering pages (031 comment) [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/108539 (owner: 10Theopolisme) [01:43:05] (03PS3) 10Jdlrobson: WIP: Use MediaWiki UI buttons in alpha [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/102581 [01:45:23] (03CR) 10Jdlrobson: Use DISPLAYTITLE when rendering pages (031 comment) [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/108539 (owner: 10Theopolisme) [02:26:45] (03PS1) 10Kaldari: Story 1621: Fixing VE content area typography/design for mobile [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110122 [07:27:13] (03CR) 10Yurik: [C: 032] Add COPYING [extensions/ZeroRatedMobileAccess] - 10https://gerrit.wikimedia.org/r/107768 (owner: 10Reedy) [07:27:17] (03Merged) 10jenkins-bot: Add COPYING [extensions/ZeroRatedMobileAccess] - 10https://gerrit.wikimedia.org/r/107768 (owner: 10Reedy) [07:40:08] violetto: around? [07:40:10] brion: around? [07:40:20] yuvipanda: she's here [07:40:33] violetto: since when has she started talking in third person? :P [07:41:10] yuvipanda: since right about now! [07:41:24] violetto: she sounds fun! :P [07:41:40] violetto: so monte just wants to display the short 'info' string from AbuseFilter [07:41:43] yuvipanda: she can be! [07:41:51] violetto: but that only says things like 'Hit AbuseFilter: contains poop' [07:41:54] short info string? [07:42:00] which is all sorts of eugh :( [07:42:38] violetto: https://dpaste.de/Nn8u brion and monte conversation from earlier [07:43:14] yuvipanda: /reading [07:43:19] violetto: ok [07:45:27] oh okay. so along the same thought as brion, we talked about logging a bug with character count limit so the community can help us with that. [07:46:27] violetto: right, so what I was thinking of was letting the community control which content gets shown to apps and which ones get shown to desktop [07:46:44] yuvipanda: im going to send you a comp that was the result of our convo and talking to the design team and andrew, etc etc. hang on [07:46:50] violetto: hmm, ok [07:46:57] yuvipanda: actually i'll need about 10 mins on this [07:47:03] violetto: ok! [07:47:18] it can solve some of the problems with what we have currently before we log a bug for it [07:52:02] violetto: hmm, I'm curious. Because I don't think the bug is too hard to solve [07:52:12] violetto: with community goodwill, at least [07:52:14] * yuvipanda looks at legoktm [07:53:48] violetto: there are only 36 enabled abusefilters on english wiki that result in a warn [07:53:55] violetto: that's just a few hours of work to fix them all up [07:54:11] yuvipanda: https://www.dropbox.com/s/9klgapqe9rk4xn5/Screenshot%202014-01-28%2023.57.44.png [07:54:38] yuvipanda: yep, i mean this comp will work either way [07:54:46] but i agree it should be solved anyway [07:54:53] violetto: we don't actually need to do anything for 'tag' [07:54:59] violetto: we only care about 'warn' and 'disallow' [07:55:07] violetto: with 'warn' you get to submit again. [07:55:15] violetto: with 'disallow' there's no submitting with the same content again [07:55:22] violetto: tag is just for RC patrollers, doesn't matter to the user [07:55:35] violetto: I think we can ignore tags? [07:55:44] yuvipanda: if i knew next to my edit will be a tag on the article history, i'd like to know the fact. But either way, there's still going to be a warning to the users that they will be tagged right [07:55:57] violetto: there isn't one on desktop afaik [07:56:33] yuvipanda: oh reals? [07:56:35] :S [07:56:44] violetto: yeah, I am pretty sure. [07:57:15] https://en.wikipedia.org/w/index.php?title=Special:AbuseFilter&sort=af_hit_count&limit=100&asc=&desc=1 [07:57:25] go to filter 11 [07:57:39] which has the "Tag" consequence [07:57:42] violetto: select 'hide disabled filters' as well :) [07:58:08] preview the message, that message will be shown to users right? [07:58:08] violetto: https://en.wikipedia.org/wiki/Special:AbuseFilter/11 you mean? [07:58:14] violetto: yeah, so that is a result of the 'warn' [07:58:19] violetto: so we will get back a 'warn' [07:58:26] I don't think tag is even reported in the API [07:58:30] since it is a purely server side thing [07:58:53] violetto: so what happens here is, you are warned first, but if you decide to go ahead anyway, it will be tagged in the logs [07:59:32] yeah, so within the warning, you'd see AF comp on the left [08:00:06] yuvipanda: from there, if user decides to proceed, they will get tagged, jsut like we warned them [08:00:26] violetto: yeah but warn and tag are independent [08:00:31] violetto: you can have tag without warn and warn without tag [08:01:09] violetto: and if it is 'disallow' there is no 'done in good faith, go ahead' possibility. They *must* go back and fix it [08:01:20] yuvipanda: yep [08:01:21] violetto: you should forget about 'tag' at all, and just do 'warn' and 'block'. [08:01:34] yuvipanda: oh i see [08:01:45] violetto: warn and block are the only things that result in user facing messages [08:01:57] i might not have gotten abit confused [08:02:02] *might have [08:02:12] yuvipanda: yep [08:02:16] violetto: don't worry, AbuseFilter is confusing as fuck [08:02:29] i imagine warn is orange block is red [08:02:46] cus block is more severe than the other [08:03:43] violetto: warn and disallow you mean? [08:03:58] violetto: 'block' is also used in some wikis, but they literally block your user account from making any further edits [08:04:01] warn allows you to save anyway [08:04:11] disallow, doesnt? [08:04:19] yuvipanda: i see [08:04:30] violetto: yup. warn allows you to save anyway. disallow does not [08:05:43] check the link i sent you again [08:06:46] violetto: doing [08:07:09] violetto: where is the 'go back and fix this' CTA? [08:07:15] violetto: that should be the primary action on both of them, no? [08:07:20] the back button [08:07:23] violetto: rather than just 'go ahead, hit save again' [08:07:47] violetto: that doesn't seem... important enough? Most people when seeing this will just hit 'save anyway' [08:11:05] typically the progressive button has a filled background. In this instance, I'm leaving it out to place the same emphasis to leave it to users to make that decision. I'm kinda torn to put it on the right/left. On left because you're literally going back to fix it. I originally had it on the right but i wouldn't have a problem with it if on the "warn" instances, you get [save anyway] [go back and re-edit] and on disallow [go [08:11:22] do a test and see how people react to it [08:11:55] violetto: hmm, maybe we could have a two line thing there - 'go back' and 'save' buttons? [08:12:15] err [08:12:17] two button thing? [08:12:26] on two lines even? [08:12:59] yuvipanda: https://www.dropbox.com/s/oyy76gs4ljoodoa/Screenshot%202014-01-29%2000.16.40.png [08:13:32] yuvipanda: that wouldn't be necessary [08:13:34] violetto: I like that better, but 'Oops' makes no sense :| [08:13:41] violetto: also no affirmative actionms on top left [08:13:44] on Android at least [08:13:53] violetto: why not? [08:14:04] we can try this first and get feedback. Those things are placeholders, including the additional text that isnt in the template [08:14:04] violetto: nothing in it tells me I need to hit the back button and fix it [08:14:15] violetto: we can try the two buttons thing first and get feedback :P [08:14:31] two buttons thing? [08:14:31] if people say 'I already know I have to hit back! that is just clutter!' we can remove it? [08:14:48] violetto: one to say 'go back and fix it' and one to say 'this is constructive, go on' [08:15:51] (03PS4) 10Dr0ptp4kt: Slide the keyboard down on search result item tap. [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/109504 [08:16:15] (03CR) 10Yuvipanda: [C: 032 V: 032] Slide the keyboard down on search result item tap. [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/109504 (owner: 10Dr0ptp4kt) [08:17:58] yuvipanda: we have a system going and if we ever want to break it, it has to happen on a very strong reason and have proven that nothing else worked that made that a necessary move. there's space on the right to make that happen, plus, it already exists and reusing what we have across web and web mobile is always great [08:18:12] violetto: err, what? [08:18:19] violetto: that entire sentence made no sense to me :| [08:18:22] violetto: what system? [08:18:31] violetto: what space on the right? [08:18:35] I... am so confused [08:18:49] [destructive action] Context [Progressive/Constructive action] [08:19:03] top nav [08:19:24] violetto: yeah, sure. but not on the ActionBar. Imagine if I started having desktop style 'menu' on top of every web page with the same argument. [08:19:58] yuvipanda: not sure what you mean, draw something for me! [08:20:02] violetto: plus reuse here doesn't seem right to me - I would have to go completely against the actionbar code, redo it all just do do this one thing [08:20:06] violetto: ok wait [08:23:34] violetto: I only had preview to work with, so ignore the colors. And ignore the exact text as well. http://imgur.com/EiMz14l [08:24:33] yuvipanda: oh for sure we can do that [08:24:38] violetto: :P [08:24:43] violetto: that's all I was trying to say [08:24:45] yuvipanda: i thought you were talking about messing with top nav bar [08:24:53] putting 2 buttons on the left [08:25:09] violetto: I only want it to not say 'Oops', primarily because our translators will have no idea [08:25:13] violetto: other than that it looks ok to me [08:25:16] violetto: heh, no. [08:25:33] yuvipanda: oops area can be "warning," etc [08:25:43] violetto: yeah, we can figure out exact text later on I think [08:25:48] Reason why it's not "warning!" because it's repeated on the body copy [08:26:13] violetto: right. I don't mind putting 'oops' there either, just be warned that the langeng team will probably poke me and ask me to change it [08:26:22] POOPS! [08:26:28] violetto: hahaha! :P [08:26:45] haha. [08:26:49] violetto: also, I thought *you* were talking about messing with the top nav bar :P [08:26:53] violetto: anyway, it's settled now :P [08:27:19] ok so on block and disallow consequences, there isn't a "submit anyway" button, correct? [08:27:23] violetto: can you update your mockup to have the 'two buttons' but with better colors? [08:27:28] violetto: yup, no 'submit anyway' [08:27:32] violetto: submit anyway only for warn. [08:27:36] others don't have submit anyway [08:27:40] only 'go back and edit' [08:27:40] in that case just "make changes to my edit" [08:27:47] violetto: yeah, seems fair enough [08:30:06] yuvipanda: ok koo [08:30:15] violetto: what's 'koo'? [08:30:53] haha in australia that's how i said "cool" [08:31:09] totally brought my memories back when andrew was around [08:32:18] violetto: hahaha! :D [08:32:18] violetto: right [08:32:36] violetto: I thought working with abusefilter has added words that sound like 'poop' to your vocabulary :P [08:32:45] violetto: can you update the mockup? [08:35:34] yuvipanda: completely possible [08:35:41] yeah im sending them over soon [08:35:45] violetto: wheee! [08:41:18] yuvipanda: updated trello :) [08:41:31] violetto: wooo! [08:41:33] violetto: nice [08:41:37] assets and all [08:41:48] violetto: looking [08:42:37] violetto: no CTAs for the 'warn'? [08:43:16] on the top nav, i think it's great that it's repeated for disallow at the bottom though [08:44:05] violetto: there's nothing at the bottom for warn? [08:44:18] violetto: so without reading the full thing, I don't know what actions I can do [08:44:42] violetto: this is what I drew on the image, no? The actions you can do for warn (back and edit or continue) being more prominent? [08:44:50] violetto: the edit pencil says mostly nothing at this point. [08:45:23] violetto: I drew the extra button on the disallow, should've done two buttons on warn and one on disallow. [08:45:28] violetto: that's the 'two buttons' I was talking about [08:46:32] yuvipanda: it wouldn't hurt putting it down there. the top nav is persistent and it means edit, that's how they even got into editing right, they already got the concept and not to mention it's highlighted. and by now they have already been using the tick to mean go ahead, I want to submit my edit [08:46:51] violetto: yeah, but you have to fully read the entire thing to figure out what actions you can do, no? [08:47:03] i took out the submit anyway because we just said it wouldn't appear on disallow, right? [08:47:09] violetto: so after the bright large context clues for 'hey, warning!' you sitll have to read the stuff [08:47:17] violetto: yeah. disallow looks perfect [08:47:20] violetto: just talking about warn here [08:47:26] violetto: but let's just put it down there as well? [08:50:22] yuvipanda: either way the highlighted next action is very emphasized, it's not going to do any harm to us or them. if you worry that they tap on re-edit without reading the text, we can make it so it highlights only when user is half-way scrolled down. like i said, in this event, i don't have a strong opinion about not repeating at the bottom. i'm only thinking about including sufficient amount of actions/text. [08:50:30] so sure, we can include it [08:50:56] violetto: let's include it. I also don't think the 'edit' action on top should be highlighted in any way - it should just have the usual actionbar styling [08:51:38] I mean, the 'back' would also be styled as Android's back, rather than the big iOS-like one we have on the mockup [08:51:59] violetto: can you add the bottom actions repeated in the mockup too? [08:52:31] violetto: oh, also - the actions at the bottom, will they be 'fixed' (visible while scrolling as well) or just inline (you will have to scroll to the bottom to see them)? [08:53:24] yuvipanda: scroll to bottom to see. that's the idea right, so they go to the bottom. Otherwise they already have the top nav persistent [08:53:33] violetto: yeah, sounds ok to me [08:54:06] violetto: if the response text is not long enough to require people to scroll, do we stick these at the bottom of the screen, or at the end of the message? [08:54:46] yuvipanda: at the end of the message. [08:54:50] violetto: ok [08:54:58] violetto: also, Open Sans here as well? [08:55:10] same as content styling in terms of font size and line-spacing? [08:55:24] mhm :) [08:55:48] violetto: sweet then [08:56:31] yuvipanda: oh, we should totally do a simple animation for the flag and the other pending icon [08:56:43] violetto: easy enough, I think [08:56:45] ;D [08:57:04] violetto: let me know what you want to do :) [08:57:08] yuvipanda: ok [08:57:10] as long as it isn't too distracting... [08:57:13] btw, send me a build! [08:57:23] violetto: hah! ok [08:57:26] yuvipanda: i'll make it extra distracting [08:57:38] not too, but extra [08:57:41] violetto: make it vibrate the phone and also play a loud banjo noise? :P [08:57:50] hells yea [08:58:03] vibrate the phone until you decide to re-edit [08:58:14] violetto: :P [08:58:30] if you choose not to re-edit, it'll vibrate faster, like with the seatbelt beeper in the car [08:58:37] the more you ignore it the faster it sounds [08:58:54] violetto: sent you a build. this edits textwiki [08:58:59] violetto: *testwiki [08:59:29] violetto: you should try out the captcha. ignore the issue with the captcha size being too small, but other than that, I bet you will have plenty of issues to report :P [09:00:43] violetto: you can trigger a captcha by adding an external link [09:06:08] yuvipanda: /checkin! [09:06:28] violetto: ? [09:06:51] yuvipanda: btw, how to/when to log bug for abuse filter? [09:07:54] violetto: what bug, exactly? [09:07:57] violetto: the restyling one? [09:08:03] violetto: err, the rewording-for-apps one? [09:09:29] rewording one [10:16:27] (03PS2) 10Yuvipanda: Make CaptchaResult depend only on id [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/109740 [10:16:29] (03PS4) 10Yuvipanda: Add AbuseFilterEditResult & a test to trigger it [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/109887 [13:48:06] grrr... experimental is still broken on Android Chrome for me. [13:48:32] sections won't open, and some other buttons don't work. [18:07:14] kenanwang_: standup? [18:08:08] brion: yuvipanda: heys! [18:08:13] hey brion [18:08:14] yo yo [18:08:43] yuvipanda: brion: so i feel abused by the abuse filter... [18:09:03] ;) [18:09:09] mhurd: haha [18:09:14] mhurd: typed 'poop' enough times yet? [18:09:23] so. many. times. haha [18:09:45] mhurd: heh :) [18:09:54] (03CR) 10Jhall: "The second (VisualEditor) scenario fails for me in beta labs because the expected VE controls are not being loaded at this URL:" [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109436 (owner: 10Jdlrobson) [18:09:55] mhurd: I might change poop to warn, rather than disallow, for a while in a bit. to test my warning filter. [18:09:58] mhurd: I'll warn you beforehand [18:10:09] perhaps i'll start typing variants of 'poop' just to keep things interesting [18:12:08] p00p [18:12:45] mhurd: :P [18:12:57] WARN ALL THE POOPS! [18:13:00] brion: you need to make an iOS build today. At leats StevenW and legoktm are waiting for it :) [18:13:07] i shall do [18:13:43] brion: :) [18:18:42] hi jdlrobson if you need to sort out what VE should and should not be doing, Rummana Yasmeen in the office is an expert on VE behavior [18:19:20] jdlrobson: I mentioned to her yesterday that you and she might want to talk about VE + Mobile view [18:27:42] mhurd: I was saying 'it is not really an Issue in Android' :) [18:28:42] yuvipanda: ah cool! [18:29:50] yuvipanda: gonna go see if may's around... [18:29:56] mhurd: heh, ok :) [18:30:00] mhurd: oh yeah, we've a meeting. [18:30:28] yuvipanda: hmmm i don't see her [18:30:40] mhurd: txt her mabe? [18:32:01] yuvipanda: she's not on the hangout either... [18:32:14] violetto: hey may! [18:32:49] mhurd: she's on the hangout [18:40:49] mhurd: http://etherpad.wikimedia.org/p/design-thingies-jan-android [18:58:07] (03PS7) 10Jdlrobson: QA: KeepGoing browser tests [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109011 [18:58:09] (03PS3) 10Jdlrobson: QA: Allow browser tests in alpha mode [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109451 [19:04:33] mhurd: you could also just add http:// and it will trigger :P [19:05:27] i like to add http://spam.com [19:25:18] jdlrobson: It looks like the Thanks problem isn't specific to Thanks. All Echo notifications are currently being reported as Talk page notifications for some reason. [19:25:26] yep kaldari i sent a mail out [19:25:35] didn't know the latter though :) [19:29:42] actually, that's not right either. For some reason a small amount of Talk Page notifications are still being recorded (and thus show as 100% of the notifications) [19:44:56] so, when is Special:MobileDiff going to get a Thanks button? [19:45:14] I find myself needing that feature all the time. [19:49:54] mhurd: that was fine :) [19:49:55] err [19:49:55] fun [19:50:11] yuvipanda: yay! [20:01:35] jdlrobson: Do you mind if I merge bug 60550 to bug 60555? [20:03:35] fine with me [20:04:47] (03CR) 10JGonera: Hygiene: Add proper error reporting in lead image uploads (031 comment) [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109264 (owner: 10JGonera) [20:05:17] yuvipanda: i just emailed you a copy of what i'm going to email mobile-l about devoting a day or 2 per sprint to polish. could you go over it for a sec and see if it sounds ok before i send to list? [20:06:10] mhurd: ok! nothing yet tho [20:06:12] brion: hey [20:07:06] brb [20:07:15] yo [20:07:47] brion: greg reminder :P [20:07:52] greg-g: ? [20:10:14] (03PS4) 10Jdlrobson: Use MediaWiki UI buttons in alpha [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/102581 [20:10:51] brion: actually, we decided we didn't need him, right? [20:10:54] dr0ptp4kt, you there? [20:11:15] yuvipanda: no idea, i thought you and max and greg worked it out already :D [20:11:26] brion: heh, yeah. so nevermind, let me just send out an email [20:11:33] :D [20:11:41] (03PS5) 10Jdlrobson: Use MediaWiki UI buttons in alpha [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/102581 [20:14:18] yuvipanda: got your reply... adding your suggestion now [20:14:29] mhurd: ty! [20:14:39] brion: all the patches have been merged, right? [20:14:46] brion: can you just verify that? [20:14:49] brion: no left out ones? [20:14:51] let's find out! [20:15:05] brion: ok! [20:15:11] yuvipanda: you've got a couple on android still [20:15:11] lemme finish those up [20:15:13] brion: I can compute when they will be on enwiki once you tell me that :) [20:15:24] brion: oh, no, I meant the account creation patches [20:15:28] yuvipanda: hmm, oh that? yeah those are all merged [20:15:51] brion: ok! [20:16:01] brion: I've a biggish abusefilter patch coming up, but yeah, would be nice to get the ones out of the way [20:17:07] (03CR) 10Brion VIBBER: Make CaptchaResult depend only on id (031 comment) [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/109740 (owner: 10Yuvipanda) [20:17:26] yuvipanda: so i would prefer not to make assumptions about the internal structure of the captcha image url [20:17:43] i don't think it's really guaranteed [20:17:44] brion: yeah, but the refresh captcha thing gives me only an ID [20:17:47] ugh [20:17:49] brion: so I will have to? [20:17:54] brion: I made this change after seeing that [20:18:05] yuvipanda: so my pref would be to fix that api to return the full captcha info :) [20:18:07] or [20:18:14] we could just string-replace the old ID from the old URL ;) [20:18:38] but as long as we're willing to make updates, we can use this assumption for now [20:18:46] as it'll hold for foreseeable future [20:18:53] brion: string replace feels dirtier to me than this [20:18:55] :P [20:18:56] and nobody seems to be maintaining it ;) [20:18:57] yeah [20:18:59] brion: yeah [20:19:00] ok i'll merge it :D [20:19:12] wait lemme test it ;) [20:19:23] :D [20:25:56] ugh i hate that single quotes don't mean "string" in java [20:26:01] brion: hehe :P [20:27:10] "Hit AbuseFilter: Removal of op-tag without rights to change the page's protection level" [20:27:13] *pp-tag [20:27:19] but.... i'm not removing any tags? wtf [20:27:56] brion: huh? [20:28:10] yuvipanda: try editing https://test.wikipedia.org/w/index.php?title=Online_editing&action=edit as an anon [20:28:13] just add some text and save [20:28:21] i get back [20:28:54] brion: should be fine, right? I've the abusefilter handling commit coming up... [20:29:08] yuvipanda: well i can't see how that should even be coming up [20:29:17] if i can't edit anything without a bogus error [20:29:34] maybe someone broke a rule [20:29:35] basile: were you editing with the app? [20:29:39] err [20:29:40] brion: [20:29:43] brion: or desktop? [20:30:02] yuvipanda: both, same error [20:30:26] brion: sounds like weird abusefilter rule to me [20:30:45] yeah, i don't see a rule that says that though [20:31:06] no wait i see it [20:32:47] ok i disabled the rule and i can edit again [20:32:49] now back to testing captcha [20:33:35] brion: heh :) [20:34:11] (03CR) 10Brion VIBBER: [C: 032 V: 032] "I still don't like hardcoding that path, but it'll do for now until we revamp ConfirmEdit to suck less :D" [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/109740 (owner: 10Yuvipanda) [20:34:54] brion: there's also a unit test for that :P [20:35:03] whee [20:36:36] "info": "Hit AbuseFilter: Contains poop", [20:36:43] \o/ [20:37:11] yuvipanda: however what i get in logs is a java.lang.RuntimeException for "null" [20:37:18] shouldn't it report back the proper exception type? [20:37:47] brion: run the unit tests? [20:37:59] brion: wait, the unit tests are failing? [20:38:03] brion: the abusefilter unit test, I mean? [20:38:06] yuvipanda: manual test [20:38:18] brion: yeah, I mentioned it in the commit message that it will crash :P [20:38:22] brion: that's in the commit I'm about to make now [20:38:23] it's ok to crash, but the crash really ought to give some info about the cause of the crash [20:38:39] which right now only happens because we always the response before the crash [20:38:44] there's no information *in* the crash log [20:38:55] so it won't get emailed back to you for instance [20:39:00] brion: yeah, I agree, but this is an intentional crash, since the actual AF thing is coming right after this. [20:39:02] in case of an unhandled response type [20:39:05] brion: I'll keep it in mind for other intentional crashes [20:39:09] oh i see [20:39:11] onCatch(null) [20:39:16] ttttttpppppphhhhhhh [20:39:37] ok for future i recommend throwing a RuntimeException with a message in it :D [20:40:23] brion: yeah, will do ;) [20:41:26] (03CR) 10Brion VIBBER: [C: 032 V: 032] "For future reference, instead of failing with "null" throw a runtime exception with a relevant message, such as:" [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/109887 (owner: 10Yuvipanda) [20:42:46] brb [20:44:07] brion: at a tranining thingy today, please leave a message :) [20:44:10] (03CR) 10Jdlrobson: "I think there has been a misunderstanding. I didn't ask for this. I wanted to avoid API requests all together. I will submit a follow up." [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109939 (owner: 10MaxSem) [20:44:57] (03CR) 10MaxSem: "Umm, you're loading text with mobileview, right?" [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109939 (owner: 10MaxSem) [20:45:07] (03PS3) 10Jdlrobson: QA: Add browser tests for ajax pages [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109453 [20:45:13] jdlrobson, ^ [20:45:14] (03PS3) 10Jdlrobson: WIP: Make edit button permissions work on alpha lazy loaded pages [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109455 [20:45:42] MaxSem: no. [20:45:47] (03CR) 10Yuvipanda: "Doesn't matter though, apps still want this :)" [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109939 (owner: 10MaxSem) [20:45:49] MaxSem: I want to getGroups of a user [20:45:52] without doing an ajax request [20:46:13] why do you need groups when all you need to know is whether you can edit? [20:46:29] MaxSem: the mobile view already gives permissions [20:46:43] we should be moving away from that horrible wgIsPageEditable [20:46:47] yep, but this way is simpler, right? [20:46:58] i want us to do it right. Makes things like moving and deleting easier down the road [20:47:09] and i'm pretty much there with the code [20:47:15] so you will construct that variable manually from rights? [20:55:59] (03PS1) 10Yuvipanda: Display appropriate warning when AF returns a message [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/110228 [20:56:23] brion: ^ [20:56:26] (03PS4) 10Jdlrobson: Make edit button permissions work on alpha lazy loaded pages [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/109455 [20:56:32] MaxSem: fixes my problem ^ [20:56:42] whee [20:57:17] +114 [20:57:18] mw.user.getGroups() seems to return same as mw.config.get( 'wgUserGroups' ) [20:57:25] eh [20:57:35] but the former makes an ajax request [20:57:37] I was looking for it [20:57:50] bit confused to why that's the case [20:58:08] brion: it sometimes produces links that look like, uh, https://www.dropbox.com/s/86q2lqsxmipw7cu/2014-01-29%2020.57.25.png [20:58:09] :P [20:58:14] brion: but we will be rewriting HTML anyway [20:58:20] lol [20:58:40] yeah we're going to need small-screen-friendly messages at some point [20:58:56] brion: yeah, I have a plan for that as well. [20:59:11] brion: short term, rewrite the messages in here. [20:59:23] whee [20:59:23] brion: long term, have AbuseFilter support context-specific messages [20:59:36] mtg anyone? [20:59:47] brion: hmm, also if I try to save again it doesn't actually save [20:59:54] sounds about right [21:00:37] i wonder if we should just set a wider fake viewport in there for those damn tables/divs [21:00:46] brion: doesn't seem to be happening (I changed the 'poop' filter to just warn, not disallow now) [21:04:49] brion: were you able to save? [21:04:58] yuvipanda: ok so tried to i save with "poop", got the message, did the 'make changes' and removed 'poop' and it saved correctly [21:05:06] brion: oh [21:05:11] brion: but that's not how this should work, no? [21:05:18] brion: considering that it is 'warn' and not 'disallow' [21:05:27] well if it's a warning then it should prompt to save again [21:05:28] brion: with 'warn', the second edit should go through [21:05:37] ...... i can push 'save' again but it gives me the warning again [21:05:47] brion: yup, that's not correct behavior [21:05:50] I'm trying to find out why [21:06:04] yuvipanda: send me the screenshot of what you showed us earlier agian? [21:06:12] violetto: which one? [21:06:17] violetto: oh, that. wait [21:06:34] brion: switching it back to disallow again, for screenshot. moment [21:06:44] ok :D [21:07:21] brion: ok, back to warn [21:07:36] violetto: https://www.dropbox.com/s/16ouw9j5899jjbm/2014-01-29%2021.06.55.png [21:08:01] thanks! [21:08:13] yuvipanda: going to update the patch set or shall i merge it and let you make a followup later? [21:08:40] brion: test it a bit, I want to hear from violetto before merging [21:09:03] (03CR) 10Brion VIBBER: "I might also recommend setting a wider viewport width to make the little tables fit a bit better.... but then you get smaller text. :P" [apps/android/wikipedia] - 10https://gerrit.wikimedia.org/r/110228 (owner: 10Yuvipanda) [21:09:06] ok [21:09:18] brion: I think we can put arbitrary CSS in there [21:09:24] brion: and we should to force things to be better [21:09:43] yeah we just need shorter messages available that are friendlier to small screens [21:09:48] and don't hardcode a bunch of formatting :P :) [21:09:55] jdlrobson: jgonera MaxSem kaldari: http://hatjitsu.wmflabs.org/40516 [21:10:42] yuvipanda: violetto: do we have a wiki page where all latest design assest links are posted for various app screens? it's getting hard to remember where things are haha [21:10:56] mhurd: :P afaik, no [21:11:50] yuvipanda: violetto: could we consider having such a page, then for trello cards we'd link to relevant section of such page? [21:12:03] (for design assets) [21:12:17] mhurd: it is extra work(?) for violetto, so upto her. [21:12:34] yuvipanda: i think it'll be great to re-associate re-editing at the bottom with the pencil icon just like in the top nav [21:12:35] mhurd: I personally haven't had too much trouble just looking at the trello boards, so I don't know if it will add much value for me violetto [21:12:39] yuvipanda: https://www.dropbox.com/s/jk0damjh1z7kvpv/Screenshot%202014-01-29%2013.14.06.png [21:12:54] and when it runs however many lines: https://www.dropbox.com/s/4cfueve2pm6xiux/Screenshot%202014-01-29%2013.13.54.png [21:12:55] violetto: ok, that sounds good [21:13:15] violetto: also, we won't have 'edit' icon in the top nav, since here you are already editing, and the action is *save*, rather than edit [21:13:28] violetto: but yeah, editing here makes sense I guess [21:13:31] yeah im pretty happy with this solution, it avoids translating button text and re-associating previous icons [21:13:46] nice [21:14:07] violetto: hmm, so would you have to touch the button to go back to edit? [21:14:13] violetto: I think we should let them touch the entire bar [21:14:46] yuvipanda: i wouldn't have a problem with making the entire bar a target [21:14:55] violetto: yeah, but then it doesn't look like a target... [21:15:00] it looks like only the edit icon is a target [21:15:16] do you think users will not tap on edit icon? [21:15:51] mhurd: i'll respond to your q in a bit k! [21:15:54] violetto: I think it feels a little weird to have text associated with an icon be so far out right [21:15:54] yuvipanda: violetto: having a central page for storing the latest design mocks would maybe make it easier for things like our meeting today - where we weren't necessarily tweaking for items that are in the current sprint. [21:16:06] violetto: ya no rush [21:16:13] violetto: there's a fair bit of a gap [21:16:47] violetto: it just feels out of touch with the rest of the app. [21:17:00] violetto: we could maybe move the icon to the left, and just highlight the entire bar. [21:17:03] it's already a sectioned area for that one particular message [21:17:04] violetto: then it'll be consistent with top nav [21:17:35] yuvipanda: violetto: also would reduce work for may if she updates a png on a central page she wouldn't have to go and update it in both ios and android trello cards as both cards would just have link to central page [21:17:55] (link to section on central page) [21:18:41] yuvipanda: can you tell me more why you feel like it's out of touch with the rest of the app? [21:18:54] violetto: yuvipanda: something to consider - i know you guys are in the middle of something :) [21:19:00] violetto: so, look at the top nav, for example. [21:19:15] violetto: you'll see that the 'save' button isn't actually highlighted with a background color - it highlights only when you tap it [21:19:19] MaxSem, here now. what's up? [21:19:29] violetto: that's consistent across the app everywhere - the 'W', the 'three dots', all list items. [21:19:38] violetto: also consistent across apps in Android. They don't have highlihgts until you tap them [21:19:45] violetto: this has a highlight before you do anything to it. [21:19:50] violetto: does that make sense? [21:20:05] dr0ptp4kt, wanted to discuss how you guys want to fix link zerofication for https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/703 [21:20:54] tfinc: "Any other thoughts?" Sorry, but are you asking for my thoughts on the candidate or my thoughts on whether I should be doing review on the tech tasks? [21:22:04] violetto: did that make sense? [21:22:56] MaxSem, okay, i have some recollection of this. i see i'm on the bugzilla, but haven't thought about it much. lemme get it in our backlog and then we'll need to figure it out. [21:23:09] ok [21:23:45] yuvipanda: we're having the same conversation again.. our priority is to be consistent within wikipedia. consistency across apps in Android is more about making sure people know where to expect actions. Not style. Reason why three dots aren't highlighted because it's not a progressive/constructive suggested action, it's neutral. [21:24:17] violetto: well, save isn't highlighted either [21:24:25] violetto: and we will probably have this for a long long time [21:24:29] yuvipanda: save should be highlighted [21:24:33] violetto: shouldn't be [21:24:40] violetto: that's not how action bars on android look like [21:24:41] yuvipanda: why not? [21:24:56] violetto: to fit in with 99% of other things the user does on that device? [21:24:57] is that the only argument? [21:25:20] violetto: isn't that good enough? 'to fit in with 99% of other things the user does on that device, in an app context'? [21:25:28] your argument isnt, user cannot find it or that it stays consistent with our agora style, it's more sticking with android style [21:25:53] violetto: it is 'be consistent with the rest of android apps so that when the users sees it he knows what it is because he has seen it on all the other apps he has used so far' [21:25:55] yuvipanda: what's most important is to make sure user finds it. I'm not breaking that rule. [21:26:20] MaxSem, is that in production or not? [21:26:30] yuvipanda: that's not how it should be. android released a guide, not a rulebook. [21:26:32] violetto: indeed, and he will because that's where how it looks like on every other android app. [21:26:34] dr0ptp4kt, it's live in beta [21:26:40] MaxSem, oh okay, got it [21:26:46] MaxSem, thx [21:26:52] violetto: indeed, but why break it when we do not have a need to? [21:27:11] violetto: is it not true that that is the style users will be most familiar with on that device, context? [21:28:54] let me put it this way.. when android decides to change their visual language, we won't have to worry about it and we shouldn't, because we have our own identity. We want our users to have the "wikipedia experience on Android" not "Android experience for Wikipedia" [21:29:19] violetto: we are repeating the same things over and over again. [21:29:19] but when Android decides to change where it wants to put the progressive action, that's all we need to stay consistent [21:29:37] violetto: but it hasn't changed it. when it changes, we will talk about it at that time [21:29:47] violetto: we should ignore it for no reason other than to 'future proof' while ignoring current reality [21:30:14] violetto: err, *shouldn't* [21:30:46] violetto: again, would you put OS X style menu bars on web to be 'consistent'? [21:32:48] yuvipanda: the thing is, why the need to talk about it when it changes? That's android's identity problem, not ours. They can change however many times they wish, but whenever they do, it shouldn't be our worry to redesign our visuals [21:33:01] yuvipanda: im trying to find you something, hang on [21:33:13] violetto: we *are* building Wikipedia for Android [21:34:01] yuvipanda: violetto: the kindle app is a good example pehaps of what may's talking about [21:37:33] yep mhurd kindle (4star), yahoo weather (4.5 star), pinterest (4.5star), im just naming a few. These apps have their own identity, if you look across just about any platform. [21:37:56] im goign to try making a human example [21:38:29] violetto: mhurd the current wikipedia app also has a 4.4 star rating https://play.google.com/store/apps/details?id=org.wikipedia [21:38:59] yuvipanda: right. so it's showing that no matter who's stlye you use, users aren't confused [21:39:13] why don't we use Wikipedia style instead of copying what Android wears? [21:39:47] violetto: I think, ultiately we both have 'arguments to guides'. You want to follow the WMF style guide with a hint of Android, I want to follow the Android style guide with a hint of the WMF's [21:39:51] violetto: is that an accurate statement? [21:40:39] violetto: the Wiki 4.4 rating tells us that people love wikipedia, no matter how shitty the app is :P [21:41:01] yuvipanda: visual style wise, I want it 100% Wikipedia. interface wise, I want it Android. [21:41:04] violetto: I'd argue it is the same with kindle (it looks a bit like an old gingerbread app on my phone), and pintrest [21:41:11] consistent behavior is more important i think than consistent appearance :D [21:41:33] brion: that me and violetto both agree on, I think [21:42:23] brion: it's only with things like particular visual stylings, etc [21:42:35] brion: consistent appearance leads to many things other than just appearance. It leads to consistent experience. Wouldn't you want people to feel as seamless as possible when interacting across platform, and when they had a great experience on other platforms, they bring back the same feelings when they use the app? [21:42:59] violetto: but do you not care about a consistent experience when I'm reading an email on GMail, get a wiki link, and click one? [21:43:04] violetto: or when I am on twitter and click on? [21:43:18] violetto: what possible scenario exists where I will need to be smoothly transitioning between mobile web and mobile app? [21:43:29] yuvipanda: I care about all of that. I'm not saying one is less than the other [21:43:45] violetto: no, I am saying the mobile web <-> mobile app interaction does not exist at all [21:43:51] where does it? [21:43:59] i don't want to follow and copy what android wants to wear today. if he decides to wear slippers tomorrow it's not my problem because my style is suit and tie [21:44:08] not saying that wikipedia wears suits and tie [21:44:19] violetto: you don't want to be wearing 80's style clothing in a party today either, do you? [21:45:11] violetto: but where *does* a user experience a flow that involves both the mobile web and the mobile app? [21:45:26] violetto: I can't think of one yet [21:46:07] yuvipanda: we're trying to not make wikipedia wear a 80s style clothing. point is, i dont care what androids decides to wear. I respect its behavior when im in his house, but im wearing my own dresses, damnit [21:46:16] violetto: well, my point is, *I* care [21:46:21] violetto: I want the app to be a good Android citizen [21:46:25] why do you want to follow what he wears? [21:46:26] violetto: not stick out like a sore thumb [21:46:28] you have your own identity [21:46:41] yuvipanda: violetto: hehe could i suggest a hangout may be a less typing intensive option for hashing out design philosophies? [21:46:41] violetto: Android is a platform, not another app [21:46:53] mhurd: typing's good :P [21:47:10] you are sticking out like a sore thumb with your own brothers. you're trying to do surgery on your face so you don't look like your brothers [21:47:17] violetto: you could still easily convince me by pointing out a workflow where I would be going between the app and mobile web [21:47:37] violetto: I did point out several workflows that involve going from another app to yorus [21:47:38] yuvipanda: what you're suggesting is not a good practise in design [21:47:38] *yours [21:47:50] that is why there is a whole industry for brand identity [21:47:55] it's just so we have our own [21:47:59] not following others [21:48:32] mobile web has just implemented the header design [21:48:42] you can take a look at that [21:48:44] violetto: I'm not saying we won't have our own design. I'm simply saying that things like solid backfilled colors as in that mockup to indicate actions make the app feel like the people building it did not really care about android [21:48:50] go into the edit workflow and you can see what im talking abuot [21:49:07] yuvipanda: your concern is not in the right place [21:49:11] violetto: explain [21:49:45] violetto: my end goal here is to make sure that the app 'fits into' the android ecosystem, rather than look like something that was developed with iOS in mind and then absentmindedly ported to Android. [21:50:21] the action is placed in the area where it's consistent in android. How is making the back colored to encourage users to notice as a next progressive action in any way bad? [21:50:25] violetto: there are plenty of people who do that, and I explicitly do not want to be one of them. I do not want us to be one of them. I *know* we aren't one of them. Just that these small things make it appear otherweise [21:51:49] yuvipanda: making the back fill is iOs? [21:53:22] violetto: for actions? IMO, yes. but I think I am going to take a time out and sleep. But, here's a compromise - do up the actionbar theme generater I showed you, or just give me assets and exact colors for the top nav, and I'll implement it your way, and then let's have this discussion? [21:53:36] violetto: maybe we both are saying the same thing but disagreeing with each other [21:54:00] yuvipanda: when you get a chance to, show me an example where an iOS app did that [21:54:06] right now, i don't see your point. [21:54:13] i mean, i don't see your association [21:54:16] ok go to bed! [21:54:18] violetto: Instagram? [21:54:28] violetto: 'But, here's a compromise - do up the actionbar theme generater I showed you, or just give me assets and exact colors for the top nav, and I'll implement it your way, and then let's have this discussion?'? [21:54:48] yuvipanda: okay [21:58:49] violetto: in hindsight, ignore the things I said about iOS and stuff. I seem to have been talking out of the wrong end of my brain, feueled more by some random emotion than actual rational thought. [21:58:57] I'll just implement it and let's tweak it until it fits. [21:59:02] violetto: apologies for the rants. [22:00:25] yuvipanda: it's all good, if there were none of these i'd be worried that things are too smooth sailing anyway [22:00:53] violetto: heh :) should also teach me against staying up past 2AM :) [22:01:14] yuvipanda: its hard when it's so bright over here, bed, now! [22:01:41] violetto: heh! :) [22:04:49] violetto: oh, may, can u attach svg's for the flag and "x" icons to the abuse filter stories? [22:06:10] mhurd: i think i did, you didn't find them in there? [22:06:17] violetto: quick question - what happens if user taps the checkmark icon in top left or pencil icon in top right in the abuse warning mock: https://trello-attachments.s3.amazonaws.com/52cd94d036733f07251de3a5/52deba4d901328970adb7bfb/5d928a81265f94f94586a3bf3545ed60/AF.png [22:06:25] violetto: ah lemme check... [22:06:25] im in the midst of asking Pau something about the X icon [22:06:38] violetto: ah you did! thanks [22:06:46] oops :) [22:06:55] mhurd: does iOS support native SVG rendering? [22:07:02] mhurd: or do you also have to rasterize into PNGs? [22:07:11] yuvipanda: no i just use them to get precise rasters [22:07:18] mhurd: ah, ok [22:08:25] mhurd: how many sizes do you need to rasterize to? [22:08:30] (just curious) [22:08:40] reminder awjr|errand i'm gonna be out for half of next iteration [22:09:24] yuvipanda: say the icon is 100px by 100px, i do one at that resolution for non retina devices, then i do one at 200px x 200px for retina [22:10:17] jdlrobson: ahha, thanks i had forgotten [22:10:21] they still look same size as long as i name them according to apple's naming covention - the system grabs proper one at display time [22:10:24] jdlrobson: dates? [22:10:26] yuvipanda: ^ [22:10:33] mhurd: ah, nice! [22:10:37] mhurd: right. [22:10:47] mhurd: android's slightly more complicated, so I wrote a script that does it :D [22:10:53] awjr|errand: should be in the mail somewhere. will confirm sometime next week before i go [22:11:10] jdlrobson: ok; im looking throug emails but not seeing anything - did you send it a long time ago? [22:11:24] ah yeah from 12/18 [22:11:27] i guess :) will dig it out later but it's there somewhere :) [22:11:31] yuvipanda: nice! i've found things look best if i never resize rasters, but generate them at the exact resolution needed directly from the svg [22:11:32] jdlrobson: found it :) [22:11:44] thanks for the reminder [22:11:53] be sure to remind us again when we kick off on monday [22:11:56] ok, now im running my errand for real [22:11:57] bbiab [22:14:16] mhurd: yeah! What do you use to rasterize from SVGs? [22:15:26] yuvipanda: since i don't do it too often, i just google for online svg to png converter and use online tool [22:15:33] hehe [22:15:57] mhurd: hehe [22:18:57] (03CR) 10Jdlrobson: [C: 04-1] Story 1621: Fixing VE content area typography/design for mobile (038 comments) [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110122 (owner: 10Kaldari) [22:19:29] brb [22:20:45] (03CR) 10Jdlrobson: Story 1621: Fixing VE content area typography/design for mobile (033 comments) [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110122 (owner: 10Kaldari) [22:30:44] brion: so, you should make the build without any of the AF stuff, I guess :) [22:30:50] brion: do send out the b uilds! especially iOS [22:31:34] oh you committed it, it's gonna be in there. ;) it'll just fail in interesting ways instead of less interesting ways ;) [22:32:18] brion: yeah, I mean, the unmerged stuff [22:32:34] ok :D [22:32:44] brion: :) [22:37:01] violetto: brion mhurd going to sleep! [22:37:04] night! [22:37:09] yuvipanda: gnight! [22:37:14] hehe [22:37:16] gnight yuvi :D [22:37:52] brion: have you seen http://jgilfelt.github.io/android-actionbarstylegenerator/ [22:38:15] i have not.... but that sounds handy! [22:38:41] brion: yeah, trying to get violetto to play with it so we can directly use them here [22:39:37] spiff [22:47:51] mhurd: hey monte, back to the mediawiki/trello asset delivery. I'll eventually find time to update mediawiki. But yuvipanda and I spoke and have decided to create cards on Trello if they don't exist on current iteration. Plus, it's so easy to upload assets, if they need to change, etc, rather than going through the uploading process on commons [22:48:18] mhurd: would you be open to trying that? [22:51:21] DarTar: Hey I'm going to pop into another meeting for a little bit so I'll be 10 minutes late if that's ok [22:52:00] (03CR) 10Kaldari: Story 1621: Fixing VE content area typography/design for mobile (0311 comments) [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/110122 (owner: 10Kaldari) [22:52:44] jdlrobson: Would love to get your replies to comments at https://gerrit.wikimedia.org/r/#/c/110122/ before doing another patch on it. [23:02:24] kenanwang_: np, running late too [23:05:39] MaxSem: were you able to connect with adam or yuri today? [23:06:15] yup, waiting for them to think about it [23:06:21] great [23:18:10] k DarTar I'm heading over now [23:24:08] violetto: yuvipanda: https://trello.com/b/Id6qXKSY/mobile-app-latest-design-assets-by-page [23:25:38] violetto: the article nav assets are out of date. but that's why i like this approach, my hope is that you will add your new article nav assets to the card for "article navigation". that way i can see both the initial mocks and the new ones all in one place [23:26:38] mhurd: okay let's try this [23:26:39] violetto: i tried to go to old boards to get mock from saved pages/history etc. but trello say's those boards are closed! all the more reason to have a persistant board [23:27:30] violetto: can we try never deleting assest - just adding new assets so we can follow the evolution of the design? [23:27:39] *assets* [23:27:50] mhurd: yea i like the idea too [23:28:01] violetto: also maybe try only ever having *one* card per page [23:28:15] i wish commons is less of a pain, i'd love to update on mediawiki if it was easier [23:28:44] violetto: i've stubbed most pages cards out, so we should never have to create card (or rather, only once when we add new page to app) [23:29:43] mhurd: cool. i hope this works better for you [23:30:05] violetto: if we start being able to count on assets always being posted here we won't have to add *any* links to sprint board stories - we'll just know to look at the "latest assets" board [23:30:19] mhurd: i'll find some time at the end of the week to upload what i have [23:30:48] violetto: if you could dig up the assets for saved pages / history etc too that would be super useful for me [23:31:19] kenanwang_: I'm in R36 in case you're lost ;) [23:31:38] mhurd: sure [23:31:42] violetto: also, i see the flag svg for the abuse filter warnings card, but not the "X" icon. would you mind attaching that too? [23:32:02] mhurd: ok i'll do that. need to run into a meeting now, ttyl k! [23:32:08] violetto: thx! [23:47:35] (03CR) 10Kaldari: [C: 04-1] Use MediaWiki UI buttons in alpha (033 comments) [extensions/MobileFrontend] - 10https://gerrit.wikimedia.org/r/102581 (owner: 10Jdlrobson)