[00:02:56] !g I45028ed2f13148332518badd5f4647d4d652884e [00:03:51] RoanKattouw: https://gerrit.wikimedia.org/r/#/c/70918/ [00:04:09] RoanKattouw: But I assume you were wanting grrrit-wm to answer? :-) [00:04:17] James_F: No that's wm-bot's job [00:04:29] RoanKattouw: Whichever. But yes. :-) [00:04:56] James_F: Anyway, that ---^^ is what Ori and I discovered is causing keyboard interaction (jncluding typing) to be so slow on Chrome [00:05:25] Heya Krinkle. [00:07:23] I'm very happy to have finally solved that particular mystery [00:08:02] Problem is, I don't know how to fix the toolbar issue without introducing that slowness, and mobile seems to have additional issues in Chrome anyway [00:11:43] :-( [00:15:00] RoanKattouw: We could have the toolbar not float, but instead terminate the document below it, I guess… [00:16:01] Finally back in civilisation [00:16:24] Krinkle: Is that what you call it? :-) [00:58:59] RoanKattouw, the VE overlay's container has -webkit-backface-visibility: hidden and translate3d(0, 0, 0) and I think that [00:59:01] 's it [00:59:20] correction [00:59:30] VE overlay's _header_ container [00:59:42] but header container is a sibling to VE's surface, not a parent [01:00:10] we do a weird hacky thing though and we move the VE toolbar node from the surface to the header (not sure if that could be related) [01:03:04] jgonera: OK [01:03:23] jgonera: So what's the ID/class/identifying property of the element that has bf:hidden and translate3d(0,0,0) on it? [01:03:56] Also, using bf:hidden broadly is playing with fire, I can probably expose bugs related to ti [01:04:08] mooeypoo: GitGutter and Gutter Color [01:04:40] RoanKattouw, .overlay-header-container [01:04:48] Thanks [01:04:48] ti? [01:04:51] *it [01:05:01] Let me experiment with removing those properties, see if that changes anything [01:05:11] if you can point me to some reading, I'd be grateful [01:08:01] It's mostly personal experience [01:08:14] And the main bug with backface-visibility (transparent PNGs render as all black) has been fixed [01:12:02] jgonera: Oh, never mind, the bf:hidden rule isn't applied to the surface itself it seems, just to an overlay [01:39:29] RoanKattouw, I probably should have marked it in the commit - some of this blocked-checking code was copied from core, I probably didn't clean it up properly [01:41:20] Title::checkUserBlock specifically [01:49:44] fixed, will deal with issues on js file later [01:55:21] Krenair: Tsk, GPL code copied into an MIT repo? [01:56:33] Of course, MW-core code is generally so awful that it goes the other way. :-) [01:57:31] Yes, I should probably know better than to simply use it like that :/ [02:02:23] * James_F grins. [02:48:04] quick question, how do I add categories using VisualEditor? [02:57:19] how do i upload and then insert and image into a page? [02:59:22] Meiko, does this help? http://www.mediawiki.org/wiki/Help:VisualEditor/User_guide#Editing_categories [02:59:34] k-man: yeah, thanks [03:00:16] i'm new to visualeditor myself [06:39:47] Is visual editor plugins idea dropped from gsoc? [07:09:33] +roan are you there? [14:42:02] Anyone there? Need help [14:59:00] Anyone there? Need some help [15:03:56] So, last night I installed supervisor for nodejs... Couldn't use any of the scripts for /etc/init.d since the client uses RH [15:04:34] and now, I need to find someone to talk to about what needs to be supported in a browser for the browser to use IE. [15:04:56] (Since the client has deployed IE. How corporate!) [15:11:42] IE and RH? very corporate! [15:30:23] santosh2201: Hello! When you're on IRC it's usually good practice to jump right in and ask a question, as it saves time for everyone involved :) how can we help you? [15:31:26] santosh2201: Hello! When you're on IRC it's usually good practice to jump right in and ask a question, as it saves time for everyone involved :) how can we help you? [15:31:57] Is visualeditor plugin idea dropped from gsoc? [15:33:36] santosh2201: I don't see any evidence of that, why do you ask? [15:34:42] Till yesterday it was listed in ideas... But today it's gone. I was working on a proposal. [15:34:57] santosh2201: https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#VisualEditor_plugins [15:35:41] But maybe James_F knows something about it being gone [15:36:32] Ok. [15:36:36] santosh2201: Your connection is really bad :) [15:36:49] * hexmode looks for James_F, decides he might need to send an email. [15:37:12] (also, wow, I did it again, I got into -visualeditor and failed to realize it) [15:37:24] Yeah. It's too bad. Will find another irc client to connect [15:37:28] hexmode: James_F just signed on, in fact, and is active in other channels. [15:38:06] rdwrer: hey, twin! [15:38:07] ;) [15:38:13] Hah, hi [15:38:16] Hey. [15:38:28] Not available for about three hours when my back-to-back meetings are over, sorry. [15:38:40] :((( [15:38:54] TrevorP|Away would be my next attempt at an answer. [15:39:33] James_F|Away: so, I was just looking at https://www.mediawiki.org/wiki/User:Jdforrester_%28WMF%29 and notice that I *really* want to talk to you about distribution issues for Lua/VE, etc. [15:39:38] But you're away now [15:39:46] so I'll type up my thoughts [17:33:50] FYI you all should expect tonythomas to come in here later asking about https://bugzilla.wikimedia.org/show_bug.cgi?id=62762 [17:44:50] rdwrer: how's it going? [17:44:57] Hi TrevorParscal. [17:45:12] did you get an answer? [17:45:20] We had a potential GSoC'er in here asking about VE plugins as a project [17:54:56] ah [17:59:15] TrevorParscal: Is it still a project, or did it get murderededed. [17:59:28] which one? [18:00:17] ve plugins work, it's a hook thing [18:01:10] I think it may or may not be a project to *create* plugins [18:01:21] TrevorParscal: https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#VisualEditor_plugins is the one in question [18:02:04] ah, yeah I think we are still doing that [18:11:32] On replacing $.proxy() with .bind() for the bug https://bugzilla.wikimedia.org/show_bug.cgi?id=62762 , will it be ok, if I replace [18:11:40] this.$element.on( 'keypress', $.proxy( this.keyup, this ) ) with [18:11:46] this.$element.on( 'keypress', this.keyup.bind(this) [18:11:48] tonythomas: I'm writing a comment on that bug right now [18:11:48] ? [18:11:57] RoanKattouw: ok [18:15:09] Meh, Krinkle|detached is away [18:15:17] Krinkle|detached: When you're back, could you weigh in on https://bugzilla.wikimedia.org/show_bug.cgi?id=62762#c3 ? [18:18:02] tonythomas: I've asked Krinkle|detached to give his opinion since he's our JS expert, but if in the meantime you have any other questions, feel free to ask :) [18:18:43] RoanKattouw: when you said 'We don't use $.proxy() directly in the VE code base' , but I see the same in jquery.uls.langauagefilter.js -> if ( this.eventSupported( 'keydown' ) ) { [18:18:43] this.$element.on( 'keydown', $.proxy( this.keyup, this ) ); [18:18:43] } [18:19:21] Right [18:19:27] jquery.uls is an external library we use [18:19:49] So it's not part of the VE codebase proper, instead we just copy it from somewhere else [18:20:33] VE itself lives in the modules/ directory, libraries live in the lib/ directory [18:20:54] But then in the VE-MW repository, VE-core lives in lib/ve/modules/ve , which is a bit confusing :S [18:21:12] But in general, only things in modules/ are things that actually belong in that repository, and things in lib/ are things that came from somewhere else [18:21:21] Hey. [18:21:37] RoanKattouw: *cough* mv modules src [18:22:06] RoanKattouw: ok! so, thats part of the external code -- so no probs [18:22:45] and indirectly, when you use those in your VE, we are implementing ve.bind = $.proxy ? [18:23:10] greg-g: E4J [18:23:56] ? [18:25:37] I will brb. [18:26:09] tonythomas: So in modules/ve/ve.js in the VisualEditor/VisualEditor.git repository (which is lib/ve/modules/ve/ve.js in the mediawiki/extensions/VisualEditor.git if you're using the submodule) there's this definition that sets ve.bind = $.proxy; [18:26:16] And then everywhere in the VE code we use ve.bind() [18:26:19] hexmode: Sure, what thoughts? [18:26:32] So if you change what ve.bind() does, you'll magically change how everything everywhere (at least in VE-land) is bound [18:41:00] TrevorParscal, are you around? I have a question regarding oojs object. Namely, I would like to see if we can put the size widget inputs side by side with inline labels. [18:41:15] TrevorParscal, So, something like [___] x [___] px [18:43:05] RoanKattouw: Ok. but, I cant find ve.js in https://github.com/wikimedia/mediawiki-extensions-VisualEditor/tree/master/lib/ [18:43:19] TrevorParscal, I could probably force this with two fieldset layouts and some CSS, but it will also likely be a little hacky this way. Should we have this as a new oojs widget? Is it useful in general? a sort of group of input/labels in the same row? Or should I make this a ve-specific widget? *or* should I abandon this completely as a bad idea and stick to inputs in separate lines? [18:44:26] tonythomas: Yes, GitHub (and gitblit) don't work well with submodules. [18:45:42] James_F: yeah. and there is a link ( not clickable ) showing ve @ f1249e there though [18:46:10] James_F: And how do I clone the submodule ? [18:46:12] tonythomas: https://git.wikimedia.org/blob/VisualEditor%2FVisualEditor.git/HEAD/modules%2Fve%2Fve.js is the file. [18:46:46] tonythomas: Once you've done `git clone` of the main module, run `git submodule update --init` inside the directory. [18:47:07] tonythomas: So `git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git`, `cd VisualEditor`, `git submodule update --init`. [18:47:37] James_F: Thanks! [18:48:27] James_F: I am little late for tonight. Will start with it tomorrow. [18:48:34] tonythomas: No worries. [18:48:44] James_F: :) yeah [18:49:48] I want a sushiritto today! James_F, TrevorParscal: Do you know if they still constantly have long lines? [18:50:05] mooeypoo: hey [18:50:09] sorry, diddn't see it bouncing [18:50:15] reading [18:50:38] np, that's why I pinged. I'm trying to figure out the best way of doing this, if at all. [18:50:42] InezK: I have no idea what that is. :-) [18:51:28] mooeypoo: within the widget, use inputs inside divs and style the divs [18:51:30] James_F: It's the place right next to the Crunch Fitness gym on New Montgomery. You know, the place that put barriers outside so the line wouldn't block the fym [18:51:37] *gym [18:52:03] TrevorParscal, the other "challenge" is that I'm thinking about having the layout be something like this: [18:52:06] Scaled: [____] % [18:52:06] Custom: [____] x [____] px [18:52:12] InezK: I *think* the lines aren't that bad any more but then I 1) haven't been out at traditional lunch time a lot lately and 2) have probably become desensitized to that line [18:52:32] RoanKattouw: Oh. I thought they were queueing for the gym? [18:52:39] Nooo [18:52:41] The gym was pissed [18:52:56] Diddums. :-) [18:52:58] hah, were they blocking entrance to the gym? [18:53:03] (errrr internet weirdness) [18:54:40] yeah, so the challenge is that Scaled and Custom might not translate to labels that fit? [18:55:27] btw, I love the ASCII rendering of the UI [18:55:30] TrevorParscal, the challenge is how to make it so they're aligned, too [18:55:45] well, first off those should be right aligned labels [18:55:57] so if it was something like label: [___] / label: [___] i could use field layout for both [18:56:08] but field layout accepts widget and then label [18:56:22] InezK: Yeah the gym wasn't happy, that place gets a lot of people working out over lunch [18:56:24] and in the case of the size, it's actually 2 input widgets with 2 label widgets [18:56:29] <-- brainsplosion [18:56:31] mooey: look at this image: http://cl.ly/image/3C1d3D2j340E [18:56:45] this is an image export dialog in a program I use for vector graphics [18:56:57] So Sushirrito ended up putting these things on the gym's sidewalk to guide the line and keep it away from the gym entrance [18:56:59] ooh [18:57:26] mooey: so, the labels to fields like this should be right aligned [18:57:35] TrevorParscal, yes, my next idea btw was to make a scale for the scale. So, testing my ascii drawing skills, something like: |--------*--| [18:57:45] and.. movable. But anyways, that's for later. [18:57:54] and you can add a generous amount of space on the left to accomodate for the labels being unpredictable lengths [18:58:11] TrevorParscal, yes, but we need to have inputs for the width/height, not just labels [18:58:12] ah, like a slider? [18:58:19] yup, that's the word I was looking for [18:58:42] Would've been easier to say slider than try to draw it, but I forgot the word... [19:01:26] James_F: Just wanted to check base with you about my proposed timeline before submitting my application tomorrow for OPW: https://www.mediawiki.org/wiki/User:Mvolz/OPW_proposal_round_8 [19:03:49] mvolz: I presume in "Month 2" the second label should be 18 July, not 18 June? :-) [19:05:30] mvolz: It looks reasonable, other than that. [19:05:43] James_F:yes [19:05:58] Great! Also there was a confused GSoc in here earlier, didn't know if you saw that [19:06:17] VE plug-ins got moved from the projects section to the raw projects section? [19:06:47] mvolz: Yeah, we wanted to de-prioritise for other people because we have some great candidates already. [19:07:07] Ok [19:09:33] TrevorParscal, ok, so I think I will maybe make a ve-specific widget for [__]x[__] so I can then feed it into fieldlayout and make another widget. Is this too roundabout'y? i think it might be better than hacking away at the CSS [19:09:57] that seems ok, but feel free to just build that all into the widget you are making [19:10:38] I mean, all the fields can be encapsulated if you want, but if breaking some out and then using FieldLayouts is totally cool too [19:11:11] using FieldLayouts is probably easier and better for a couple of reasons, but as you noted, you will need to make a widget for [__]x[__] [19:12:55] Yeah, I wanted to use the FieldLayout so I can also set css rules that can align them correctly and such. It might be better. Then again, I will start and see. If I end up going in too many circles, I'll just build everything into the media size widget directly. [19:14:56] You should use FieldLayout, I think that is the best [19:15:15] that way, as we make changes to FieldLayout it will automatically apply to this widget [19:22:43] mooey: http://cl.ly/image/0O1y180T0b2Z [19:22:50] this is another idea, James_F, any thoughts? [19:23:11] TrevorParscal: You can't set the width by %. [19:23:36] Maybe when you are in % mode it shows only 1 input [19:23:42] TrevorParscal: I mean, it would either show 300x200 px or 50x50% [19:23:43] and when in PX mode it shows 2 inputs [19:23:50] Animating input changes? [19:23:51] Eww. [19:23:59] animating? no, it would just switch [19:24:02] in place [19:24:04] same width [19:24:39] just an idea [19:25:02] I think that's confusing, especially since we're going to let the user choose between 'custom' and 'scale' [19:25:13] We should get rid of custom [19:25:15] those should probably be best as separate sections, to make it more understandable. [19:25:31] we should just unselect the options in the buttonselect when it's custom [19:25:48] and auto-select the options when you happen upon values that match their criteria [19:26:07] also, what happens when both are true? The original size is the same as the default size [19:26:16] TrevorParscal: Picture in your e-mail. [19:26:18] I don't really like them being stateful [19:26:29] Actually,I think that the user needs to know that what they just did is "custom" [19:26:50] as in, "you just changed the size to neither of the automatic values" indicator. [19:27:27] TrevorParscal, they can't be both true, because of wikitext. Scale is setting "upright=x" and custom is bounding box [19:27:31] I guess because default is the lack of a setting it should be stateful, but making full or custom are not stateful, they are commands [19:27:41] hmm [19:27:47] Default isn't the lack of a setting. [19:27:50] That's why the ticks are important :\ so, you'll see the values reflecting the change, but they won't be *set* [19:27:52] It's a setting in itself. [19:28:03] images in MW are so horrible [19:28:08] Yes. [19:28:11] We should fix them. [19:28:14] But later. [19:28:17] sure [19:28:21] i'm not trying to change them now [19:28:22] as in, if I change the width/height to some value that, incidentally, is scale=80%, i'll have 80% in the scale textbox BUT it won't be set to scale until I click "SCALE"... does that make sense? [19:28:39] :-) [19:28:41] so you're always either scale or custom or automatic. [19:29:02] And it will show the values if you switched to using that system? [19:29:09] after looking at a lot of image size dialogs in different programs [19:29:13] yeah [19:29:15] it's super common to select units [19:29:28] TrevorParscal, different systems don't go by wikitextravaganza [19:29:30] :\ [19:29:33] Yeah. [19:29:45] Also, we shouldn't let images be abused they way they are. [19:30:02] Sure, but meeting user expectations is good, and using [ one or two inputs here ] [ px | % ] works pretty well [19:30:09] you are either scaling or using PX [19:30:44] I'm not saying I've solved it, i'm just saying, selecting units is probably a good idea [19:30:57] Gah. [19:30:57] and magically switching depending on which input you change seems sort of wrong [19:31:04] I disagree. [19:31:10] the user should know whether they are using % or px [19:31:14] scale or custom [19:31:18] As you would have known for the past hour of conversation about this had you been here. :-) [19:31:20] TrevorParscal, but upright (percent) scales the width-only and px is width and height [19:31:32] so it gets confusing when you have % on 2 inputs when in reality you just need one [19:31:35] TBF it's linear scaling on both dimensions. [19:31:48] But yeah, 45%x45% is confusing. [19:31:50] french wiki I believe uses 'upright' a lot -- that's a single-input setting, like 80% or something [19:32:07] I don't think it's confusing if you disable or hide the input you aren't using [19:32:19] i also think that for an unsuspecting layman user, it is much easier to go "scale 80%" and see the width/height values reflect the change [19:32:25] i'm not suggesting showing 2 scale inputs [19:32:33] That's what we were talking about - greyed out inputs if you weren't using them. [19:32:43] With placeholder values, but not actual values unless active. [19:32:51] oh, yes, but always show the *actual* image size in the width/height [19:33:19] so if you go with scale, the inputs will be greyed out, but still reflect the values. I think that makes it clearer. [19:33:22] anyway, I'm not like convinced I have this sorted, I'm just suggesting suggesting that custom and scaled are strange terms, px and % are much clearer [19:33:52] TrevorParscal, well, the 'custom' will have 'px' after it, and the 'scale' will havde % after it, fi that's what you mean? [19:33:56] it will just alwas appear. [19:34:03] (and be selectively disabled) [19:34:13] is that what you mean [19:34:13] ? [19:36:15] I think you are on the right track [19:36:18] just run with it [19:36:30] sorry, I didn't mean to make it more confusing [19:41:53] TrevorParscal, I don't think it's possible to make images more confusing than they already *are*. [19:43:00] * James_F grins. [19:52:22] https://bugzilla.wikimedia.org/show_bug.cgi?id=62796 sounds like it's to do with autoEllipsis [20:01:41] James_F, did you assign that to me because I recently touched some related code? [20:10:02] Krenair: Yeah, thought you might be interested. [20:10:16] Krenair: If you don't want it don't sweat. :-) [21:45:39] (03PS5) 10Jforrester: [WIP] Red link support [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/118045 (owner: 10Catrope) [21:45:50] (03CR) 10jenkins-bot: [V: 04-1] [WIP] Red link support [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/118045 (owner: 10Catrope) [21:47:42] lol: "Wikipedia makes extensive use of two faces: Linux Libertine and Jimmy Wales." [21:49:22] RoanKattouw: ^^^ Apparently you need to rebase. Fun. [21:50:17] Boo [21:50:23] I'm doing LU review now [21:50:33] RoanKattouw: Kk. [21:50:40] Niklas's code is looking pretty nice and clean so far [21:50:46] Night and day from what was there before [21:50:48] * James_F can imagine. [22:38:40] (03PS11) 10Robmoen: Create mixin for ce nodes that responds to dblclick [VisualEditor/VisualEditor] - 10https://gerrit.wikimedia.org/r/103062 [22:38:57] (03PS10) 10Robmoen: Mixin ClickableNode with ce nodes that have tools [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 [22:39:12] (03CR) 10jenkins-bot: [V: 04-1] Mixin ClickableNode with ce nodes that have tools [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 (owner: 10Robmoen) [22:39:34] (03CR) 10jenkins-bot: [V: 04-1] Create mixin for ce nodes that responds to dblclick [VisualEditor/VisualEditor] - 10https://gerrit.wikimedia.org/r/103062 (owner: 10Robmoen) [22:40:18] (03PS11) 10Robmoen: Mixin ClickableNode and add Primary command names [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 [22:40:28] (03CR) 10jenkins-bot: [V: 04-1] Mixin ClickableNode and add Primary command names [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 (owner: 10Robmoen) [22:49:28] (03PS12) 10Robmoen: Create mixin for ce nodes that responds to dblclick [VisualEditor/VisualEditor] - 10https://gerrit.wikimedia.org/r/103062 [22:49:57] (03PS12) 10Robmoen: Mixin ClickableNode with ce nodes that have tools [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 [22:50:08] (03CR) 10jenkins-bot: [V: 04-1] Create mixin for ce nodes that responds to dblclick [VisualEditor/VisualEditor] - 10https://gerrit.wikimedia.org/r/103062 (owner: 10Robmoen) [22:50:29] (03CR) 10jenkins-bot: [V: 04-1] Mixin ClickableNode with ce nodes that have tools [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 (owner: 10Robmoen) [22:50:38] (03PS13) 10Robmoen: Mixin ClickableNode and add primary command names [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 [22:51:02] Arrgg Jenkins [22:51:09] (03CR) 10jenkins-bot: [V: 04-1] Mixin ClickableNode and add primary command names [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 (owner: 10Robmoen) [22:53:31] rmoen: If you have a commit in VE-MW that's based on an unmerged commit in VE-core, then Jenkins is expected to fail [22:53:54] So the Jenkins failures for https://gerrit.wikimedia.org/r/103063 aren't a problem [22:54:10] (not a problem with your code that is; they are a problem with our infrastructure that needs to be fixed at some point) [22:54:22] (03PS3) 10Alex Monk: Show blockedtext message in edit notices [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/119204 [22:55:07] Hello, everyone. Would someone like to check a possible bug for me, to make sure that it's not just me? It will take just a minute or two. [22:55:44] Go to mediawiki.org, open a page in VisualEditor, type something, and try to link it to Help:Help (which is an existing redirect page there). [22:56:23] It claims that this page doesn't exist for me. In fact, I can't link to any redirect page at MW; it claims they're all "New Pages". [22:56:34] But it works correctly at both beta labs and en.wp [22:56:52] RoanKattouw: any idea why the npm check is failing on https://gerrit.wikimedia.org/r/#/c/103062/ ? [22:57:43] whatami: Checking [22:57:58] rmoen: 22:50:07 Illegal trailing whitespace at modules/ve/ce/ve.ce.Surface.js : [22:58:05] line 593 [22:58:10] RoanKattouw: oh [22:58:13] ty [22:59:03] rmoen: Ideally we wouldn't bury that one useful line in hundreds of lines of garbage :S [22:59:46] RoanKattouw: yeah sometimes the logs confuse me. [22:59:55] whatami: Confirmed that Help:Help shows as red [23:00:02] And for some reason i didn't see that whitespace in the diff [23:00:15] Thanks RoanKattouw . I'll give you a bug report in a bit. [23:00:18] which is BS because it's a redirect to Help:Contents which exists [23:00:28] whatami: Thanks. I'm already looking to see if I can diagnose this quickly [23:00:42] rmoen: There's a trailing whitespace plugin for Sublime that mooey told me about yesterday [23:01:10] Do you want the bug report, then, or is that just one extra piece of paperwork for you, Roan? [23:01:14] It makes them red, and you can optionally add a keyboard shortcut to destroy them all, or have it destroy them all on save (the latter is a bit too radical for me) [23:01:19] whatami: Please do file the bug report [23:01:20] RoanKattouw: I'm really surprised the linter didn't see it [23:01:35] Okay. I'm off to Bugzilla. Thanks! [23:09:22] I've created the bug report: https://bugzilla.wikimedia.org/show_bug.cgi?id=62804 [23:14:33] (03PS13) 10Robmoen: Create mixin that tries to execute primary node command [VisualEditor/VisualEditor] - 10https://gerrit.wikimedia.org/r/103062 [23:15:38] (03PS14) 10Robmoen: Mixin ClickableNode and add primary command names [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 [23:16:09] (03CR) 10jenkins-bot: [V: 04-1] Mixin ClickableNode and add primary command names [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/103063 (owner: 10Robmoen) [23:17:42] I'm getting smaller and smaller. [23:35:31] (03PS1) 10JGonera: [WIP] Style link inspector on mobile [VisualEditor/VisualEditor] - 10https://gerrit.wikimedia.org/r/119413 [23:35:37] (03PS1) 10JGonera: [WIP] Limit some styles to desktop [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/119414 [23:36:11] (03CR) 10jenkins-bot: [V: 04-1] [WIP] Limit some styles to desktop [extensions/VisualEditor] - 10https://gerrit.wikimedia.org/r/119414 (owner: 10JGonera) [23:40:31] ryasmeen, mooeypoo: https://bugzilla.wikimedia.org/show_bug.cgi?id=62805 is the bug I filed against Parsoid for the NaNxNaNpx thing